visual-editor VS foundation

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.

GraphQL is a query language and runtime for APIs. It provides a flexible and efficient way for clients to request and retrieve specific data from a server using a single API endpoint.

When you use technologies like GraphQL, it is trivial to derive TypeScript types. A GraphQL API is created by implementing a schema. Generating the TypeScript type definitions from this schema is simple, and you do not have to do any more work than just making the GraphQL API. This is one reason why I like GraphQL so much.

REST and GraphQL have advantages, drawbacks, and use cases for different environments. REST is for simple logic and a more structured architecture, while GraphQL is for a more tailored response and flexible request.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

At Woovi we are GraphQL lovers, hence we develop many helpers around this tool to bring a good developer experience.

A query language for APIs that allows clients to request only the data they need. It provides a more flexible and efficient alternative to RESTful APIs. GraphQL provides a single endpoint for multiple data sources, making it efficient for clients to retrieve only the necessary information forexample if a Node.js microservice uses GraphQL, a client can send a query to request specific data, and the GraphQL service will fetch the required information from the underlying data sources and respond accordingly.

This approach is particularly beneficial for teams looking to enhance their digital presence without the need for extensive coding or software development. By leveraging the GraphQL API endpoint, developers can prepare and execute queries to retrieve the desired content. This makes the Headless Channel a valuable tool 🔨 for content managers and developers, offering ease of use and practicality.

To know about Graphql and why it's being used head over to for more details, Now let's cut to the chase.

GraphQL is an excellent choice for real-time data synchronization in React Native apps. By using GraphQL, you can retrieve precisely the data you need and receive updates in real-time, reducing network usage and providing a seamless user experience.