Okay, I can see where their in trouble with that.:> I hope RMS has the ability to speak for the FSF as a whole. (Yes, I know his position, but above he indicated that only the copyright holders could grant that permission. Does the FSF retain copyright?)
KDE doesn't contain any GPL code copyrighted to the FSF, so this doesn't matter anyway.
>Why Qt doesn't use the standard C++ std::string >class? STANDARD GOOD, HOMEBREW BAD. Even a >caveman knows it. Because the C++ string class handles plain old C-style Strings, while Qt's QString supports Unicode. Second, the implicit sharing used by Qt's QString makes string handling quite fast without doing manual optimization.
Slashdot Mirror
Okay, I can see where their in trouble with that. :> I hope RMS has the ability to speak for the FSF as a whole. (Yes, I know his position, but above he indicated that only the copyright holders could grant that permission. Does the FSF retain copyright?)
KDE doesn't contain any GPL code copyrighted to the FSF, so this doesn't matter anyway.
I know that Trolltech hired a
developer for a Mac port recently,
so it seems that there will be Mac
support in the future.
just switch to motif style (or any of the
advanced KDE 2.0 styles) and they will
behave like Motif or GTK.
windows style sucks.
>Why Qt doesn't use the standard C++ std::string >class? STANDARD GOOD, HOMEBREW BAD. Even a >caveman knows it.
Because the C++ string class handles plain
old C-style Strings, while Qt's QString supports
Unicode.
Second, the implicit sharing used by Qt's QString makes string handling quite fast without doing manual optimization.
Yes, you can (in the kicker configuration) ;-)