Update: working on wiki

[Nicola Ken Barozzi <ni...@apache.org>]

In my quest to making it easy for users to edit pages in Forrest, I have 
committed the possibility for users to use html pages as content with 
*.ihtml .

I just wanted to let you know that I'm finishing the same thing with the 
wiki-like format in chaperon, so that all *.cwiki files can be processed 
in a similar fashion.

The wiki editor is working on my system, I just need to finish a couple 
of things.

As for the *.ihtml, if we put an applet in the editor we can quite 
easily edit those pages via webapp too. On my system I have made an 
addition to the forrestbar that opens the file in composer, but it 
cannot yet publish to ftp... so I made it resolve the real system path 
of the file, but then again I had to hardcode things...

...just to let you know what I'm doing.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------

Re: Update: working on wiki

[Nicola Ken Barozzi <ni...@apache.org>]

Nicola Ken Barozzi wrote:
> 
> In my quest to making it easy for users to edit pages in Forrest, I have 
> committed the possibility for users to use html pages as content with 
> *.ihtml .
> 
> I just wanted to let you know that I'm finishing the same thing with the 
> wiki-like format in chaperon, so that all *.cwiki files can be processed 
> in a similar fashion.

Done on my system... and I get  a nice exception if I edit a wiki file 
after viewing a wiki file, or the opposite... I'll wait to have it ixed 
before comitting, no?


java.lang.ClassCastException

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

stack-trace

java.lang.ClassCastException
	at 
org.apache.cocoon.transformation.TextFragmentParserTransformer.setup(TextFragmentParserTransformer.java:164)
...	



> The wiki editor is working on my system, I just need to finish a couple 
> of things.
> 
> As for the *.ihtml, if we put an applet in the editor we can quite 
> easily edit those pages via webapp too. 

I have found only this which is prebuilt http://www.hexidec.com/ekit.php 
but it's LGPL.

Do others have other possibilities? Someone wants to fix up a small html 
editor in Swing?

On my system I have made an
> addition to the forrestbar that opens the file in composer, but it 
> cannot yet publish to ftp... 

Or shall we add a ftp server for it?

> so I made it resolve the real system path 
> of the file, but then again I had to hardcode things...

Or let Cocoon give infos about the real paths of the source files via a 
cocoon-view?

> ...just to let you know what I'm doing.

and I've added svg processing to images, but still need to update the jar.

I'll commit ASAP, promise.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------

Re: Update: working on wiki

[Stefano Mazzocchi <st...@apache.org>]

Nicola Ken Barozzi wrote:
> 
> In my quest to making it easy for users to edit pages in Forrest, I have 
> committed the possibility for users to use html pages as content with 
> *.ihtml .
> 
> I just wanted to let you know that I'm finishing the same thing with the 
> wiki-like format in chaperon, so that all *.cwiki files can be processed 
> in a similar fashion.
> 
> The wiki editor is working on my system, I just need to finish a couple 
> of things.
> 
> As for the *.ihtml, if we put an applet in the editor we can quite 
> easily edit those pages via webapp too. On my system I have made an 
> addition to the forrestbar that opens the file in composer, but it 
> cannot yet publish to ftp... so I made it resolve the real system path 
> of the file, but then again I had to hardcode things...
> 
> ...just to let you know what I'm doing.
> 

Way cool. I really look forward to see it!

-- 
Stefano Mazzocchi                               <st...@apache.org>
--------------------------------------------------------------------