On Tuesday 13 February 2007 22:30, Anders Olofsson wrote: > Looks good but I have a few comments as well. > > * Adding features to the API should not stop older plugins from loading as > long as the new API is still backwards compatible with the version > required by the plugin. > This has already been mentioned in previous replies but I think this is > important as this could otherwise be a problem for plugin-developing that > all plugins must be updated just because some new function was added. > I like the numbering described in Jon's reply with for example 3.2.4 being > backwards compatible with 3.2.1 but not with 3.1.5 or 2.8.3. My > interpretation (or suggestion) is that the last number is increased when > the API is changed but still backwards compatible, the middle number > increased when changes break the compability and the first number > increased when there is a major redesign of the API. Maybe the first > number is not needed at all(?) I'm assuming the API version will be > independant af the licq version.
See my response to Jon. > * A reason for unloading plugin libraries would be when developing. I > think it would be great if I could unload a plugin library completely so I > can install and load a new version without restarting licq entirely each > time I test something. > This would mostly be useful when developing but it would be a nice feature > for users as well to able to upgrade plugins without going offline. I have seen the light and I'm now all for unloading :) // Erik -- This message has been ROT-13 encrypted twice for extra security. Erik Johansson http://ejohansson.se
pgph7UyBNWtyJ.pgp
Description: PGP signature
