Re: [xwiki-devs] XEM review

2007-09-11 Thread Thomas Mortagne
I also have to modify XEM to be based on XWiki Plateform 1.1 in place of 1.2. 2007/9/11, Thomas Mortagne [EMAIL PROTECTED]: 2007/9/10, Vincent Massol [EMAIL PROTECTED]: Hi Thomas and everyone, I've started reviewing the XEM code in SVN in preparation for the 1.0M1 release for the 17th

[xwiki-devs] [Discussion] Designing the new Rendering/Parsing component/API

2007-09-11 Thread Vincent Massol
Hi, I've started working on designing the new Rendering/Parsing components and API for XWiki. The implementation will be based on WikiModel but we need some XWiki wrapping interfaces around it. Note that this is a prerequisite for the new WYSIWYG editor based on GWT (see

Re: [xwiki-devs] [Discussion] Designing the new Rendering/Parsing component/API

2007-09-11 Thread Vincent Massol
On Sep 11, 2007, at 6:36 PM, Jean-Vincent Drean wrote: Two possible solutions: 1. Have a WikiSyntax Object (A simple class with one property: a combox box with different syntaxes: XWiki Legacy, Creole, MediaWiki, Confluence, JSPWiki, etc) that users can attach to pages to tell the

Re: [xwiki-devs] [Proposal] Improve installer to include database setup

2007-09-11 Thread David Ward
Vincent, I'm not sure if this is the email you were referring to. For Curriki, I think as long as there is an easy (and constant) way to add the driver and configuration to the war via a script (such as unjar, copy files, jar) then this sounds fine to me. Right now this is how the xwiki.cfg,