Qt and KDELibs for D?

[Craig Black]

We use Qt for a C++ project.  We have developed many wrappers for Qt classes 
for technical reasons.  One reason is that we hate annoying moc files. 
Anyway, we are on our way to having our entire GUI written using wrapper 
classes.  We have a somewhat complex solution to eliminate the need for moc 
files.  Because of this, we only have one moc file for all of our wrapper 
classes.  We retain most of the Qt functionality, including signals/slots, 
and event interception using custom C++ delegate classes.  One drawback is 
that we cannot override virtual methods in Qt classes very easily.  A long 
term goal of mine has always been to port our project to D.  But if we did, 
we would drop Qt and use a GUI native to D.  We would have to rewrite our 
wrapper classes to accommodate this, but its easier than rewriting the 
entire GUI.

-Craig

"just jeff" <jeffrparsons at optusnet.com.au> wrote in message 
news:epkgmb$2b33$1 at digitaldaemon.com...
> Firstly, is anybody working on Qt bindings for D? If so, the rest of this 
> message is probably irrelevant and can safely be ignored. But continuing 
> under the assumption that nobody is... :P
>
> I'm wondering what would be involved in a project like that. Has anybody 
> looked into hooking into C++ libraries enough to know what would be the 
> best plan of attack? (And for Qt in particular, I hear it uses some custom 
> pre-processor magic on top of the standard C++ one; is this right, and is 
> this likely to be a huge problem?)
>
> Qt Jambi 
> (http://doc.trolltech.com/qtjambi-1.0/com/trolltech/qt/qtjambi-index.html) 
> seems to be doing a similar thing for Java, so I presume they got over any 
> problems with multiple inheritance. What other major problems would there 
> be?
>
> Any random thoughts appreciated.