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
Thread beginning with comment 442555
To view parent comment, click here.
To read all comments associated with this story, please click here.
Richard Dale
Member since:

"It is quite straightforward to create everything the moc creates at runtime.

For instance, the qml environment creates QMetaObjects at runtime, as do most of the Qt language bindings. All the moc mostly does is generate code for QMetaObjects, and so you can do everything the moc does at runtime pretty much.

Oh yeah? please show me the relevant Qt documentation that allows one to do the same job himself.

(psst...don't bother, there is no documentation. Qt does not encourage that, and I don't want to have to support many versions of the Qt internals that might change from version to version).

I didn't me 'easy' in the sense that it is something a normal applications programmer would want to do. I meant 'easy' in the sense of it allowing systems programmers to make use of the dynamic runtime. I agree there is no documentation and you do need to read and understand the code that the moc generates and how QMetaObjects work at runtime.

Of course that is something that an applications programmer would not want to, and nor would they want to keep track of internal apis. But the fact is using statically typed Boost signals is much, much harder for language bindings and other dynamic language features like properties in Qt Designer.

"If qt was basic on statically typed signals and slots like Boost signals, then you wouldn't be able to do that sort of thing. Which would be a big loss. Nor would KDE KParts work and a lot of other features which depend on the *dynamic* runtime that the moc based features of Qt provide.

There is nothing that stops a statically typed signals and slots system to be connected at runtime via text files. All that is required is the appropriate interfaces in the code.

What is the 'text files' technique that you are talking about? It is a new one on me. What do these 'text files' look like? How would Boost signals work with 'text files'? Is there a tool to autogenerate them?

Reply Parent Score: 2