It is too late to use LibRocket as UI system?

[urho3d]

It is too late to use LibRocket as UI system?

[cadaver]

LibRocket is not actively developed any more, which makes it unappealing to integrate, as any bugfixes would then be ours to do. I also evaluated it one year ago for another project and came to the conclusion that it basically still is a custom HTML dialect, no matter what the documentation says. At the time it also lacked common features such as alpha fading of UI elements. Due to the HTML layouting rules it was somewhat unclear how to query the elements for their exact size & positioning.

I will answer similarly to this as the MyGUI question: if you think you need LibRocket, try integrating it. If your experience on it is extremely good, and you manage to expose the element classes and events to scripting in a clean manner, make a pull request and it will certainly be considerd.

[Canardian]

I think the UI of Urho3D is quite perfect, and doesn't need a replacement.

[shackra]

But, there is people using Librocket for real life games. How it comes that you came to such conclusion? Also the last commit was two months ago, so it is a active project anyway (I'll grant that it isn't active project in development if the last commit where 6 months ago).

The objections seems weird to me. But then I'll master my C++ integrating Librocket to this project. I need a replacement for BGE in the future.

[rasteron]

Hi Jorge,

Fortunately there is already one that has been done in C++ only so you might want to check out Mike Nelson's implementation. It's NOT a full integration with Script API and all but it will definitely get you started.

https://github.com/realrunner/urho3d-librocket

I agree with the guys though, Urho's built-in UI is perfect for the engine, and I'm a web guy used to HTML/CSS stuff like libRocket.

[cadaver]

Ah sorry, I didn't check the git repository, I just looked at the long time from latest release, the forums that were filled with spam messages and some forum messages suggesting it was abandoned.

[cadaver]

I will close this for now, as integration of LibRocket by us is unlikely. Will wait for your work & findings.

Note that it's certainly easier to integrate LibRocket into a stand-alone Urho C++ project, as then you can for example use two event systems (LibRocket's and Urho's own) side by side if it doesn't bother you, and you necessarily don't have to care of the script bindings at all.

For "official" integration it would be quite crucial to be able to use Urho's inbuilt events for the UI elements too, and that's probably easier said than done. One suboptimal solution would be to wrap every UI element class into a corresponding Object subclass.