5 ms·
Ended up having too many customization problems with Summernote and Angular on our current project and switched to Quill (http://quilljs.com/ http://quilljs.com
by jzig 11y ago
Ended up having too many customization problems with Summernote and Angular on our current project and switched to Quill (http://quilljs.com/ http://quilljs.com/) instead. Both are pretty good projects though, and each have room to grow into something bigger.
- cgijoe 11y agoThere's a good list of them here: https://github.com/cheeaun/mooeditable/wiki/Javascript-WYSIWYG-editors https://github.com/cheeaun/mooeditable/wiki/Javascript-WYSIW...
- hatsix 11y agoReally liked the idea of Quill and their usage of rich-text. Didn't use it because of lack of tables and the effort of moving our storage of data to rich-text... But I was very tempted, and still not certain I made the right decision. We went with CKEditor instead, and while it is extensible and the developers are responsive, it is a LOT of work to integrate with JS-heavy front-ends. They use setTimeout() liberally, and don't recover gracefully from ascendant DOM changes. (like being removed from the DOM without being destroyed). That said, it is the most feature-full, open-source editor in active development... The state of web-based editors is... a mess... and there seem to be new ones popping up constantly, while old ones go stale. So, yet another generation of young devs whose time will be wasted solving the basic, known problems of contenteditable, while quill, scribe, wysihtml, goog.wysiwyg, aloha-editor, tinymce, ckeditor, redactor and likely a dozen others need help. (and what I really want is ace or kix... a content-editable-less editor)
- hackerwins 11y agoI'm creator of summernote. Actually I agreed with you comment. So I try to implement non-content-editable editor. https://github.com/summernote/winternote https://github.com/summernote/winternote