Replies: 2 comments
-
|
It's a mess, but I'm using it successfully for 100kloc+ projects. I'll clean it up significantly, basically release a new version written from scratch with pure Cocoa/Win32 widgets. I'll use everything I learned about UI dev over the last 6 years :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In this new version I'll probably have something like QML for declarative UI. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It appears development on VUI has completely stalled, from an already too slow of a progression pace. Since V has GUI (here) and Raygui (from V's Raylib binding), which both are working and are well done, they arguably should be highlighted or emphasized instead.
Don't get me wrong, as think VUI was/is good (especially the boxlayout feature), but it has fallen behind other UI toolkits and its usability beyond a demo is very questionable and various examples don't work. Lots of features are not implemented (TODO) and it can't be counted on for any serious projects. Sadly, VUI is not something to give a good impression or inspire confidence in newbies, as an introduction to V, in the way that V's GUI or V's Raylib/Raygui bindings can.
Lastly, maybe VUI can return using something other than Sokol or as something completely implemented in V code.
Beta Was this translation helpful? Give feedback.
All reactions