We have taken a look at it, we went with TinyMCE for a variety of reasons and we''re committed to it for the foreseeable future.
What do you like about FCKeditor that you don''t see in the one we''re using?
Thanks AJ, we looking for more "advanced" rich editor functionality over any particular editor. Features such as:
Rich text shortcomings:
- unable to embed a table within a table.
- unable to modify the following table properties:
- width in pixels/percent
- height in pixels/percent
- border size
- cell spacing
- cell padding
- cell alignment (vertical/horizontal)
- unable to justify text (left, right, center, block)
- unable to modify text properties (I still can''t figure this out)
- The cut and paste functionality required additional steps, an additional CTRL-V and button click. This is a bit annoying because all other editors only require a CTRL-V to paste
- the hyperlinks cannot be renamed
- difficult to embed a image within the document. Also the following image properties cannot be modified:
Thank you for being so supportive,
Most if not all of the shortcomings you outline are not actually shortcomings in the gui editor but rather shortcomings in the wiki syntax that clearspace uses to save all content in. Once the wiki syntax supports a given piece of functionality (say table widths) I''ll update the RTE to enable/support that feature.
The ctrl-v issue is a known issue which we''re planning on correcting when time allows. Much better image support is slated to be added for the 1.2 release, though setting properties on images may not make it in for that release.
Bruce, thank you for your reply.
How can we accelerate the extension of wiki syntax support to enable the capabilities listed above?
We have no issue per se with the graphical interface.
The filter and macro code is pluggable (http://www.jivesoftware.com/builds/docs/clearspace/latest/MacroFilterDevelopmentGuide.html) so it''s possible to include modified versions of the wiki filter and other filters. It''s obvously a lot of work and not something that I''d recommend to anyone but a seriously dedicated user (or as a professional services engagement).
In general though I would suggest putting in feature requests for each feature to support @ jivesoftware.com (linking this thread). Support will create issues in our issue tracker for each request and it can then be voted on by the community which we do use to help determine what features go into each release). We do try our best to improve the wiki syntax a bit for each release as we understand that the functionality it provides impacts in a direct manner what you can do with the product.
Is there a current roadmap for wiki syntax enhancements?
Right now there is no explicit roadmap beyond bug fixes and general improvements. It''s likely that at some point we''ll allocate a developer for a development cycle to go through and add improvements and make changes that have accumulated up (such as the
vs The specified item was not found. syntax conversion that can be quite confusing to people) however that has yet to be scheduled.
Would you like me to create an issue in the issue tracker for general wiki syntax improvements (with your examples as starting points) for the community to add improvement requests to and to vote upon?