Re: [xwiki-devs] [Gsoc-2009]-Integration of Mozilla Bespin as a core Script editor in XWiki

Hello Harsha, Harsha Halgaswatta wrote: Currently the skin editor only colors HTML for velocity templates. It would be good to add a colors for velocity statements, too. Groovy coloration is a good idea. But more important will is first to write a syntax coloration engine for XWiki syntax 2.0 (http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax). Ideally the engine should be use other engines to color the content of some macros, for example : = Heading level 1 // <-- this is wiki syntax, it should have its own coloration == Heading level 2 {{html}} // <-- the content of this macro is colored with the html coloration engine <form> <div> // etc... </div> </form> {{/html}} {{groovy}} // <-- content colored with the groovy engine. def a = "foo" {{/groovy}} About coloration, you can read this post http://www.rsaccon.com/2009/03/porting-codemirror-syntax-parser-to.html. It is likely going to be the default highlighting engine in future versions of Bespin. Another idea would be to write a simple XWiki Syntax 2.0 parser in JavaScript. This would allow very cool features like collapse/expand macros, outline views, jump to section, etc. The integration has been done with a very early version of Bespin (bespin 0.1.1), and it is a clearly a hack, not a clean integration. If you want to see how it's made, you can install the skin editor on a XWiki Enterprise instance, all the integration code is located in wiki documents (or JS / CSS extensions objects, see http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial). Now with more recent versions of Bespin it is a lot easier and no longer hackish to make that integration. The bespin team has made the editor being instanciable, see http://almaer.com/blog/embedding-and-reusing-the-bespin-editor-component. Your proposal should demonstrate your understanding of how the integration can happen in XWiki - both from a features point of view (what will it offer exactly ?), and from a technical/architecture, point of view (how is this going to be done). For this project to be a success, the student will very likely have to communicate with the communities (XWiki, and Bespin), it's additional work that one should have in mind from the start of the project. Regards, Jerome