I’ve released a new version of RichText that supports clickable text via the a anchor tag. It’s now very easy to detect clicks on words with an a tag and generate a message that can open for instance a context menu.
The extension is used to create rich text, nothing else. In my mind the scrollsbars is something that has nothing to do with displaying rich text, while you on the other hand expect it. A great example of the problem with expectation management when it comes to more complex features.
What other UI interactivity do you need from rich text beside detecting clicks on certain words?
Godot has made huge step forwards in usability on both the engine and the editor. GUI system is nice, although yes, pretty locked. A lot of the rough edges have been polished, GUI themes included.
Exporting is still not so smooth. HTML5 has a lot of issues.
I would say is a totally different paradigm than Defold. For me it’s missing that minimalism in the engine and the hassle free workflow, especially when having to deal with the native side of things.
What is a huge source of inspiration is the way you can script the editor to your needs, from creating panels and custom inspectors, down to the interaction in the viewport with custom manipulators and interactions.
There has been quite a few mentions about editor extensions, but I’m not sure Defold editor is headed in this direction though, at least from what was stated so far (I know it’s a big task).
This is being worked on right now. @vlaaad is doing good progress on the first iteration. This will allow you to hook in your own scripts to perform tasks based on stuff happening in the editor. You will be able to run scripts pre and post build and bundle. Run scripts when files are added. When things are selected. Add and react to menu options etc. This will allow you to do a lot of interesting things.
But the first iteration will not cover creation of viewport customizations though. That will come later.