I'm using the Twitter Bootstrap styled version of this in a current project. It looks stunning: http://jhollingworth.github.com/bootstrap-wysihtml5/
WYSIHTML5: A better approach to rich text editing
21–30 of 82 posts
Re: WYSIHTML5: A better approach to rich text editing
#22Earlier quoted context omitted.
Aloha handles Tables perfectly (including merge/split of rows & columns, plus pasting from Microsoft Word). Check the demo - http://aloha-editor.org/builds/development/latest/src/demo/b...
Looks nice, but the Aloha licensing basically requires you to buy a license if you're going to use it commercially, whereas this one uses the very simple and open MIT license.
It's licensed under AGPLv3. I prefer MIT as well, but surely you don't need to buy a licence to use this?
https://github.com/alohaeditor/Aloha-Editor/blob/dev/LICENSE...
Re: WYSIHTML5: A better approach to rich text editing
#23Earlier quoted context omitted.
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.
Are you aware of any such editor that does store the data in Markdown or something similar?
Not really what you're after, I guess, but a link anyway: 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."
Re: WYSIHTML5: A better approach to rich text editing
#24Whenever I see "new rich HTML editor", I notice that there is no table editing. What's the point of editor that is missing the most needed function? You could argue that it is not needed, however lack of this function leads to cases of copy-paste from word/excel with bad markup.
I have never seen a rich editor that handles tables well. In fact I've never seen a rich editor that does much of anything well. I almost always have switch to HTML view to get anything done.
Re: WYSIHTML5: A better approach to rich text editing
#25This is a fantastic rich text editor, easily one of the best I've seen. If I remember correctly, 37signals uses it in the note writing feature of the new Basecamp.
Re: WYSIHTML5: A better approach to rich text editing
#26Feature request - ability to add 'notes' to a document. I'd imagine these as toggleable divs that would be able to be inserted anywhere in the doc, then made visible or not by toggling a class. When 'on' the visible portion would just be a small box/space/marker that, when clicked, opened up a larger div with the full note.
I'd tried to do this with the YUI and Dojo editors a couple years ago, but my JS-fu wasn't good enough. I'm possibly better now, and maybe wil try my hand at adding that to this editor (which looks nice for a lot of applications) but someone else with better skills could probably lay the foundation for a 'notes' system much better than me :)
Re: WYSIHTML5: A better approach to rich text editing
#27Earlier quoted context omitted.
Aloha handles Tables perfectly (including merge/split of rows & columns, plus pasting from Microsoft Word). Check the demo - http://aloha-editor.org/builds/development/latest/src/demo/b...
Aloha is more than a meg of JS as it stands and the documentation is pitiful.
I'm a contributor to Aloha and recently project underwent a huge re-write to cut down the cruft. Next release, will use a light weight UI based on jQuery and also switching to a newer command API based on W3C's editing API will also make things more faster (and easier).
Main issue with the documentation was the rapid changes to the API in the past. Since the API is getting stable there will be more concern on improving the documentation.
Re: WYSIHTML5: A better approach to rich text editing
#28Earlier quoted context omitted.
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.
Are you aware of any such editor that does store the data in Markdown or something similar?
Take a look at bergie's Hallo editor:
http://bergie.github.com/hallo/markdown.html
He also has an interesting project called Create:
Re: WYSIHTML5: A better approach to rich text editing
#29Feature request - ability to add 'notes' to a document. I'd imagine these as toggleable divs that would be able to be inserted anywhere in the doc, then made visible or not by toggling a class. When 'on' the visible portion would just be a small box/space/marker that, when clicked, opened up a larger div with the full note. I'd tried to do this with the YUI and Dojo editors a couple years ago, but my JS-fu wasn't goo…
> Feature request - ability to add 'notes' to a document. I'd imagine these as toggleable divs that would be able to be inserted anywhere in the doc, then made visible or not by toggling a class. When 'on' the visible portion would just be a small box/space/marker that, when clicked, opened up a larger div with the full note.
I think this suggestion fully qualifies as something they don't want to do, "[to create] unmaintainable tag soups and inline styles".
Re: WYSIHTML5: A better approach to rich text editing
#30Creating a simple editor which works, seems to be quiet hard, judging based on all the horrible examples we have of existing ones. Hopefully, they'll keep it clean and don't add many new features.