ace VS quill

I used a note system built on top of Fossil as my primary system for quite a while. Here are the details in case anyone is interested.

Fossil allows CGI extensions[1]. There's a database for tickets, but that's just a regular SQLite table that you can use to store anything you want, and it's version controlled and queryable. I stored the notes plus metadata in the tickets database. The CGI returned HTML with the Ace editor for creating/editing notes.[2] Notes were stored using the command line.[3] I needed to add the web server user to the sudoers file to access the Fossil binary.

There were two reasons to use Fossil for this. The biggest was that it handled authentication. The second is that I had a version controlled database to do all the work for me.

I think I eventually moved away from it because I prefer working locally. The "transition" was dumping the data out of the database and into markdown files.

[1] https://fossil-scm.org/home/doc/trunk/www/serverext.wiki

[2] https://ace.c9.io/

[3] https://fossil-scm.org/home/help?cmd=ticket

Ace editor -> https://ace.c9.io/

Hey there! Thanks for reaching out. Writing a code editor with syntax highlighting in a browser can be a little tricky, but it's definitely doable. One resource that might be helpful is the Ace Editor library (https://ace.c9.io/). It's a lightweight but powerful editor that includes syntax highlighting for a huge range of languages. You could also check out CodeMirror (https://codemirror.net/), which is another popular library for building web-based code editors. Good luck, and let us know how it goes!

neocities seems to use the ace editor, and you can view its default keybinds here: https://github.com/ajaxorg/ace/wiki/Default-Keyboard-Shortcuts

The frontend uses the ace editor for syntax highlighting and then sends all the "text" you have typed to a python backend. The backend then writes all the text to a temporary directory and calls the compiler using subprocess (something similar to os.system).

It is built using Reveal.js and Ace, and is a simple markdown presentation tool right in the browser.

https://github.com/ajaxorg/ace

It's a pretty complex JavaScript application but you can development and even run tests locally without ever needing to "build". I'm building a JavaScript-based text editor, too, and it also uses Makefile and you can just run a static file server such as Python SimpleHTTPServer to host all the files in the directory. I still have and componentized HTML/CSS, separated JS files.

Thanks for the suggestion! Although Ace is not the most popular kid in the block, it is still maintained. It does support tmLanguage and could be used for a proof-of-concept editor!

For the code editing you can use Ace.

Ontop of that this [issue](https://github.com/quilljs/quill/issues/3806) exists - which forces us to upgrade once primeNg lets us. Anyone knows a good alternative? I am done with quill and would love to use something more stable.

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?