2 ms·
ImGUI is terrible at text rendering. As soon as you need to support multi-line text or Unicode text, you will run into a hard wall fast. Oh and accessibility.
by andsoitis 3y ago
ImGUI is terrible at text rendering.
As soon as you need to support multi-line text or Unicode text, you will run into a hard wall fast.
Oh and accessibility. No accessibility.
There are other issues too, but these two are typically deal breakers for any serious (or even hobby) application with a non-trivial UI.
Some prior discussion: https://news.ycombinator.com/item?id=24987964 https://news.ycombinator.com/item?id=24987964
- johnnyanmac 3y agoIMGUI is great but I always saw it as a more dev-backend debugging tool than a serious production UI framework. Hooks in easily and draws some very convenient visuals. That's great for bootstrapping, not great for scalability.
- shortrounddev2 3y agoYeah I just wish there was a native UI library that was as easy as ImGui. Everything else is overly complicated. The only other UI framework I know of that is comparably simple is html and css
- andsoitis 3y ago> Everything else is overly complicated. > The only other UI framework I know of that is comparably simple is html and css I'm curious to hear more. What's an example where the HTML/CSS is simpler than putting together something similar in another UI architecture?
- shortrounddev2 3y agoHTML and CSS are very forgiving for non-compliant code. I can morph the webpage at will by using <div>s everywhere and then manipulating the appearance in CSS. If I want to add data to the dom later on, I have a billion different ways to do so using javascript. Compared to, say, XAML, where some elements can only have certain types of children, auto-populating data has to go in specific containers, and all the XAML tags map to actual C# classes, It's a much more strict, far less forgiving, and far less flexible syntax