Perhaps they should've used the MobileDoc standard instead creating another one.
Editor.js – Block Styled Editor
21–30 of 75 posts
Re: Editor.js – Block Styled Editor
#22Why JSON-that-resembles-HTML rather than whitelisted-subset-of-HTML? Seems to throw away a huge amount of tooling and force an extra step on anything that wants to render the content? Although I guess I could render the JSON to HTML server-side and get the best of both worlds. Everything usually boils down to a question of caching something somewhere.
Re: Editor.js – Block Styled Editor
#23too bad browser selection api will cause LOT of bugs of this kind https://streamable.com/0gc8j
Re: Editor.js – Block Styled Editor
#24Two long established predecessors to this: Sir Trevor JS[0] and Colonel Kurtz [1]. I've used Kurtz extensively and it's been brilliant. The only downside of all these block-based editors is that you can't easily create layouts where images float to the left or right of text. Well, you can create them but you don't get a WYSIWYG idea of what it looks like right in the editor. I can live with that! I've explored all so…
CK is our workhorse for tons of sites, and we've struggled to come up with a good general pattern for editing horizontal layouts. We'd happily take suggestions, however. I'll admit it's one of the more awkward things with the editor.
Re: Editor.js – Block Styled Editor
#25Or better still, just show them on the side maybe. It takes too many clicks to get work done. (IMHO)
Re: Editor.js – Block Styled Editor
#26That pop-up when I click the 3 dots is way too slow, it's really annoying. Those buttons should probably be visible on hover. Or better still, just show them on the side maybe. It takes too many clicks to get work done. (IMHO)
Re: Editor.js – Block Styled Editor
#27[1]: https://docs.wagtail.io/en/v2.4/topics/streamfield.html
Re: Editor.js – Block Styled Editor
#28Why JSON-that-resembles-HTML rather than whitelisted-subset-of-HTML? Seems to throw away a huge amount of tooling and force an extra step on anything that wants to render the content? Although I guess I could render the JSON to HTML server-side and get the best of both worlds. Everything usually boils down to a question of caching something somewhere.
, next one has paragraph, etc. ect.
JSON is not here for resemblance, but for normalization. You force single presentation of things from start, and when user presses enter (or other text composition event happens) you prevent default action, update document model (JSON) and then update the HTML.
This approach is much more sane and predictable than trying to trust browser's HTML.
Re: Editor.js – Block Styled Editor
#29Every time I see a new contenteditable-based editor I'm reminded of this https://medium.com/content-uneditable/contenteditable-the-go...
We are thinking of hiring a manager to license this to everyone using the other editors on their site (sites like BuiltWith can tell you entire lists of these sites) or just negotiate to give an unlimited / open source license to Froala / Imperavi themselves!
See for yourself: https://youtu.be/-DgaTwG1csc
Contact greg at the domain qbix.com if interested. It would be a commission based job, but can involve a lot of fun things like producing videos and websites w our team.
Re: Editor.js – Block Styled Editor
#30Earlier quoted context omitted.
Or slatejs. As I understand both have (or used to have) some serious problems with Android mobile. I don't see an explicit claim of Android/mobile support here either, which to me would be the killer feature.
They're hard at work on Android support on SlateJS. https://github.com/ianstormtaylor/slate/issues/2062