+1
Also it would be better to have all WYSIWYF project pure java (the one
not converted into javascript) in a jar project on which the the
WYSIWYG war project depends.
On Thu, Dec 11, 2008 at 3:50 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote:
Hi devs,
I'd like to suggest to move our current xwiki-web-gwt and
xwiki-web-wysiwyg modules from platform/web to platform/.
Rationale :
- Generic GWT modules to come (wiki-explorer, color picker, etc).
- xwiki-web would hold only fully functional WARs.
- WYSIWYG release cycle should be different from the one of web. This
would allow to benefit from WYSIWYG improvements in branch releases
(ex: XE 1.7.2, 1.7.3, etc) without requiring devs to commit on
multiple branches.
- A lot of issues regarding the wysiwyg editor are created in the
XWiki Core project in jira, I think having a dedicated project makes
sense.
Current organization :
|- platform/
|- web/ (xwiki-web)
|- exo/ (xwiki-web-exo)
|- gwt/ (xwiki-web-gwt)
|- standard/ (xwiki-web-standard)
|- wysiwyg/ (xwiki-web-wysiwyg)
New organization proposal :
|- platform/
|- gwt/ (xwiki-gwt)
|- commons/ (xwiki-gwt-commons)
|- wysiwyg/ (xwiki--gwt-wysiwyg)
|- web/ (xwiki-web)
|- exo/ (xwiki-web-exo)
|- standard/ (xwiki-web-standard)
This would also mean that we'd need 2 new projects in JIRA :
XWiki GWT Commons (XGCOMMONS) and XWiki GWT WYSIWYG (XGWYSIWYG).
Here's my +1.
Thanks,
JV.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne