4 ms·
How does it compare to https://github.com/remirror/remirror https://github.com/remirror/remirror?
by ampdepolymerase 6y ago
How does it compare to https://github.com/remirror/remirror https://github.com/remirror/remirror?
- strogonoff 6y agoOurs looks fairly similar in the core concept. Less polished. A bit older. Will have to take a detailed look at remirror later! Update: I created an abstraction called “feature” that seems to be similar to the extension concept, but different. Through features, editor creator can contribute related schema aspects and plugin views. Schema is always there and is not handled by a separate feature, however.
- kushan2020 6y agoI have been following remirror since the start and also started working on bangle.dev at the same time. bangle.dev aims to add little API overhead on top of Prosemirror (PM) whereas Remirror tries really hard to hide the PM API and attempts to provide its own React-ish abstraction. This might be a totally fine choice, but I went with the route of building reusable components instead of abstractions.
- scottmessinger 6y agoI'm glad to hear this! Using Remirror worries me because it injects an abstraction between our code and PM. However, when I look at your docs, it's not clear it's a different in approach from Remirror. The imports are all from bangle.dev which makes it seem like the same approach. I would love to see a doc explaining the "API overhead" and how to use PM directly. I want to feel confident I can easily drop back down to PM if Bangle doesn't have a feature I need or implements it in a way that won't work for our use case. Really excited to see this approach! Shared PM plugins are a great idea!
- ampdepolymerase 6y agoHow easy is integration between the two frameworks?