Thanks,
Maxence
I think what plugin features is best. develop plugins is simplest and
I see many plugins for mucommander.
search as plugin, integration plugins (svn for example), custom views
as plugin and any.
But current ExtensionManager engine is little incorrect because many
plugins to be work with conflict of namespacing in JVM. I propose
solution where any plugin (jar) will be use your ClassLoader
Thanks
> I think what plugin features is best. develop plugins is simplest and
> I see many plugins for mucommander.
> search as plugin, integration plugins (svn for example), custom views
> as plugin and any.
Agreed, a plugin system is badly needed. Nicolas and I have been
discussing it but didn't get to it simply for the lack of time.
Defining an interface for plugins is not all that complicated but
needs to be carefully thought out to avoid having to change it down
the road and break existing plugins.
> But current ExtensionManager engine is little incorrect because many
> plugins to be work with conflict of namespacing in JVM. I propose
> solution where any plugin (jar) will be use your ClassLoader
I'll let Nicolas answer that, I remember discussing this particular
issue with him and I think he had planned about this.
Cheers,
Maxence