Issue #SCB2738 () Addon Wiki features

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 01/01/2009 13:54

  *Reasons for the changes*


  *Comments*
  - By Hussayn Dabbous - 01/01/2009 13:54 ---
  "@Mick: I also vote for (1) in the short term and (3) in the short term, becasue we can have both more or less out of the radeox-box. I meanwhile contacted the main radeox developer and he answered, that there is common interest in re-awaking radeox. we are currently discussing the best way to go to bundle interests and resources. As i reported in an email earlier today, the radeox-1.0-b3 release (available at http://svn.codehaus.org/radeox/main/trunk ) has got a lot of Creole-1.0 allready implemented. There are basically 3 creole-options missing: 

* tables
* {{{comments}}}
* external links

Although there is a non standard mechanism implemented in radeox for all three aspects... 
I tested all this in my development system and i have reached most of my goals almost for free.

So here is my current tasklist for this issue:

1.) switch to radeox-1.0-b3 (allready done in my development system)
2.) Add missing creole-1.0 support as pointed out above (I started on that, preparing to give it to radeox, when it wakes up)
3.) Release that to Scarab and tell the world we are creole-1.0 compliant.

Basically i needed to change 2 lines of code in Scarab and switch to radeox 1.0-b3. 
I will have to add some new radeox filters (fully decoupled from Scarab) to achieve 
the full standard creole though. But the benefit would be, that we would have 
introduced a creole-1.0 compliant wiki syntax. (Good for the marketing ;-)

4.) I would wait for a moment before we go to check xwiki and the rest. Maybe we don't need that.
Maybe it is a good idea instead to start some work on a configurable "renderingEngineService", so we could
prepare an integration API for that purpose. That sounds a good way to go. Then people can integrate 
engines as needed (if needed) ..."

  - By Hussayn Dabbous - 01/01/2009 13:55 ---
  "@Mick: I also vote for (1) in the short term and (3) in the short term, becasue we can have both more or less out of the radeox-box. I meanwhile contacted the main radeox developer and he answered, that there is common interest in re-awaking radeox. we are currently discussing the best way to go to bundle interests and resources. As i reported in an email earlier today, the radeox-1.0-b3 release (available at http://svn.codehaus.org/radeox/main/trunk ) has got a lot of Creole-1.0 allready implemented. There are basically 3 creole-options missing: 

* tables
* {{{comments}}}
* external links

Although there is a non standard mechanism implemented in radeox for all three aspects... 
I tested all this in my development system and i have reached most of my goals almost for free.

So here is my current tasklist for this issue:

1.) switch to radeox-1.0-b3 (allready done in my development system)
2.) Add missing creole-1.0 support as pointed out above (I started on that, preparing to give it to radeox, when it wakes up)
3.) Release that to Scarab and tell the world we are creole-1.0 compliant.

Basically i needed to change 2 lines of code in Scarab and switch to radeox 1.0-b3. 
I will have to add some new radeox filters (fully decoupled from Scarab) to achieve 
the full standard creole though. But the benefit would be, that we would have 
introduced a creole-1.0 compliant wiki syntax. (Good for the marketing ;-)

4.) I would wait for a moment before we go to check xwiki and the rest. Maybe we don't need that.
Maybe it is a good idea instead to start some work on a configurable "renderingEngineService", so we could
prepare an integration API for that purpose. That sounds a good way to go. Then people can integrate 
engines as needed (if needed) ..."

  - By Hussayn Dabbous - 01/01/2009 13:54 ---
  "@Mick: I also vote for (1) in the short term and (3) in the short term, becasue we can have both more or less out of the radeox-box. I meanwhile contacted the main radeox developer and he answered, that there is common interest in re-awaking radeox. we are currently discussing the best way to go to bundle interests and resources. As i reported in an email earlier today, the radeox-1.0-b3 release (available at http://svn.codehaus.org/radeox/main/trunk ) has got a lot of Creole-1.0 allready implemented. There are basically 3 creole-options missing: 

* tables
* {{{comments}}}
* external links

Although there is a non standard mechanism implemented in radeox for all three aspects... 
I tested all this in my development system and i have reached most of my goals almost for free.

So here is my current tasklist for this issue:

1.) switch to radeox-1.0-b3 (allready done in my development system)
2.) Add missing creole-1.0 support as pointed out above (I started on that, preparing to give it to radeox, when it wakes up)
3.) Release that to Scarab and tell the world we are creole-1.0 compliant.

Basically i needed to change 2 lines of code in Scarab and switch to radeox 1.0-b3. 
I will have to add some new radeox filters (fully decoupled from Scarab) to achieve 
the full standard creole though. But the benefit would be, that we would have 
introduced a creole-1.0 compliant wiki syntax. (Good for the marketing ;-)

4.) I would wait for a moment before we go to check xwiki and the rest. Maybe we don't need that.
Maybe it is a good idea instead to start some work on a configurable "renderingEngineService", so we could
prepare an integration API for that purpose. That sounds a good way to go. Then people can integrate 
engines as needed (if needed) ..."

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=998377

To unsubscribe from this discussion, e-mail: [[email protected]].