react-quill VS visual-editor

The email template settings page should provide a user interface where users can see and edit the email template. The react-quill (https://github.com/zenoamaro/react-quill) component will be used as the editor for the email template message.

Did you consider react quill instead of tiptap? If so, why did you choose it?

const rt = useRef(); const doAThing = useCallback(()=> { const editor: Quill = rt.getEditor(); // add a button to the toolbar here using // the api: https://github.com/zenoamaro/react-quill/tree/v1.3.5 }, [rt]);

i'm using react-quill.

To demonstrate how Quill works, we are going to use the React-Quill package, which is a React wrapper around the Quill editor. Below we have a component that will render the React Quill editor with a toolbar that offers tools for formatting text.

What I used is this one: https://www.npmjs.com/package/react-quill

I could dig into that and explain but it would probably be easier for you to just look at react-quill since it's already doing what you want.

I'm using this editor in a React application with PostgREST and PostgreSQL. I plan to store the RT in text fields. Looking for advice and cautions on whether this is a good approach.

Quill is also pretty nice.

Quill has good libraries but has completely fallen into disrepair across the board. ReactJS I would argue is in an even worse state.

A few words about Visual Editor. This editor is built around the powerful Quilljs Delta document format originally developed by QuillJs. Delta documents can be easily converted to JSON, the encoding is easy to read and modify and offers many extensibility options.

There's a fork of flutter_quill called visual-editor. It switches to the next widget in the focus sequence, which is one way to properly handle the key.

Flutter also isn't great for text editors, but there are a few implementations like visual-editor for formatted text that's acceptable. Also, the xterm package is pretty amazing from its capabilities (even runs full vim!).

There's visual-editor, but that one has a different focus than a programming editor.

Two months ago I decided to fork the Quill rich text editor because the architecture is extremely difficult to follow. Since I desperately need for my own project, a strong rich text editor that can be easily extended with more features I took the decision to byte the bullet and refactor Quill from the ground up. There are numerous extremely good features in Quill yet the overall architecture was a total train wreck. In this article I'll be explaining in detail what were the issues and how I attempted to improve them. You can find the source code at Visual Editor Github. I've documented the entire process and I'll be releasing deep dive Flutter architecture episodes at Visual Coding YouTube. Enough shameless plugs, let's get going.

You are right, we have programmed the app with Flutter and are very happy with the framework. Two years ago, when we started, many libraries were still missing in the community, especially the text editors were problematic. That's why I contributed a lot to the community to improve the status. At the moment I am very excited about the libraries SuperEditor and VisualEditor. Otherwise, the tooling with Flutter is excellent and it's a lot of fun to program with it. We programmed the server with NestJS, use a PostgreSQL database and GraphQL as the query language.

Visual Editor Gihub Repo - Freshly forked, already many changes, to be published in pub dev.