[opencms-dev] XML/XSLT and structured editor

[Niklas Eklund]

If anyone is looking for applet editors, the link below could be worth 
checking out. The code is old but try the demos, good stuff...
http://openlab.jp/kyasu/

Regards,
  Niklas

Kenneth Lewelling wrote:
> On a related note, I ran across this project the other day. Not sure if
> anyone
> has taken a look at it. Its an HTML editor, something that could replace
> the current active x control used. It's written in java and can be run as an
> applet or standalone application.  http://www.hexidec.com/ekit.php
> 
> Kenneth
> 
> -----Original Message-----
> From: owner-opencms-dev at www.opencms.org
> [mailto:owner-opencms-dev at www.opencms.org]On Behalf Of Niklas Eklund
> Sent: Monday, December 30, 2002 2:03 PM
> To: opencms-dev at www.opencms.org
> Subject: Re: [opencms-dev] XML/XSLT and structured editor
> 
> 
> Anil,
> Thanks, I'll take a look in that file.
> The textarea will do fine for me for source editing, hopefully I won't
> have to use it at all when I'm done replacing the other editor :)
> Just curious though, do you run JEdit as an applet or standalone?
> 
> Regards,
>   Niklas
> 
> Anil Patel wrote:
> 
>>Niklas,
>>There is a file corresponding to all the supported resource types in
>>OpenCMS in the following folder
>>"\etc\ocsetup\vfs\system\workplace\restypes"
>>This file is used to prepare Context menu for each resource. Search for
>>"edit" keyword in this file and you should be able to figure out rest of
>>story.
>>Some time back I posted my work on JEdit based Source editor for
>>OpenCMS. This editor has syntex highlight for some source types, If this
>>is something you may wnat?
>>Regards
>>
>>
>>
>>
>>
>>
>>>From: Niklas Eklund <niklas at curalia.se>
>>>Reply-To: opencms-dev at www.opencms.org
>>>To: opencms-dev at www.opencms.org
>>>Subject: [opencms-dev] XML/XSLT and structured editor
>>>Date: Mon, 30 Dec 2002 12:53:29 +0100
>>>
>>>Hi all,
>>>
>>>I'd like to use XSL to transform XML instead of (or rather concurrent
>>>with) the template system used now. I have made a simple test by
>>>adding a master template and a java-class which gets hold of the body
>>>and then transforms it. Is there another better aproach? My goal is to
>>>have Cocoon do all page rendering to the client in the future...
>>>
>>>Also, on the editor side, I'd like to substitute the HTML-editor
>>>alltogether and have a simpler form-based editing solution. The
>>>reasons for this are to allow more structured pages (ie not just one
>>>big "textarea" per page but rather have x fields - heading,
>>>subheading, text etc depending on the page template) and not allow so
>>>much custom HTML. How would I go about replacing the HTML editor while
>>>still keeping the source-editor (so I can still edit stuff when my
>>>code is broken)? I have read somewhere about multiple bodies but
>>>haven't seen any examples of how to use it, could that maybe help me?
>>>
>>>Regards,
>>>
>>>  Niklas
>>
>>
>>
>>_________________________________________________________________
>>Add photos to your messages with MSN 8. Get 2 months FREE*.
>>
> 
> http://join.msn.com/?page=features/featuredemail&xAPID=42&PS=47575&PI=7324&D
> I=7474&SU=
> 
> http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_addphotos_3
> mf
> 
>