|
From: <Bra...@ca...> - 2003-08-18 01:23:37
|
If you can find a LGPL framework that works on IE and Mozilla (or close too it with some tweeks) then I would be willing to wrap it in an EchoPoint component The trick is to get something that has a "quasi" JavaScript API. Otherwise it gets very hard to have a component layer that "magically" produces very specific JS setup. I learnt this with the Milonic Menu library that I wrapped whihc doesnt really have a JS API but rather you create array structures in "just the right format" so it just works. This proved a lot harder than I had thought it would. Cheers Brad Baker ---------------------------------------------------------------------------------------- Email : bra...@ca... Mobile: 0418-642-341 ---------------------------------------------------------------------------------------- |---------+--------------------------------------------------> | | Thomas Hentschel Lund | | | <th...@tr...> | | | Sent by: | | | ech...@li...| | | ceforge.net | | | | | | | | | 16/08/2003 06:31 PM | |---------+--------------------------------------------------> >-----------------------------------------------------------------------------------------------| | | | To: ech...@li... | | cc: | | Subject: [EchoPoint] Editor Component | >-----------------------------------------------------------------------------------------------| I was wondering if anyone was working on a WYSIWYG editor component? I am thinking along the lines of this: http://www.p42.net/dhtmleditor/demos/demo14.html (license is payware for commercial projects, free for private) or this: http://www.kevinroth.com/rte/demo.htm (GPL) See a larger list here: http://www.bris.ac.uk/is/projects/cms/ttw/ttw.html There are tons of these editors, and I would love to have one available for echo, but I'm one of the "fortunate" people with lots of projects and little time to do things myself. I would expect such editor to be very very _very_ usefull for a lot of ppl. It could either be implemented by embedding one of the existing LGPL/GPL javascript editors as a component and then for viewing use a component that embeds the HTML that comes out of the editor. The other way would be to rewrite the output of the editor from HTML to a panel/pane (if at all possible). There would be persistance problems with the latter approach I would suspect. So it would maybe involve writing a data format descriptor that could be saved in a database - which again would make it easier to just use the HTML in the first place. Any other ideas or comments? /Thomas ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Echopoint-list_listnam mailing list Ech...@li... https://lists.sourceforge.net/lists/listinfo/echopoint-list_listnam |