Replace QuillJs in the RichTextEdit?

[njannink]

I was doing some investigation and the last release that we use from QuillJs is from sep 2019. Apparantly the maintainer is now focusing on his commercial product see this discussion.

We might consider swapping the editor from something that is more actively maintained eg

• TinyMCE
• ProseMirror
• Trix
• SummerNote
• DevExtreme Quill (fork)

Im thinking about TinyMCE because that one is actively being maintained and used

[njannink]

Maybe a new extension Blazorise.RichTextEdit.TinyMCE needs to be created to not immediately break the old API

[stsrki]

If it's not maintained anymore I don't see a reason to further continue with supporting it. We can leave it as it is for now but in the long run, we can create Blazorise.RichTextEdit base project and then have implementation for each supported provider(TinyMCE, ProseMirror, or even QuillJs). Just like we have for Bootstrap, Bulma, etc.

But it's a breaking change so we will need to plan it well.

[njannink]

Indeed thats why I suggested to make it into a new extension and keep the QuillJS based variant in the current extension and possibly in a release later rename that extension to Blazorise.RichTextEdit.QuillJS

[njannink]

I will work that out. With the dynamic loading concept that I use for QuillJS it should work fine

[Melestrua]

Note that TinyMCE has more restrictive licencing than QuillJS.

I wasn't able to use Tiny because I am creating an editor which should be able to work offline, and with Tiny I only get 30 days development time free before I have to licence in that scenario, whereas Quill doesn't have that restriction.

[stsrki]

It might be a good idea to have a licensing mechanism for libraries that have them.

[njannink]

I don't think we will need it ourselfs. TinyMCE has it's own licensing/deployment mechanism for it's premium features. Only thing is we should not add support for turning off the branding, because in the community edition you are not allowed to turn that off.

[stsrki]

No, I didn't mean to turn off anything. I just want to make licensing easier. For example, instead of adding an API key of any libraries into the index.html file, we could have this:

services.AddRichTextEdit(options=>{
  options.LicenceKey = "abc";
});

and then it would all be done automatically by the Blazorise extension.

[Melestrua]

The community version of TinyMCE seems fine see: https://www.tiny.cloud/pricing/

It requires you to use the cloud version of TinyMCE, which doesn't work for me because I want to be able to run completely offline (I had the discussion with their licencing team). Yes, I've been using QuillJS.

[Melestrua]

TBH my use case is probably a bit out of band. I'm experimenting creating a multi-page cross-platform app with rich text edit including understanding/translating typical markdown commands, adding cross-references inline from a menu and save to/restore from markdown.

With all the additions/plugins, QuillJS seems to offer the features. But I have to confess I'm wondering whether Blazor is the best fit since web isn't my primary target, it's just where the rich text/markdown seems to be best supported.

[swaipa]

You could take a look at Trix by Basecamp (Ruby on Rails creators).

https://trix-editor.org/
https://github.com/basecamp/trix

[stsrki]

Trix editor looks really nice.

[njannink]

I find it a bit limited. No support for emoijs for example