Linked by Thom Holwerda on Tue 21st Sep 2010 21:32 UTC, submitted by diegocg
Qt After many months of designing, coding, reviewing, testing and documenting, Qt 4.7.0 is finally ready for the big time. Although it's a little more than nine months since Qt's last feature release (4.6.0 on December 1, 2009), the seeds of some of the new stuff in 4.7 were sown much earlier. Indeed, many of the ideas behind the biggest new feature in Qt 4.7.0, Qt Quick, were born more than two years ago, not long after Qt 4.4 was released
Permalink for comment 442543
To read all comments associated with this story, please click here.
siride
Member since:
2006-01-02

"If you're so dead set against using tools why don't you program in assembler?


I use tools, but I don't want to use more tools than what is actually required. The MOC is not really necessary in order to have signals and slots: any other signals and slots system does not use an external tool.
"
MOC really is required for Qt, so you have to use it. End of story. Just deal with it. I mean, what are you gaining by taking this ridiculous stance about MOC? It's not that hard. It costs pretty much nothing. It's fairly automatic if you use any type of build system at all. Stop bitching about something that almost nobody else cares about and just get your job done. Really isn't that hard. People like you make me weep for the programming community.

"Is there any Decent and modern gui toolkit that does not use external tools to create boilerplate code?


Nope. That's what I said.
"
A lot of other toolkits actually do use autogenerated code. Some Java frameworks do it. .NET does it. It makes things easier because you can avoid the tedium of building your GUI in pure code.

As I said in another comment, if C++ had proper reflection, MOC wouldn't be needed. Yet another reason why C++ is actually a poor language for building GUIs (among other things).

Reply Parent Score: 3