TinyMCE VS turbo-rails

TinyMCE provided a bit more information about this change in a GitHub discussion thread here: https://github.com/tinymce/tinymce/discussions/9496

As I posted there, this directly affects my open source project which is heavily tied to TinyMCE so I may end up forking, and reducing down to what my project needs to reduce maintenance scope & burden.

TinyMCE have been jumping around with their licensing. They were under LGPL, with some (what I believe were) misleading guidance into meeting the LGPL (they specified rules about keeping specific branding elements). They then jumped to MIT, and since moved some of the open plugins to their commercial offering. Now they're making this change.

TinyMCE 7 includes fixes for 17 bug fixes reported by the community. See the changelog for details.

TinyMCE - rich text editing API. Core features are free for unlimited usage.

Website

Any idea how i could replace the current classic editor with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and is some really old version of tinymce and I'm unsure of how to change it, any plugins or scripts to do this?

Any idea how i could disable the default crappy wordpres ugtenbergs block and instead replace it with the newest tinymce wyswig editor: https://www.tiny.cloud/ it looks so modern and clean and i would love to use it but the default wordpress classic editor is so old and honestly makes me sick, any plugins or scripts to do this?

Luckily, implementing a basic text editor in your React application is a fairly straightforward process. In this article I will show you how to implement a rich text editor using TinyMCE.

Check https://www.tiny.cloud/

I'm using TinyMCE as the rich text editor, you can replace it with something else, or simply use a if you wish.

The install notes here link to an issue specific to webpacker. Try that and see if it works?

True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.

Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb

So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.

Use this too: https://github.com/hotwired/turbo-rails

Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433

Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0

turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.

The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails