ProseMirror 1.0
21–30 of 69 posts
Re: ProseMirror 1.0
#22Cool to see persistent data structures under the covers here. I tried to make a contentEditable editor some time ago and gave up when I realized how many edge cases there would be, but from what I learned when working on that, this general sort of approach seems like the right way. What do you feel like you learned when working on this project? Will any of it make it back to Codemirror?
Re: ProseMirror 1.0
#23The color of the links on that blog is not very colorblind friendly. I couldn't tell what was a link and what wasn't without zooming in to make the text larger.
Re: ProseMirror 1.0
#24Earlier quoted context omitted.
Yes, I have a small patreon at https://www.patreon.com/marijn . Right now I'm also running a crowd-funding for the new edition of my book at https://eloquentjavascript.net/3rd_edition/
Don't forget to download a bitcoin wallet and add a bitcoin address for donations to the page.
Re: ProseMirror 1.0
#25I've tried a lot to get it working for https://github.com/fiatjaf/coisas and only managed to make it work by copying running code from one of the demos, ignoring all customization and working myself around the editor to provide the custom functions I needed.
I may be totally wrong here, but I'm trying to be sincere about my experience.
Re: ProseMirror 1.0
#26I love CodeMirror and like very much the content of the Marijn's blog posts I've read, but I must say ProseMirror is a nightmare to work with. I guess the problem is that there is too much customization options, no sane defaults, no understandable tutorials, many different overlapping API and documentation versions. I've tried a lot to get it working for https://github.com/fiatjaf/coisas and only managed to make it w…
> If you're looking for a simple drop-in rich text editor component, ProseMirror is probably not what you need. (We do hope that such components will be built on top of it.) The library is optimized for demanding, highly-integrated use cases, at the cost of simplicity.