Absorbed into Tiki 6.x
This page is redundant now really as all this was merged into trunk and ckeditor replaces fckeditor in 6.0.
Update on 17 Sept
The current aim is to make the new ckeditor version the standard wysiwyg editor for Tiki6 onwards and to eliminate the old fckeditor.
But there are two clear options on how it can be used:
- The "Use Wiki syntax in WYSIWYG" option, which converts the html generated into wiki syntax and stores this 'conversion' in the database, is still Experimental and is not yet recommended for any serious use.
- With "Use Wiki syntax in WYSIWYG" NOT set, the html generated by the editor is stored in the database BUT most plugins (and images which use the IMG plugin) are treated in such a way that whilst the raw plugin is viewable in the Source screen, the result of the plugin is shown in the edit screen in a wysiwyg format. In addition these plugins are then double-clickable in the edit screen which pops-up the standard plugin editor.
This 'stored as html' with wysiwyg plugins then provides a good mix of capabilities which exploits the richness of the plugins and aligns their use with the normal wiki editing methods - including being able to edit each plugin independently when the 'edit icons' feature is 'on'. A great deal of testing is still required however as we move towards the Tiki6 freeze and ultimate release.
A dilemma going forward with the "Use Wiki syntax in WYSIWYG" set 'on' option is that ckeditor now has more and more formatting features for which there is not (as yet?) a wiki editing equivalent so moving this option on from Experimental is not just a matter of cleaning up the conversions - but may need the 'suppression' of certain ckeditor features. This clearly needs some discussion.
Your thoughts?
Progress
I'vejonnyb - 9 aug 2010 set up a test server on the new experimental branch here with a user "tikipassword is wiki" for helpful testing people to share. It is updated from SVN at 42 minutes past every hour at least. Please let me know how you get on (via the devels list, for instance)
Background
The wysiwyg editor currently used by the system is FCKEditor - but this has now been replaced by CKEditor - and from version 5 an experimental facility to use the new CKEditor was made available.
The aim of this project is to complete the integration of the experimental CKEditor and in doing so remedy a number of long standing issues with the wysiwyg capability.
Issues to be addressed
- fix any residual 'line feed' problems so that wysiwyg and wiki edited pages behave consistently
- keep it simple by not stripping out things ie the way FCKeditor strips out {img} parameters is very irritating - instead allow all/any plugins to be used on a wysiwyg page and to ideally use the existing plugin editor screens to update/manage the plugin parameters
- this would allow the new more extensive {IMG} plugin to be used for images - ideally with an insertion icon in the toolbar
- the {FILES} plugin (again with an insertion icon) would also enable a simple/flexible file/download text insertion capability - which is a bit ugly currently with FCKeditor
- conventional wiki and external links should also use the same insertion icon (and method) as the current wiki/standard editor
- Ideally the stored page content should be in wiki format but maybe an option is needed to allow 'pure' html - especially as we'll need to allow for existing site migration.
- Wysiwyg doesn't handle floated elements (try edit HomePage)
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}