In the cases of big changes like the progress indicator for loading, it may not be possible to maintain compatibility with a reasonable amount of effort, but in those cases we should at least keep track of the incompatibilities so that we can summarize them for plugin programmers at the next release.
I agree in principle but in some cases we're still ot clear what is and is not the API for plug-in developers. There is much that we we should be free to change without such effort. For these examples you are right though. The model interface is quite clearly defined. The persistence API less so but the classes you list are obvious candidates. Should we keep some document for this in CVS to update as required. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
