On Mar 23, 2009, at 8:49 AM, Marius Dumitru Florea wrote:
Hi Anca,
Anca Paula Luca wrote:
mflorea (SVN) wrote:
Author: mflorea Date: 2009-03-20 19:48:20 +0100 (Fri, 20 Mar 2009) New Revision: 17880
Added: platform/web/trunk/wysiwyg/src/test/java/com/xpn/xwiki/wysiwyg/ client/widget/MockEvent.java platform/web/trunk/xwiki-gwt-dom/
actually, could we have this just gwt-dom ? for consistency with the others module names.
I thought it's consistent with: http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwiki...
I replaced "core" with "web" and "rendering" with "gwt".
We could also think about putting it under gwt in this case, but the truth is that that one should be renamed into xwiki-gwt since that one is xwiki specific API and this one is generic.
Yes, I had in mind: platform/web/xwiki-gwt/xwiki-gwt-dom but I said to myself that we should wait till we have more than one module to put inside xwiki-gwt. Also note that xwiki-rendering is pretty generic and still prefixed with xwiki. I think it's good like this.
I could have moved/renamed the gwt module to platform/web/xwiki-gwt/xwiki-gwt-api but I wanted to know first how is this move going to affect the projects using it, like Curriki.
My target is something like:
platform/web/xwiki-gwt /xwiki-gwt-api (the current gwt module) /xwiki-gwt-diff (used for real-time editing) /xwiki-gwt-dom /xwiki-gwt-rta (the rich text area used by the WYSIWYG) /xwiki-gwt-wysiwyg
Sounds good to me as a first step. The following step would be to move some modules to top level project status. Thanks -Vincent