Despite of what many of you may think this is not a bad thing(TM). Really, on Windows, QT is layered on top of the Win32 API. Heck, for all platforms (UNIX excluded) QT is layered on top of the native widget API, so why not do the same for Unix!
Just wondering, is the file system case-sensitive?
I've always wondered about case-sensitivity versus user-friendliness. I think it is difficult to explain to the 'common (wo)man' that "Readme.txt" is a different file than "readme.txt".
Slashdot Mirror
Why not layer the QT API on top of GTK? (QTK)
Despite of what many of you may think this is not a bad thing(TM). Really, on Windows, QT is layered on top of the Win32 API. Heck, for all platforms (UNIX excluded) QT is layered on top of the native widget API, so why not do the same for Unix!
See also: initial QTK ponderings
Still, it is very feasible to implement C++ iostreams based on fopen() and friends provided by C. So, why not base QT on GTK/GDK?
Just wondering, is the file system case-sensitive? I've always wondered about case-sensitivity versus user-friendliness. I think it is difficult to explain to the 'common (wo)man' that "Readme.txt" is a different file than "readme.txt".