Re: the future of radeox ...

Hi, all;

As some of you might already know, there is a new standard for 
wiki-syntax creeping up the walls,
named Creole-1.0. While i was researching about what sort of 
Wiki-related enhancements could be
good add ons for Scarab, i found out, that it wouldn't be a bad option 
to make Scarab standard
conform in that sense.
So i did some more work on radeox, i even hunted for the sources and 
found them at the end. I also
talked to the author, then i patched radeox a bit and now i have 
something, that is near enough to the
standards, so that IMHO it can be released to radeox (i am currently 
negotiating with Stephan Schmidt,
the original author).
Atr the meantime, i have updated the Scarab-Selfhost and now you can see 
Creole-1.0 in action in the
Scarab-comments section ;-)

Well, at the moment there is not really much to see, but you can at 
least get a glance on what is possible
when looking at this issue here: 
http://www.solitone.org/scarab/issues/id/SCB2738

We will update the css-files shortly so that the markup will come out 
nicely and well conformant to our
own GUI.

BTW: The radeox-built-in functionality is not broken, so those of you, 
who allready use that functionality
in your own projects, can relax. Nothing damaged!

Any feedback is welcome (as always ;-)

Happy new year, thanks, regards,
Hussayn

Hussayn Dabbous wrote:
> Hi,
>
> What shall we do with radeox now ? The project is definitively dead.
> The website is down, documentation is close to zero. After some 
> searching on the
> web  i finally found sources at codehaus,  labeled with radeox-1.0-b3
>
> http://svn.codehaus.org/radeox/main/trunk
>
> This apparently last version of radeox contains some Creole-1.0
> development (a try to unify the wiki languages of the world, see
> http://www.wikicreole.org/ ), but it is not complete.
>
> I have checked out the sources and replaced the radeox-1.0-b2 by the
> new version and tested it. It works great so far. This is what i checked
> in my development instance of Scarab concerning creole-1.0 syntax:
>
> 1.) fully supported syntax:
>
> //italics//
> **boldface**
> * bullet list
> * second item
> ** sub item
>
> # numbered list
> # second item
> ## sub item
>
> == large heading
> === medium heading
> ==== small heading
>
> force\\linebreak
>
> ----  (horizontal line)
>
> 2.) not supported, or not fully supported:
>
> [[externalWiki|wikiPage] ]  (cross wiki links for many of the existing 
> wikis in the web)
> [[anyURL]] (link to an external resource)
> [[anyURL|renderingName]] (link to any external resource)
> {{Image.jpg|title}} (image with subtitle)
>
> |=|=table|=header|
> |a|table|row|
>
> {{{ text will not be marked up }}}
>
> ====================
>
> Now the question is, where to go next.
>
> The code is clean, but there is almost no documentation available on the 
> net.
> The snipsnap documentation covers some aspects, but since snipsnap seems 
> also
> to be dead, this is not convenient.
>
> We could decide to do our own radeox fork, name it "scarabeox" or something
> and continue the developing, make the thing creole-1.0 compatible and use it
> inside scarab.
>
> We also could decide to replace radeox, but then which replacement would 
> be convenient ?
> For further dicussion on possible replacements see the comments section 
> of my issue
> http://www.solitone.org/scarab/issues/id/SCB2738
>
> For now i will start my private fork of radeox, implement creole-1.0 and 
> consider adding it
> as new project "scarabeox" into the tigris repository. (the name sounds 
> good to me ;-)
>
> a happy new year and a good start to all of you
>
> regards,
> Hussayn
>
>   


-- 

SAXESS Software Design GmbH
Neuenhöfer Allee 125
D-50935 Köln

Dr. Hussayn Dabbous

Fon: 0049 (0)221 56011 0
Fax: 0049 (0)221 56011 20

http://www.saxess.de
http://www.cinemacchiato.com
http://blog.machinimatrix.org
-----------------------------

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

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