Something no one seems to have mentioned yet is that lying might sometimes be necessary for effective leadership.
Since this is Slashdot, think of Theoden at the battle at Helm's Deep. Putting on a brace face, sometimes straight out lying about things. I can imagine e.g. tribal leaders doing the same thing. So there might be a mechanism whereby people either develop these skills when in a leadership position, or the people who tend towards lying more easily attain these positions.
Of course, this can only ever be a positive thing if the leader in question actually cares about his underlings.
In Finland you get a pre-filled tax sheet in the mail, you only have to return it if there are any changes you need to make. I'm currently living in the US, I find the amount of crap you need to go through to get your affairs in order absolutely stunning.
QString has function to convert to/from std::string, and the Qt containers can all give you STL compatible iterators. I've found working with Qt and the STL in general to be quite easy - in fact I prefer to use the Qt classes whenever I can, as I much prefer their API.
No. Qt has several event loops - it will default to the glib-based one if glib is available at compile time. It will fall back to the generic Unix event loop if glib is not found. You can also disable the glib event loop by setting the environment variable QT_NO_GLIB if you need to - for example debugging is simpler with the generic Unix main loop.
This was developed by Trolltech back in 2006, see here. Interesting quote: the ideal would be for all applications on the X11 desktop to use the same event dispatching mechanism. Here are Trolltech, we think the Glib main loop should be that mechanism...
This has the nice side-effect of being able to use gtk and Qt in the same process. This can be convenient at times, for example I have been developing a Qt-based user interface for the mupen64plus emulator. The glib event loop makes it possible to use plugins with gtk interfaces where no Qt interface exists yet. It also makes integrating glib-based things in general pretty much completely painless.
A common expression amongst Finns is "Vaikka läpi harmaan kiven", "Even through gray rock". More elaborately put, if you are determined enough, you'll get there eventually, no matter the obstacles. There are other similar expressions, and even a word that sums it all up, sisu.
So no, this is not Apple's fault. It's Adobe's and I look forward to seeing any counter-arguments!
TFA said that Apple promised Carbon would get 64 bit support in 2006, then changed their minds and cancelled it in 2007.
If Adobe expects Carbon to get 64 bit support (because Apple said so) and then it suddenly doesn't, its pretty easy to see how that is going to screw things up. That part is Apple's fault.
This also happened to Trolltech. Qt on the mac is written on top of carbon.
Something no one seems to have mentioned yet is that lying might sometimes be necessary for effective leadership.
Since this is Slashdot, think of Theoden at the battle at Helm's Deep. Putting on a brace face, sometimes straight out lying about things. I can imagine e.g. tribal leaders doing the same thing. So there might be a mechanism whereby people either develop these skills when in a leadership position, or the people who tend towards lying more easily attain these positions.
Of course, this can only ever be a positive thing if the leader in question actually cares about his underlings.
In Finland you get a pre-filled tax sheet in the mail, you only have to return it if there are any changes you need to make. I'm currently living in the US, I find the amount of crap you need to go through to get your affairs in order absolutely stunning.
QString has function to convert to/from std::string, and the Qt containers can all give you STL compatible iterators. I've found working with Qt and the STL in general to be quite easy - in fact I prefer to use the Qt classes whenever I can, as I much prefer their API.
You're wrong.
Whoever wins, we lose!
Sounds like KDE modified Qt.
No. Qt has several event loops - it will default to the glib-based one if glib is available at compile time. It will fall back to the generic Unix event loop if glib is not found. You can also disable the glib event loop by setting the environment variable QT_NO_GLIB if you need to - for example debugging is simpler with the generic Unix main loop.
This was developed by Trolltech back in 2006, see here. Interesting quote: the ideal would be for all applications on the X11 desktop to use the same event dispatching mechanism. Here are Trolltech, we think the Glib main loop should be that mechanism...
This has the nice side-effect of being able to use gtk and Qt in the same process. This can be convenient at times, for example I have been developing a Qt-based user interface for the mupen64plus emulator. The glib event loop makes it possible to use plugins with gtk interfaces where no Qt interface exists yet. It also makes integrating glib-based things in general pretty much completely painless.
A common expression amongst Finns is "Vaikka läpi harmaan kiven", "Even through gray rock". More elaborately put, if you are determined enough, you'll get there eventually, no matter the obstacles. There are other similar expressions, and even a word that sums it all up, sisu.
It's even more interesting considering there is no "e" sound in Arabic. There is a "i" sound though. al-Qaida is the more correct spelling.
This is a really nice first step. Thank you Via!
This also happened to Trolltech. Qt on the mac is written on top of carbon.
How about this?
That's all default KDE4 svn trunk stuff, the wallpaper and color scheme both come with the default install. The only custom thing is the clock font.