Has anyone done any work with QML and D?

Gustavo Niemeyer is creating a QML package for Go and it is already getting a lot of traction.

I have a little pet project where I am comparing PyQt5 and Go, and I would like to try using D as a third variant, but I don't wan't to have to use Gtk for the D version I want to use the same UI for all variants.

Thanks.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Le 14/11/2013 13:03, Russel Winder a écrit :
> Has anyone done any work with QML and D?
>
> Gustavo Niemeyer is creating a QML package for Go and it is already
> getting a lot of traction.
>
> I have a little pet project where I am comparing PyQt5 and Go, and I
> would like to try using D as a third variant, but I don't wan't to have
> to use Gtk for the D version I want to use the same UI for all variants.
>
> Thanks.
>
What do you mean exactly by same UI? Same QML files directly?

Because it's hard to port/Wrap Qt to D, I am working on a project that is based on QML principles (Property binding, Components,...). It's called DQuick.

It's only a prototype for the moment, and it will certainly never compatible with QML files. But if you are only interested by property binding and the composition system of QML, DQuick will make you happy.

On 15/11/13 00:37, Xavier Bigand wrote:
> It's only a prototype for the moment, and it will certainly never compatible
> with QML files. But if you are only interested by property binding and the
> composition system of QML, DQuick will make you happy.

First of all -- thanks for your work on DQuick :-)

However, I think we have to acknowledge that Qt5 in general is a really important toolkit that needs first-class D support.  This is only going to become more true as more and more development moves onto mobile platforms.

An effective QtD may be a hard problem but it's one that needs a solution.

On Fri, 2013-11-15 at 00:37 +0100, Xavier Bigand wrote: […]
> What do you mean exactly by same UI? Same QML files directly?

Indeed. I have one QML file (well maybe more than one given the way QML works but basically the UI is entirely in QML) and this can be used from PyQt5 or go-qml to provide multiple implementations behind the same UI.

> Because it's hard to port/Wrap Qt to D, I am working on a project that is based on QML principles (Property binding, Components,...). It's called DQuick.

D has always claimed to have excellent "link to C, and hence C++ (sort of)" support, so what is it about the Qt library that causes hassle?

> It's only a prototype for the moment, and it will certainly never compatible with QML files. But if you are only interested by property binding and the composition system of QML, DQuick will make you happy.

Sadly I really do need to work with the same UI file. I'll take a look at DQuick though and see what it's like.

Thanks.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Fri, 2013-11-15 at 11:10 +0100, Joseph Rushton Wakeling wrote: […]
> However, I think we have to acknowledge that Qt5 in general is a really important toolkit that needs first-class D support.  This is only going to become more true as more and more development moves onto mobile platforms.

Agreed. We have GtkD, but Gtk doesn't have the same acceptance as a cross-platform system at Qt and wx.

> An effective QtD may be a hard problem but it's one that needs a solution.

There is the QtD_Experimental Git repository, but it seems there is no consistent resource available to keep the project moving at a good pace. :-(

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Le 15/11/2013 11:10, Joseph Rushton Wakeling a écrit :
> On 15/11/13 00:37, Xavier Bigand wrote:
>> It's only a prototype for the moment, and it will certainly never
>> compatible
>> with QML files. But if you are only interested by property binding and
>> the
>> composition system of QML, DQuick will make you happy.
>
> First of all -- thanks for your work on DQuick :-)
>
> However, I think we have to acknowledge that Qt5 in general is a really
> important toolkit that needs first-class D support.  This is only going
> to become more true as more and more development moves onto mobile
> platforms.
>
> An effective QtD may be a hard problem but it's one that needs a solution.
>
>

My point of view is :
 1) phobos will be same as Qt basic frameworks (utf string, network, io,...)
 2) Moc try to provide some basic features of D that are missing in C++, like traits
 3) Widget model is deprecated
 4) QML isn't perfect, there is a lot of hacks (I use it for a commercial application every days)
 5) A D native GUI system will put D on stage, a such library it can demonstrate benefits of GC, signals, traits, concurrency,... on something that stay light.