Issue #SCB2738 () Addon Wiki features
Hussayn Dabbous <[email protected]> Wed, 31 Dec 2008 19:51:00 +0100 (CET)
| Newsgroups | gmane.comp.java.scarab.issues |
|---|---|
| Message-ID | <[email protected]> |
Activity report on *Enhancement SCB2738 - Addon Wiki features* Scarab Link: http://www.solitone.org/scarab/issues/id/SCB2738 Module: Scarab Activity generated by Hussayn Dabbous ([email protected]) at 12/31/2008 19:43 *Reasons for the changes* *Comments* - By Hussayn Dabbous - 12/31/2008 19:45 --- "Ok, i did a search session about Wiki rendering engines and state of the art development. The list is below. We still do have 3 options here, which way to go: 1.) Just enable wiki syntax in comments and long texts. We keep Scarab features as they are. This will not be a true wiki, especially no additional "wiki pages" will be available. This is what we currently have to some extend using the radeox engine in the background. The enhancement would be to enable the full capabilities of a wiki rendering parser, so that we get ordered lists, numbered lists, tables, indentation, external links, images... 2.) Go for an embedded wiki engine. Thus we have the whole instrumentation for creating wiki pages within the Scarab context. We get all of the above plus the capability to create and maintain extra information pages (wiki pages) in the Scarab context. 3.) Go for an integrated Wiki engine. Thus the wiki engine is some external software (webapplication, or anything else). We simply provide a mechanism by which it gets easy to define the links to the pages of the integrated Wiki engine. So it becomes possible to write [blahbla] in the comment and end with a link to the blabla page of the integrated wiki. We would step out of the scarab context though. This could easily be combined with option 1.) So here are some tools i found on a web search: 1. Radeox: (actually i did NOT find much about radeox except some letters of intent) URL: Not found Radeox seems to be dead since one year. There was an announcemnet from the core developer about forking the project, but i could not find the fork. So i suspect, radeox development has fully stopped. I strongly favorize to count opn active projects, so i consider replacing radeox. So what alternatives do we have ? 2. bliki in a jar URL: http://matheclipse.org/en/Bliki_in_a_JAR . They claim to be able to render the wikimedia language. The project seems to be actively developed, but it is a fork from a GPL based project, so this aparently cant be used for Scarab. 3.) Wikimodel URL: http://code.google.com/p/wikimodel/ Interesting development. They support creole-1.0 and many other wiki-languages. This seems to be worth a secnd look. The usage license is apache-2.0. Caveat: It is a somewhat blowed up development, many features, many classes, maybe too complex ? 4.) T 4 Wiki Parser URL: http://web-tec.info/WikiParser/ A small parser. It comes in as an easy to use and easy to integrate thingy (only 2 java files). It supports Creole-1.0 "with some minor derivations". The License is basically open to use in any context (only restriction: The usage must be published somewhere) 5.) XWiki Platform URL: http://platform.xwiki.org/xwiki/bin/view/Main/ This seems to be a very sophisticated and well developed framework. I am still unsure, if this is extreme overkill. It sounds a bit like we could better embed Scarab into the xwiki framework than the other way ;-) they do support velocity templates. The license model is LGPL." - By Hussayn Dabbous - 12/31/2008 19:43 --- "Ok, i did a search session about Wiki rendering engines and state of the art development. The list is below. We still do have 3 options here, which way to go: 1.) Just enable wiki syntax in comments and long texts. We keep Scarab features as they are. This will not be a true wiki, especially no additional "wiki pages" will be available. This is what we currently have to some extend using the radeox engine in the background. The enhancement would be to enable the full capabilities of a wiki rendering parser, so that we get ordered lists, numbered lists, tables, indentation, external links, images... 2.) Go for an embedded wiki engine. Thus we have the whole instrumentation for creating wiki pages within the Scarab context. We get all of the above plus the capability to create and maintain extra information pages (wiki pages) in the Scarab context. 3.) Go for an integrated Wiki engine. Thus the wiki engine is some external software (webapplication, or anything else). We simply provide a mechanism by which it gets easy to define the links to the pages of the integrated Wiki engine. So it becomes possible to write [blahbla] in the comment and end with a link to the blabla page of the integrated wiki. We would step out of the scarab context though. This could easily be combined with option 1.) So here are some tools i found on a web search: 1. Radeox: (actually i did NOT find much about radeox except some letters of intent) URL: Not found Radeox seems to be dead since one year. There was an announcemnet from the core developer about forking the project, but i could not find the fork. So i suspect, radeox development has fully stopped. I strongly favorize to count opn active projects, so i consider replacing radeox. So what alternatives do we have ? 2. bliki in a jar URL: http://matheclipse.org/en/Bliki_in_a_JAR . They claim to be able to render the wikimedia language. The project seems to be actively developed, but it is a fork from a GPL based project, so this aparently cant be used for Scarab. 3.) Wikimodel URL: http://code.google.com/p/wikimodel/ Interesting development. They support creole-1.0 and many other wiki-languages. This seems to be worth a secnd look. The usage license is apache-2.0. Caveat: It is a somewhat blowed up development, many features, many classes, maybe too complex ? 4.) T 4 Wiki Parser URL: http://web-tec.info/WikiParser/ A small parser. It comes in as an easy to use and easy to integrate thingy (only 2 java files). It supports Creole-1.0 "with some minor derivations". The License is basically open to use in any context (only restriction: The usage must be published somewhere) 5.) XWiki Platform URL: http://platform.xwiki.org/xwiki/bin/view/Main/ This seems to be a very sophisticated and well developed framework. I am still unsure, if this is extreme overkill. It sounds a bit like we could better embed Scarab into the xwiki framework than the other way ;-) they do support velocity templates. The license model is LGPL." ------------------------------------------------------ http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=997107 To unsubscribe from this discussion, e-mail: [[email protected]].