Hi Vincent, Vincent Massol wrote: Let me explain a bit what I'd like to do. The current wysiwyg module contains a lot of reusable code. In the process of externalizing the editor from XWiki I'd like to start by extracting all this reusable code and place it in dependency modules. After this stage we could have: platform/web/ |_ standard/ |_ xwiki-gwt-api/ (reusable only inside XWiki) |_ xwiki-gwt-diff/ (reusable outside XWiki) |_ xwiki-gwt-dom/ (reusable outside XWiki) |_ xwiki-gwt-user/ (reusable outside XWiki) |_ xwiki-gwt-wysiwyg/ (only WYSIWYG specific code + plugins) Next I'll look for a solution to load WYSIWYG editor plugins dynamically. Right now there's no straightforward approach to do this because GWT doesn't support reflection. As a consequence we can't separate the plugins from the editor because we have a cyclic dependency. I'll have to use a trick most probably to decouple them. If I succeed we could have: platform/web/xwiki-gwt-wysiwyg/ |_ xwiki-gwt-wysiwyg-api/ (reusable outside XWiki) |_ xwiki-gwt-wysiwyg-plugins/ |_ xwiki-gwt-wysiwyg-plugin-color/ (reusable outside XWiki) |_ xwiki-gwt-wysiwyg-plugin-link/ (XWiki specific) |_ (other plugins here) At this point the plugins should be self contained. Regarding this, I'm currently changing the macro plugin to use its own service (MacroService) which is a pure component. The diff module is reusable. I doubt there will be soon another code using it besides the sync plugin. We could move it inside the sync plugin but I prefer moving it outside of the wysiwyg module. WDYT?