I've wanted to see a good, production-quality open source take on this editing paradigm for a long time and your implementation appears to get a lot of things right. I took a crack at this myself a few years ago but never got around to really getting it over the line: https://github.com/segphault/codemirror-rich-markdoc
Your wysiwyg support for tables is very nice, but I couldn't quite figure out how to delete a row. The checkboxes are also a little fiddly, it would be nice if the checkbox turned into editable text when the cursor moves next to it. Does Atomic Editor work with vim bindings via replit's CM6 vim plugin?
Props for building this and sharing it, I hope you stick with it.
I'm testing it and seems to be very broken, typing things around and things jumps everywhere.
I was trying to create something like this too, because I need something that also work for mathematical writing. Let me push a version on github and update, it fixes a lot of issues.
Unfortunately it works on my own version of markdown, which is a subset of pandoc markdown, but I think one can get claude to update the parser to work for other things.
I was able to repro one issue that could have been contributing to your broken experience - there's a slight delay between, for example, clicking text in a heading and having the "#" markdown decoration appear. This is to prevent the mouse location from shifting mid-click and causing text to be selected unintentionally (obsidian does this too). But there was a bug that was causing a cascading set of failures if edits happened during that delay window, which is likely what folks who are clicking around at random points in the editor and adding text are doing. I fixed it in 0.4.2, which should be live now.
Thanks for trying it out! would you mind giving some steps that allow me to repro the issue? It's early days so i'm sure there are some rough edges, hopefully I can fix them quickly.
I just clicked around a bit and randomly typed, suddenly no matter where I typed, my text was ending up at the end of the document. Found it to be pretty broken as well.
Thanks for the heads up - I pushed up a fix to the hightlighting issue.
I originally went with Milkdown (Prosemirror-based) for Atomic, the knowledge base project that I built Atomic Editor for. ProseMirror doesn't provide virtualization out of the box. For shorter notes and even moderately long content it's fine - but atomic supports syncing content from a diverse set of sources and I noticed that long documents were causing delays on initial page load and some lag during edits. I didn't find anything like it with native virtualization that felt right to me so I built Atomic Editor.
No problem, I actually went through a similar path of trying milkdown/tiptap/a few others as the core for my own editor needs but kept running into into issues where the abstractions got in the way eventually. I was thinking about using ProseMirror for a custom 'one big text file' concept so I guess Ill close the door on that idea and give this a try.
That looks pretty good, but it isn't quite there yet, for me. If you try to delete the opening fence, the closing fence turns into a closing fence, and the abstraction leaks in tables.
Your wysiwyg support for tables is very nice, but I couldn't quite figure out how to delete a row. The checkboxes are also a little fiddly, it would be nice if the checkbox turned into editable text when the cursor moves next to it. Does Atomic Editor work with vim bindings via replit's CM6 vim plugin?
Props for building this and sharing it, I hope you stick with it.
I was trying to create something like this too, because I need something that also work for mathematical writing. Let me push a version on github and update, it fixes a lot of issues.
Unfortunately it works on my own version of markdown, which is a subset of pandoc markdown, but I think one can get claude to update the parser to work for other things.
https://github.com/chaoxu/coflat
Mine also have lot of bugs (especially reader and editor doesn't completely match yet).
repro the issue: click random places and add random texts, scroll around, and issues come up sooner or later.
I'm curious when I see things more geared toward prose using CodeMirror instead of ProseMirror. Any comment on that decision?
I originally went with Milkdown (Prosemirror-based) for Atomic, the knowledge base project that I built Atomic Editor for. ProseMirror doesn't provide virtualization out of the box. For shorter notes and even moderately long content it's fine - but atomic supports syncing content from a diverse set of sources and I noticed that long documents were causing delays on initial page load and some lag during edits. I didn't find anything like it with native virtualization that felt right to me so I built Atomic Editor.