Hi Christophe, the template stuff is something that came to my mind, too, already. The result is a bit like Lotus Notes/Domino, a document-oriented database (nowadays one would name it NoSQL): Fields which contain (editable) data and the template providing the non-editable surroundings. However, I think Janne is right, this is quite a bit away from what a Wiki is.
Reading your next lines, I wonder where you're still using wiki markup in that application. Wouldn't it be best to either customize the JSPs (i.e. creating a new "template", already today!), or, going one step further, creating a new webapp and embed JSPWiki functionality into the places you need wiki markup? IMO, crucial JSPWiki future topics are: * explicitly defining the wiki markup syntax (and its transition rules to xhtml) * explicitly defining a wiki name syntax * a backend which supports proper metadata (Probably JCR is best here, but not necessarily. The essential thing is a fast and lean backend implementation which also supports simple file storage.) * a rendering engine which supports many input formats at once (i.e. page-wise), based on a MIME type provided via a page's metadata Any opinions on this? Regards Florian PS: I'm sure you can be saved from switching to PHP ;-) On 05.11.2012 09:33, Christophe Dupriez wrote:
Hi JspWikiMakers! About plugin API, I rather agree with the approach "those who follow, will follow reasonable changes in the good direction". The other will stay with what they have. What is important is to not forget those changes in the Release Notes! Thinking to this and: 1) the problem I have recommending customers to integrate Schema.org support (HTML5 Microdata; passive SEO where all necessary metadata is added) and JspWiki (and many others) not really supporting it; 2) the problem I have with CK editor where Wiki->XHTML and back is not 100% faithful (especially with plugins parameters containing special characters like "%": I solved most other issues), I am wondering when (AFTER 2.9) / where this could be discussed. I would dream of a JspWiki 3.0 (to which I would be willing to contribute) where: 1) we would split current WikiMarkup content in Templates and "fields content": Templates would be "free" HTML with possibility to include plugins Fields content would be text, numbers, dates (etc: pluggable field content widgets/validators/marshaller/unmarshaller) or XHTML (CK editor) without the possibility to call plugins 2) Template pages could be instanciated in actual pages where different fields would be dynamically included. Page headers would also have access to fields content to fill metadata headers. For a given Wiki, a "power user" (knowing HTML 5) could create the necessary templates and the "regular" users would be much more confortable: only validated text, CK edited text, numbers, dates, etc. to fill up in a form. Am I stupid or current JSPs of JSPWiki are the templates I am dreaming of? What about the different fields in a single page then? ... the different page types? ... the different field types? This for me to investigate: any suggestions/examples very welcome! Jane already declared XHTML content would be something else than JspWiki. It is true that it begins to look like a collaborative CMS. What do you think? Have a nice day! Christophe P.S. It is told to me that Drupal is just like that. I do not want to switch to PHP!!! Le 5/11/2012 07:23, Florian Holeczek a écrit :Hi all, short answer from me: +1 for generics -1 for 2.9.0 +1 for a JIRA issue on this topic (FixVersion 2.9.1) with a good heading and description, in order to let people explicitely know about the change. BTW: I remember Janne's work on an API - is that still in people's heads? @Ichiro: Where will you publish that stuff? I guess it will be under an LGPL license? I always think it's a pity that there are many JSPWiki plugins out there, but they're quite hard to find. WDYT of some kind of extension gallery for JSPWiki, partly with links, partly with the possibility of hosting the code itself, for example apache-extras, google code or so? Regards Florian PS @Juan Pablo: Have fun at ApacheCon! Wish I was there too, but there was no possibility this time to go there.
