Hi

On Thu, 02 Nov 2006 13:02:00 -0500 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:

If I have a look at the code proposed for the new designer, I find some issues we must address:

• handling of the needed additions to pmadb

We don't handle creating of pmadb either (but we should allow this in setup).

• handling of additional configuration parameters for the plugin

Hook in config.default?

• integration of the new messages (to stay easy to translate)

Messages need to be separate, maybe support for additionally loading file from extension/lang/... matching current language?

• integration of the new images

Images are not a problem, but there might be problem with themes...

Sorry to ask more questions than offering answers. Also, I'm not sure if the plugin interface would be popular enough, or would be general enough to accept other people's code. AFAIK we did not get any contributions for transformations, export or inport, but maybe a plugin interface can help improve the structure.

All those parts now allow only dropping file in place and it will work. The only problem is lack of documentation. I started to write something about export/import in wiki, but it is far from being complete...

Hi

On Fri, 03 Nov 2006 08:17:51 -0500 Marc Delisle Marc.Delisle@CegepSherbrooke.Qc.Ca wrote:

I see the plugin interface as long-term. For short-term we have this piece of code (designer) and we could benefit from merging it, but it obviously was not written in order to respect our future plugin interface :)

Yes, merging designer and designing plugin interface are two different things. Anyway we should look on designer as one possible user of plugin interface and it should be possible to integrate it using this interface (even if we won't do it this way). Just to make interface usable for real life applications.