Re: Bug in the PluginController

> Actually, this is exactly as it is intended.

Oha.

> The outgoing raw case was already there (look at the bottom of your  
> patch, you will see it removed there).

Yeah, I noticed it, though I thought that was by mistake.

> Renaming incomingCtl to incomingRaw will break all existing plugins  
> which used it.  Plugins made for 1.5 still work with 2.0 if this  
> change is not made.  This saves people from having to recompile as  
> well as saving users from having to download their plugins again.   
> It is also useful for those of us running both 1.5 and 2.0 betas,  
> like the developers.

Hm, ok, so will you publish a new plugin interface for 2.0? As far as  
I can see versioning is fully supported by the plugin api, so this  
should be no problem.

cu Martin


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf