Isn't a lot of the "Others don't do this" addressed by Prosemirror? http://prosemirror.net/
Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
21–30 of 107 posts
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#22The Chrome worker for the demo site accumulated about 600mb of ram. Is the editor really that heavy or is the demo page abnormally heavy?
See this comment: https://news.ycombinator.com/item?id=14417601 - the memory heap should now be around 20 megabytes.
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#23I'm curious, what does this offer over something like https://draftjs.org/, https://github.com/ianstormtaylor/slate, or http://prosemirror.net/ which also use normalized JSON (or ImmutableJS) objects for editor state and are backed by much larger and more established companies/communities.
We just launched https://ridewithgps.com/ride_reports which is built with draft, and I found it to be very flexible. I'd love to see the industry start to focus on using two or three best-in-class editors and contributing bugfixes to those rather than slugging it out with contentEditable again and again in smaller one-off projects.
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#24I'm curious, what does this offer over something like https://draftjs.org/ , https://github.com/ianstormtaylor/slate , or http://prosemirror.net/ which also use normalized JSON (or ImmutableJS) objects for editor state and are backed by much larger and more established companies/communities. We just launched https://ridewithgps.com/ride_reports which is built with draft, and I found it to be very flexible. I'd love t…
Hey, the ORY Editor is actually built on top of slate - it simply adds drag and drop layout capabilities and a cool plugin system!
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#25Ory makes some really cool stuff for OAuth / Authorization that we are considering using in our stack.
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#26I'm curious, what does this offer over something like https://draftjs.org/ , https://github.com/ianstormtaylor/slate , or http://prosemirror.net/ which also use normalized JSON (or ImmutableJS) objects for editor state and are backed by much larger and more established companies/communities. We just launched https://ridewithgps.com/ride_reports which is built with draft, and I found it to be very flexible. I'd love t…
Hey, the ORY Editor is actually built on top of slate - it simply adds drag and drop layout capabilities and a cool plugin system!
You might want to make that more clear in your documentation. Your current README doesn't mention Slate at all, I'd be much more inclined to go 'oh, this makes a lot of sense' if you were pitching 'Slate.js with the batteries included' instead of 'we built another WYSIWYG editor!'
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#27Earlier quoted context omitted.
Hey, the ORY Editor is actually built on top of slate - it simply adds drag and drop layout capabilities and a cool plugin system!
You might want to make that more clear in your documentation. Your current README doesn't mention Slate at all, I'd be much more inclined to go 'oh, this makes a lot of sense' if you were pitching 'Slate.js with the batteries included' instead of 'we built another WYSIWYG editor!'
That's a good point!
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#28I think this looks great for CMS websites: where a user wishes to build an entire page in a web GUI.
For composing text in blocks on existing pages, like comments or posts, you would need a lighter-weight solution.
SlateJS (https://github.com/ianstormtaylor/slate) fits that purpose for me exceedingly well, more than DraftJS, Quill and others, since it doesn't treat XML/HTML as a second-class citizen.
The levels of complexity with text representation are:
Document -> Post -> Text
which corresponds roughly to the data sources:
JSON/Data Structure -> XML/HTML -> Plaintext / Markdown
Markdown can "upscale" to documents, but JSON data structures, by virtue of their complexity, do not "downscale" well at all to Markdown.
HTML is the simple middle for me: it shouldn't be used for documents, but it is totally intuitive for posts where a users simply wants to adjust the color of one's text. The blocks wrapping this text should own the data structure, e.g. a flag for "NSFW Content" shouldn't be in the text editor but an option on the post itself.
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#29I think this looks great for CMS websites: where a user wishes to build an entire page in a web GUI. For composing text in blocks on existing pages, like comments or posts, you would need a lighter-weight solution. SlateJS ( https://github.com/ianstormtaylor/slate ) fits that purpose for me exceedingly well, more than DraftJS, Quill and others, since it doesn't treat XML/HTML as a second-class citizen. The levels of…
This is actually using slate js! We've been contributing to slate too :)
Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux
#30I think this looks great for CMS websites: where a user wishes to build an entire page in a web GUI. For composing text in blocks on existing pages, like comments or posts, you would need a lighter-weight solution. SlateJS ( https://github.com/ianstormtaylor/slate ) fits that purpose for me exceedingly well, more than DraftJS, Quill and others, since it doesn't treat XML/HTML as a second-class citizen. The levels of…
This is actually using slate js! We've been contributing to slate too :)
Ha, then I should read more carefully before I comment :-)
Excellent work! Do you think it may make more sense to market Ory as a Page Editor or Page Maker? Content in my mind can mean anything from a block to an entire page, though I recognize that CMS's have popularized the idea of content being equivalent to a page.
Right now, I see "Layout Editor" and "Content Editor" being used to describe it, so maybe it would make sense to standardize that.
Just a thought!