5 ms·
Good job! But it reminds me of the dreaded VGUI.dll. (0_0) For those who wrote code for the GS engine it's probaby one of the worst experiences.
by IYasha 2y ago
Good job! But it reminds me of the dreaded VGUI.dll. (0_0) For those who wrote code for the GS engine it's probaby one of the worst experiences.
- jamesfinlayson 2y agoAww, I didn't think it was terrible (though I have limited experience with UI libraries). The documentation was almost non-existent though. What mod(s) did you work on?
- GranPC 2y agoIt didn't get much better in Source either, much to my dismay.
- IYasha 2y agoThey also added, like, 80MB DLL (AFAIR, chromium) just to render HTML MOTD at some point. I personally had to rewrite most of mod's VGUI code to make it less leaky and more usable, and not once have I thought of using CSS instead of those INI-style theme configs. But CSS is too complicated to parse (and no one will use that anyway). :(
- GranPC 2y agoOriginally it used Windows's built-in embeddable IE thing, which as you can imagine was not stellar for security. IIRC there have been some incidents with bad servers serving up MOTDs that exploited vulnerabilities in Trident to execute arbitrary code. I believe they switched to Chromium while preparing for the OS X port. You'd think this would be good for security, but they then proceeded to update to the latest version approximately once a decade.
- nxobject 2y agoI know a lot of servers exploited that as well to play music in the background... in retrospect, the idea of a web view hanging around while you're in a game is terrifying.
- IYasha 2y agoYes! And all of that just to parse some <font> and <img> tags? :D Also, to be fair: it was VGUI2, which, AFAIK, was introduced with Steam UI and still used in HL2. And was never made available to modders of GS.