CodeMirror VS quill

codemirror - a code editor component for the web

massCode uses Codemirror as the basis for the editor and .tmLanguage as the grammar for syntax highlighting. This tandem opens the door to over 600 existing grammars. The application currently supports more than 160 grammars. In addition to .tmLanguage, the application supports .tmTheme for themes. There is also…

After giving up countless times since I started this project, I finally managed to dig the dark secrets of Pyodide and run pyTermTk on a browser, all of this, of course, thanks to the magic of xterm.js. I know, my friend, I know what you are thinking, I was disgusted at first picturing that hideous javascript defiling the python purity of my code, but, when I saw my red pepper shining on webkit engine, well, I couldn't hold back a tear. And after that, who am I to not include also an editor and my collection of demos and examples? So, here it is, a super minimal buggy and feature incomplete pyTermTk Sandbox

syntax highlighting is simple with https://codemirror.net/

Can CodeMirror 2 be used to highlight code from a DIV or PRE tag (without the editor)?

Official website of Codemirror.

CodeMirror [MIT] https://codemirror.net/

There sure is, take a look at Code Mirror

Codemirror is open source, so you can look at, clone and experiment with its actual code as much as you like to figure out how it works.

Developed using the LAMP stack mainly because I'm more of a back-end (PHP) dev, and for various other reasons, like affordable web servers. The front-end is vanilla JavaScript (AJAX for dynamic stuff). I also use CodeMirror to provide the visual-code editor for programmers.

Ymmv, but I will never use Quill for a production project again.

We started using Quill 1.x around 2016, I initially liked it a lot. Jason proactively reached out to me when I first tweeted about considering Quill, and he was helpful when I had questions about the implementation.

Fast forward to 2019, we were running into some bugs, Quill 1.x was in maintenance mode, and 2.0 was effectively undocumented. I reached out to Jason on Twitter to get a sense for the timeline, and he basically told me to get lost. (Also his company Slab now blocks me on Twitter, though I imagine he just meant to block me from his personal account.)

Everyone has stressful days, especially when building a startup, so maybe that was just a bad time for me to reach out. My best guess is that they were focused on their own company (fair!) and barely had the time to maintain Quill for their own internal usage, let alone release it as open source. If that's the case, I wish they'd been upfront about it.

5 years later, Quill v2 is finally live. I'm glad to see Slab is still around, and I hope they have the bandwidth to publicly maintain Quill going forward. But if you're thinking about using this in production, I would push on what their commitment is to supporting it, and have a plan for if they stop responding.

(Jason, if you're on this thread, no hard feelings, water under the bridge. Feel free to ignore or chime in with your own perspective.)

* https://github.com/quilljs/quill/issues/2435

I started with Quill... wound up hitting lots of challenges. There are bugs/issues like, "don't add extra margin or it will be converted to extra spaces." I also struggled to embed Quill into an HTML form element, which I though would be easy.

Fair enough. Look maybe into more of a utility like Quill? https://quilljs.com/

I agree. Yes, you can. Quill is the example here.

Actually, back in 2015 when we started prototyping CKEditor 5, we started with this approach as well. Our goal from the beginning was to combine real-time editing capabilities with an engine capable of storing and rendering complex rich-text structures (nested tables, complex nested lists, other rich widgets, etc.). We quickly realized that a linear structure is going to be a huge bottleneck. In the end, if you want to represent trees, storing them as a linear structure is counterproductive.

So, we went for a tree model. That got many things in the engine an order of magnitude harder (OT being one). But I choose to encapsulate this complexity in the model rather than make it leak to particular plugins.

In fact, from what I remember, https://github.com/quilljs/quill/issues/117 (e.g. https://github.com/quilljs/quill/issues/117#issuecomment-644...) is a good example of issues that we avoided.

I also talked to companies that built their platforms on top of Quill. One of them ended up gluing together countless Quill instances to power their editor and overcome the limitations of the linear data model but is now looking for a way to rebuild their editor from scratch due to the issues (performance, complexity, stability).

So, yes. You can implement a rich-text editor based on a linear model. But it has its immediate limitations that you need to take into consideration.

I've always used Quill and always satisfied with it. It can be adapted to React Native as well. Despite the most popular RTE is Draft js it has some limitations on mobile.

NgPrime has this editor if you’re using it already for components. Or Quil could work

Quill

The few I have seen out there are flask-blogging, tiny-blog, and maybe quill?

So if one were to use https://quilljs.com/ as /u/ike_the_strangetamer suggested and just include a disclaimer that the site doesn't support pasting in some things, would that work?