Yep, a GUI editor is coming for the forums. We’'ll also be making a number of improvements to the post form. We realize people spend a lot of time on that page so we want it to be as enjoyable as possible.
We’'ll deploy a beta version of it in less than a month – looking forward to your feedback!
most users write some text and this takes long and some of them think even about what they are writing so I think you will not really speed up the time the people spend on the “Post Message” page. If you make it more comfortable they may spend even more time there ;).
I did forget to mention the emotions - I usually use the Spark emotions picker to get the ascii code for
Auto-save? How does this work (not using gmail)? Cause after so many years in forums i got used to press Ctrl-A Ctrl-S before posting This feature will save everything you type in real time? Like my email program does
I prefer a WYSIWIG editor. [ code ] is still not in the Text Markup Help while one must escape [ with a \ to get it displayed, otherwise it will be displayed like as an URL. So one get’'s totally confused about code[/code] while without spaces it looke like as no trailing / C O D E folllows.
A wysiwyg editor is comin very soon - it’‘s actually disabled currently on this site because the conversions between html -> text markup syntax isn’'t quite ready yet. It will be visible on IE 5.5+ and Firefox/Mozilla; other browsers such as Safari and Opera will only have the plain text editor available to them.
I think there may be a few issue with the current code tag, however you could try using the (undocumented currently) code macro which actually supports syntax highlighting other languages. The syntax is:
We’‘ll work on the performance issue and see what we can do to improve it - extending the ttl to a more reasonable value. Once the gui editor is enabled you will indeed have the option to choose which editor to use by default. There is and will not be a built-in option for administrators to use the ‘‘old style’’ post form, though they will have the option to disable features such as the inline spell checker or the wysiwyg gui editor. We are leaving the existing WebWork actions in place so current installations will have the option to replace the ‘‘new’’ post page with the post page from the 5.0.x release, though of course they will no longer have access to all the new features we’'ve added.