3 ms·
This is something I may switch to, if it proves to have any significant advantages over Quill (https://quilljs.com/ https://quilljs.com/) which we currently use
by arsalanb 8y ago
This is something I may switch to, if it proves to have any significant advantages over Quill (https://quilljs.com/ https://quilljs.com/) which we currently use.
Currently it seems to not support customising and/or creating your own blots (like here — http://quilljs.com/guides/how-to-customize-quill/#customizing-blots http://quilljs.com/guides/how-to-customize-quill/#customizin...)
Also, while we're at it, syncing operations (and example of which is shown here — https://www.slatejs.org/#/syncing-operations https://www.slatejs.org/#/syncing-operations) was a hard concept to wrap my head around until I found this — https://operational-transformation.github.io/visualization.html https://operational-transformation.github.io/visualization.h...
- slow_donkey 8y agoWe're on quill as well - any reason you'd want to switch? We haven't encountered any issues aside from having to write our own parsers (Delta to react native components)
- arsalanb 8y agoAbsolutely no reason to switch, from reading up on Slate in the past few hours.
- ergo14 8y agoI will be probably switching from quill to prosemirror because quill ignores numerous requests for shadow dom compat. It also annoyed me that its hard to get rendered delta results from it - we had some workarounds for it, maybe they provide an API for that nowdays.
- amelius 8y agoI found that last link very nice!