[xwiki-devs] [Proposal] Move WYSIWYG DOM API in a separate module
Hi devs, The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding: * W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?). Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom. WDYT? Marius
Marius Dumitru Florea wrote:
Hi devs,
The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding:
* W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods
I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?).
Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom.
WDYT?
+1 Another option is to push this into GWT, but this will not be viable for us in the short run, since it will take time until it appears inside a released GWT version. At some later time, we could simply drop this dependency once GWT provides all that we need. -- Sergiu Dumitriu http://purl.org/net/sergiu/
+1 we should also make the editor itself a separate module Ludovic Marius Dumitru Florea a écrit :
Hi devs,
The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding:
* W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods
I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?).
Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom.
WDYT? Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
+1 also as Sergiu said this should go to GWT at some point but we can't to this now I guess On Mon, Mar 16, 2009 at 16:50, Marius Dumitru Florea <[email protected]> wrote:
Hi devs,
The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding:
* W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods
I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?).
Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom.
WDYT? Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 and +1 for proposing it to gwt. Also, we should start thinking more seriously (as in roadmap seriously) about making the whole editor "standalone". Happy coding, Anca Luca Marius Dumitru Florea wrote:
Hi devs,
The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding:
* W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods
I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?).
Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom.
WDYT? Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1, JV. On Mon, Mar 16, 2009 at 4:50 PM, Marius Dumitru Florea <[email protected]> wrote:
Hi devs,
The new WYSIWYG editor uses an enhanced DOM API to manipulate the edited document. This API extends the default DOM API found in GWT adding:
* W3C Range and Selection support ( http://tinyurl.com/cvsm3a ) * Multiple-window support ( http://tinyurl.com/cphdep ) * Depth-first pre-order iterator (part of Document traversal support) * Lots of DOM utility methods
I'd like to move this API in a separate build module to make it reusable inside and outside XWiki. We could name it xwiki-web-gwt-dom (or xwiki-gwt-dom?) and place it, at list for now, in platform/web/gwt-dom (or platform/web/xwiki-gwt-dom?).
Also, I'd like to rename the package name from com.xpn.xwiki.wysiwyg.client.dom to org.xwiki.gwt.dom.
WDYT? Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (6)
-
Anca Paula Luca -
Jean-Vincent Drean -
Ludovic Dubost -
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne