4 ms·
Depends on the use case. If you are using it in as a website authoring tool, it makes sense to store the rich-edit user input as HTML itself. However, in a sce
by laktek 14y ago
Depends on the use case. If you are using it in as a website authoring tool, it makes sense to store the rich-edit user input as HTML itself.
However, in a scenario like commenting or composing a message (where only limited editing options are available), storing in a format such as Markdown make sense.
- legutierr 14y agoAre you aware of any such editor that does store the data in Markdown or something similar?
- patrickg 14y agoNot really what you're after, I guess, but a link anyway: http://code.google.com/p/pagedown/wiki/PageDown http://code.google.com/p/pagedown/wiki/PageDown "PageDown is the JavaScript Markdown previewer used on Stack Overflow and the rest of the Stack Exchange network. It includes a Markdown-to-HTML converter and an in-page Markdown editor with live preview."
- yesbabyyes 14y agoTake a look at bergie's Hallo editor: http://bergie.github.com/hallo/markdown.html http://bergie.github.com/hallo/markdown.html He also has an interesting project called Create: http://createjs.org/ http://createjs.org/
- zalew 14y agohttp://markitup.jaysalvat.com/home/ http://markitup.jaysalvat.com/home/
- kodablah 14y agohttps://github.com/OscarGodson/EpicEditor https://github.com/OscarGodson/EpicEditor
- Akram 14y agoeven in comments a whitlist of markup would save a lot of code on both the ends.