17452 Posts in 4473 Topics by 1971 members
|Go to End|
24 August 2007 at 6:55am
meaby you can use it for SS in the future.
25 August 2007 at 3:18pm
in that demo I didnt see a way to make headings etc. That might be a problem and seeing the 'size' field brought back horrible <font size="+2"> memory's
Google Summer of Code Hacker
26 August 2007 at 12:52pm
If you are considering a new WYSIWYG why not look at YUI Rich Text Editor ? which also comes with BSD license.
Also features of it seems to mix well with the new CMS concepts of Silverstripe.
Have a look : http://developer.yahoo.com/yui/editor/
26 August 2007 at 8:52pm
YUI components generally look pretty solid and well documented.
like lakshan said, integration makes more sense on a broader level - otherwise you're just introducing a massive new codebase for one feature. I could think of tabs, windows, tree, context-menu, lightbox, ...
- more solid CMSMain.js replacement
- consistent coding for most of our js-needs
- well documented & active community
- actively developed
- tested on multiple browsers
- consistent skinning support
- lots and lots of integration work & testing for silverstripe
- overlapping featureset with prototype/scriptaculous
- customizations needed?
RTEs are a pain in the ass to write and maintain, so unless there's a compelling reason to switch, i'd stay with TinyMCE for now. i'm not saying we should switch to YUI right away either (too much work?), just getting the discussion going.
17 November 2007 at 5:45am
First, Sorry for my bad english
I am thrilled by the CMS and have already provided the forum and would ransacks for this thread also a proposal
Open Source Licenses
The editor is distributed under the GPL, LGPL and MPL open source licenses. This triple licensing model avoids incompatibility with other open source licenses, making it possible to integrate FCKeditor whenever you want.
|Go to Top|