Hm… I stand (mostly) corrected. Anyways, my point was I don’t like the signals and slots concept because it (esentially) extends C++. I’ve never done extremely in depth Qt programming so all I know/knew is that you have to run qmake before make.

Just defending my, and a lot of other people’s, view about the stuff which comes with KDE: (sorry, don’t want to start a flame war here, but I am quoted in the post. Right of reply and all that. ;>)

Yes, you can customize what exactly you get with it, but say you install KDE* from the Ubuntu repos (starting from an ubuntu, not kubuntu, base, obviously). It depends on a bazillion things, most of which I’ll never use. I could go through and individually select each package, but how do I know what’s important (such as the control panel) and what’s not (such as that silly “kwin” game**)?

Ryan Morehart, AKA traherom
(spell my last name backwards… there ya go)

* Let’s assume I don’t want to go the “apt-get install kubuntu” route because I don’t want to bork my entire install with a weird hybrid of the two.

** Yes, I am aware that’s the window manager. But is the fact that it is important blazingly obvious?

qmake is not a preprocessor, it is a makefile generator, like cmake or autoconf/automake. A developer can always use a different buildsystem or write Makefiles manually, just like with any other library.

What the person probably meant is MOC, which isn’t a preprocessor either, but a code generator. It generates C++ code based on markup in the code. Obviously a developer can write this code manually as well, but it is usually more convenient to concentrate on the domain specific problems and let tools handle the boring parts.