A good while ago we seemed to agree that the name "plugin" is not a good name. It creates considerable confusion for people new to Wookie as it seems to imply that it is a way of plugging in functionality to Wookie. In fact it is about creating plugins for other platforms so they can work with Wookie widgets.

On the other hand, from the point of view of the finished code they are indeed plugins (just not for Wookie).

With my proposal to create frameworks for different languages to allow easy plugin development this problem becomes more accute. We will have code in our repository that refers to plugins.

I've started hacking a Java implementation of my framework proposal. in this work I have used the package name:

org.apache.wookie.connector.framework

The idea is we can say something like "To implement a plugin for your preferred environment select the appropriate connector framework for your programming language and implement the IWookiePluginService class."

Comments/thoughts on this?

Ross

Reply via email to