TinyMCE in Melange is horked as detailed in Issue 306. Let's talk about:
It has been suggested that the most beneficial thing to do would be to make Melange accept wiki markup and dispense with other text editing functionality.
...to be agreed/confirmed
The editor needs:
diffs/versioning - is important for proposal changes, documentation changes
TinyMCE is not so very tiny, and accounts for some of the initial start up time when the first page on melange is opened. Thereafter most browsers re-use the existing cached files, so it is probably not slowing down the app on subsequent pages.
Wiki, i.e. having python creating the html rather than storing the html directly might make it easier to overcome some kinds of scripting ‘attacks’
However it is also possible (though possibly difficult to get 100% right) to strip ‘bad html’ from html. Wiki and TinyMCE (or similar) are not mutually exclusive, and which to use could be a UserPreferences option. Clearly it is easier to support just one.