Upgrade CodeMirror to 3.0
|Priority:||Should have||Due date:|
|Category:||Backend User Interface|
- version 2.0 was released as stable meanwhile: http://codemirror.net/oldrelease.html
- said to be smaller and faster
- got rid of frame-workarounds to display and the like
details con CM1 vs. CM2 (or how to migrate):
In that thread it is mentioned the API should (hopefully) be mostly the same.
Updated by Susanne Moog almost 2 years ago
- Status changed from New to Accepted
- Complexity set to medium
We need to check for compatibility and adjust what's not compatible, but that should be pretty easy.
Updated by Tobias Liebig over 1 year ago
AFAIK within the core, only the t3editor and the extension manager (edit files) uses the codemirror library ATM. There might be some Extensions, which might use the library too.
Updated by Stefan Neufeind about 1 year ago
I had a closer look at it. Yes, t3editor and editing files should be the parts that need to be migrated.
Since the architecture of codemirror changed it's not that simply changing the codemirror-sources used. But the new architecture looks a lot simpler and more powerful to me, so I also see some value for cleaning up parts of the code during this migration.Parts that need to be taken care of:
- code-completion: Haven't tried how much of our current approach can be left as-is as a first step. The functions triggering the completion need to be changed a bit, but fetching the completion etc. should be possible to leave unchanged for now.
After that change is done we could, as a separate task, take a look whether the several divs, iframe etc. for the editor are still needed and how we could maybe reduce that overhead. There is also quite a bit of prototype-code involved.
Updated by Stefan Neufeind 5 months ago
3.0 released. We might want to consider going directly to the 3.0-tree.
If so, somebody please update the issue-title.