[
https://issues.apache.org/jira/browse/JSPWIKI-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772540#action_12772540
]
Lisa Simpson commented on JSPWIKI-450:
--------------------------------------
Considering that their website says (http://ckeditor.com/license) that they're
licensed under all 3 specifically to accommodate open source projects, I don't
think they'd have a problem working with you if you approached them about how
to handle it.
TinyMCE might be another option for you. WordPress and others use it instead
of FCKEditor. WordPress has an awesome control-panel management for what
appears in the TinyMCE toolbar.
HTMLArea is another one.
Spaw is relatively new but might work for you as well-
http://www.solmetra.com/en/disp.php/en_products/en_spaw/en_spaw_download
> Built-in WYSIWYG editor
> -----------------------
>
> Key: JSPWIKI-450
> URL: https://issues.apache.org/jira/browse/JSPWIKI-450
> Project: JSPWiki
> Issue Type: New Feature
> Components: Editors
> Reporter: Janne Jalkanen
>
> It would be really nice to ship with a built-in WYSIWYG editor. While we do
> have very nice FCK editor integration, unfortunately licensing reasons forbid
> us from distributing it with JSPWiki.
> (FCK is triple-licensed, GPL, LGPL and MPL. Out of these, only MPL can be
> included in binary form - and since FCK is Javascript, there is no binary
> form. More information at http://www.apache.org/legal/3party.html).
> No target set, but a volunteer would be nice. One option would be to somehow
> ensure that FCK is only distributed in binary form (as a zip file which can
> be installed from JSPWiki?) or that the FCK authors can be talked into
> re-releasing it under Apache license...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
