Re: [xwiki-devs] Running wysiwyg GWT editor as standalone

Thanks for the information this was helpful Regards, Fady On Fri, Feb 19, 2010 at 5:43 PM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com&gt; wrote: > Hi Fady, > > So far we haven't written a demo of the WYSIWYG editor outside of XWiki > but it shouldn't be hard to write one: > > * Create a demo GWT-Maven project > * Add a dependency on xwiki-web-gwt-wysiwyg-client ( > > http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/xwiki-gwt-wysiwyg-cli… > ) > * Inherit the WYSIWYG GWT module in your own GWT module descriptor > ** Use the same entry point as the WYSIWYG GWT module, which publishes a > JavaScript API you can use to instantiate the editor, or > ** Use your own entry point and instantiate the editor in GWT code > > The only limitation is that you won't be able to use the > "switch-to-source" feature (i.e. the tabbed version of the editor) and > XWiki-specific plugins (link, image, macro and importer) unless you > implement the GWR-RPC services currently implemented in > > http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/xwiki-gwt-wysiwyg-ser… > . > > If you choose to use the same entry point, the JavaScript API that is > being publish is described at > > http://code.xwiki.org/xwiki/bin/view/Modules/WysiwygEditorModule#HWysiwygEd… > . You can find the configuration parameters at > > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/WysiwygEditor#HConfigur… > . Note that we have written a custom GWT script loader ( > > http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/xwiki-gwt-wysiwyg-cli… > ) which allows us to write: > > Wysiwyg.onModuleLoad(function() { > // code here > }); > > This way we know for sure that when we try to create a new WYSIWYG > editor the GWT module was loaded. The easiest way to create the editor > without the special loader is to use a button and to place the code on > click. > > Hope this helps, > Marius > > Fady Matar wrote: >> I'm aiming to run the wysiwyg component as a standalone GWT for a >> number > of >> reasons: >> 1. To be able to test the component without it being hooked up to XWiki >> 2. To be able to expand it or add more features to it as required. >> >> I would like to get all the possible assistance in achieving that task >> so > I >> can share it with others and probably update the documentation if it's >> beneficial to others. >> >> Cheers, >> Fady >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >