Is it a good idea to use WTL? Let's say in this situation you don't give a shit about Macfags or Freetards and/or don't want to use a shitty ``cross-platform" toolkit like Qt. You just want to develop a frontend for Windows.
Apparently Google Chrome used WTL for Windows. Other options: Microsoft Foundation Classes (MFC), Smartwin++, .NET (obligatory, but I think it's honestly better to use C# for .NET), or raw Windows API (lol nope). WTL is superior to these alternatives, right?
Name:
Anonymous2012-02-22 0:40
WTL is superior to these alternatives, right?
You need a definition for superior otherwise you may as well the alternatives as they have no defining differences.
Name:
Anonymous2012-02-22 2:20
Use Haskell
Name:
Anonymous2012-02-22 2:52
Win32 API or bust, faggot.
Name:
Anonymous2012-02-22 15:31
>>4
it is windows api. it is a cpp wrapper for windows api; it pretty much compiles to the same machine code. it=wtl.
Name:
Anonymous2012-02-22 15:34
WTL is nice because it's lightweight. If you're ultra-focused on program size or speed, I'd use it. Otherwise use Qt, it's more "user-friendly" - better documentation, more powerful from the start.
Name:
Anonymous2012-02-22 15:34
.NET
Shoving fireants inside your urethra with a rusty nail is better than C++/CLI.
Name:
Anonymous2012-02-22 15:44
>>6
qt doesn't use native widgets, it redraws everything like swing. it tries to mimic native widgets, so therefore is only as good as the latest version of qt libs. I would rather rely on os devs than qt devs for longevity purposes.
also fuck moc. qt is useful if you are working on some enterprise quality shit, but not good for high quality programs, where you really should use native toolkits.
Name:
Anonymous2012-02-22 15:48
>>8
High quality programs like Firefox and Chrome both draw their own interface though... Opera uses Qt as far as I know. A lot of software doesn't use native toolkits.
talking about who dropped which shitty library. defending a shitty library because it's base is the obviously API you can't talk about using socially. Picking and choosing libraries like faggots buying new panties.
ITT: Libraryfags show us how far their faggotry extends.
Why would anyone sane enough use ENTERPRISE libraries?
libcaca is sufficient to anyone.
For portability, you should use a completely cross-platform toolchain. One for desktop, other for mobile. Anything else is shit, except maybe LISP
Name:
Anonymous2012-02-23 23:24
>>17
Windows API (and its libre C++ wrapper WTL) is hardly ENTERPRISE.
Libcaca...I hope that's a fucking joke.
Cross-platform APIs never look/feel native on any platform, and more importantly, have a higher overhead than native APIs. You just have to get over the fact that you can't ``write once, run everywhere."