adrianheine

3 ms·

1.
by adrianheine 8y ago
That's great to hear! CodeMirror 5 has complex code for supporting bidirectional documents, but it's not perfect and lot of work. We hope to let the browser do most of this work for us in the new architecture.
2.
by adrianheine 8y ago
Have a look at https://prosemirror.net/examples/codemirror/ :)
3.
by adrianheine 8y ago
Except for small drive-by contributions (see GitHub repo) the project is not in a state were we can really integrate other people in our process, and there will be pretty substantial changes to interfaces. Looking at ProseMirror, contributi
4.
by adrianheine 8y ago
Improving mobile, touch and screen-reader support are from a user perspective the main reasons we are doing this in the first place. We are expecting to support most of the input behavior such platforms provide.
5.
by adrianheine 8y ago
Yes, ProseMirror is quite stable and it is well-used. Marijn released version 1.0 nearly a year ago and since then we made some improvements, but the interface seems good enough that we didn't even discuss making a breaking change in a
6.
by adrianheine 8y ago
Modes implemented against the current interface will be supported by a plugin. We are definitely planning on providing a better interface for highlighting eventually, but that will take some time.
7.
by adrianheine 8y ago
It's roughly what the two of us need (in addition to regular donations and support contracts) to be able to work on this for one year. We expect a year to be enough time for stabilizing the core and porting some essential plugins.
8.
by adrianheine 8y ago
For one thing, monaco doesn't even try to work on mobile browsers.