Does it look as if the c++ side expects an extra field in the beginning of the object?

On Wed, 2013-07-31 at 14:59 +0200, michaelc37 wrote:
> for anyone still interested.

We're here :-)

> after some itch scratching i finally got this to compile with dmd 2.063.2 on ubuntu 64bit - https://bitbucket.org/michaelc37/qtd-experimental
> 
> here is what i did.
> 
> 1) had to create auto_ref template for passing rvalues
>      q: i remember some discussion on this, has a solution been
> finalized?
> 2) modify generator so that it adds the "override" keyword where
> necessary
> 3) modify generator so that structs are passed to cpp exported
> functions as pointers.
>      q: i think that some d structs are objects in cpp (QRect?),
> and when cpp read the data the alignment seem to be off(e.g.
> height variable data, ended up in the x variable). Can somone
> explain this?

Are you compiling against Qt4 or Qt5?

I don't have Ubuntu but do have Debian Unstable and Fedora 18 (will move to 19 when it is released). I'd be happy to be a test builder if that would be helpful.

I have a PySide (Qt4) application that I would like to try reimplementing in a native code language — I have to do some work on this anyway to switch back to PyQt since PyQt5 is about and PySide is stuck on Qt4). Options are C++, Go, D. Or possibly all of them. Now that Qt5 is out and about I am hesitant to do anything with Qt4, particularly now there is a SCons tool for Qt5.

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 Wednesday, 31 July 2013 at 17:55:50 UTC, Kagamin wrote:
> Does it look as if the c++ side expects an extra field in the beginning of the object?

Yes, I think that's what it looked like.
I'll try to re-run post some data results this weekend.

On 31/07/13 16:26, Joseph Rushton Wakeling wrote:
> On 07/31/2013 02:59 PM, michaelc37 wrote:
>> for anyone still interested.
> 
> Very happy to hear that QtD is getting some attention.  GUI programming is quite a long way from what I usually do, but I think having good and up-to-date Qt bindings is likely to be very important for D.
> 

+1

-- 
Jordi Sayol

On Thursday, 1 August 2013 at 07:57:30 UTC, Russel Winder wrote:
> On Wed, 2013-07-31 at 14:59 +0200, michaelc37 wrote:
>> for anyone still interested.
>
> We're here :-)
>
>> after some itch scratching i finally got this to compile with dmd
>> 2.063.2 on ubuntu 64bit -
>> https://bitbucket.org/michaelc37/qtd-experimental
>> 
>> here is what i did.
>> 
>> 1) had to create auto_ref template for passing rvalues
>>      q: i remember some discussion on this, has a solution been
>> finalized?
>> 2) modify generator so that it adds the "override" keyword where
>> necessary
>> 3) modify generator so that structs are passed to cpp exported
>> functions as pointers.
>>      q: i think that some d structs are objects in cpp (QRect?),
>> and when cpp read the data the alignment seem to be off(e.g.
>> height variable data, ended up in the x variable). Can somone
>> explain this?
>
> Are you compiling against Qt4 or Qt5?
>
> I don't have Ubuntu but do have Debian Unstable and Fedora 18 (will move
> to 19 when it is released). I'd be happy to be a test builder if that
> would be helpful.
>
> I have a PySide (Qt4) application that I would like to try
> reimplementing in a native code language — I have to do some work on
> this anyway to switch back to PyQt since PyQt5 is about and PySide is
> stuck on Qt4). Options are C++, Go, D. Or possibly all of them. Now that
> Qt5 is out and about I am hesitant to do anything with Qt4, particularly
> now there is a SCons tool for Qt5.
>
> Thanks.

I compiled against Qt4, I want to try it on Qt5 soon but there is another annoying issue I discovered when trying to update and compile all of the qtd exmples: All slot functions must now be declared public.. I'm guessing something changed in traits recently.

I'll keep trying, but I'm not sure how much further I can go with this, as i don't have a solid c++ or qt background.

On Wed, 2013-07-31 at 14:59 +0200, michaelc37 wrote:
> for anyone still interested.
> 
> after some itch scratching i finally got this to compile with dmd 2.063.2 on ubuntu 64bit - https://bitbucket.org/michaelc37/qtd-experimental

Hummm…

https://code.google.com/p/qtd/ (which has a Subversion repository) clearly points to http://www.dsource.org/projects/qtd – which I guess has a checkoutable (Subversion) repository.  But then there is https://bitbucket.org/qtd/repo and https://github.com/qtd-developers/qtd

Before any activity gets going on QtD might it be an idea to decide with which VCS and support tools?

Given Git is the DMD VCS, it would sort of make sense to work with Git and GitHub, though I am happy to work with Mercurial and BitBucket (or even Git and BitBucket!)

Perhaps more should be done on http://www.dsource.org/projects/qtd to make it clear where action is to happen?

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 Wed, 2013-07-31 at 14:59 +0200, michaelc37 wrote:

I have cloned you qtd-experimental to try a build with ldc2. However it seems cmake/FindD.cmake needs amending to cope with ldc2 in a user defined place :-(

-- 
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 Monday, 12 August 2013 at 15:28:34 UTC, Russel Winder wrote:
> https://code.google.com/p/qtd/ (which has a Subversion repository)
> clearly points to http://www.dsource.org/projects/qtd – which I guess has a checkoutable (Subversion) repository.

It's a Mercurial repository. QtD moved to BitBucket because of DSource stability problems impairing development. I suggested Eldar to nuke the DSource one to avoid confusion – i.e. either disable it, or replace it with a singe "repo has moved" text file in the root directory, or something like that –, but somehow this never happened (I don't recall whether there was actually disagreement about this or if we just never got around to do the change).

>But then there is https://bitbucket.org/qtd/repo

As far as I am aware, this is the "current" repository, i.e. the last that Eldar, Max, Alexey and I actually committed to. However, I don't think any of us are actually working on QtD right now, and even simple patches/pull requests take inexcusably long to merge.

> and https://github.com/qtd-developers/qtd

This seems to be an attempt to revive QtD, possibly by Michael Crompton, who contributed a few patches on BitBucket before. The URL is unnecessarily long, though – I just reserve github.com/qtd, if somebody wants admin rights for the organization, just drop me a line.

> Before any activity gets going on QtD might it be an idea to decide with
> which VCS and support tools?

Yep. I can't speak for Eldar and Max, who are really the ones who "own" QtD (I only contributed a few smaller fixes), but I'd say, if somebody wants to genuinely pick up QtD development, they should go ahead and choose whatever they feel most comfortable with. Git/GitHub certainly would be a good fit for the D ecosystem.

> Perhaps more should be done on http://www.dsource.org/projects/qtd to
> make it clear where action is to happen?

I just tried to; the person behind the GitHub repository (Michael?) is welcome to amend that page. Note that the actual installation guides linked from that page all referred to the proper repository before as well.

David

On Monday, 12 August 2013 at 15:47:02 UTC, Russel Winder wrote:
> On Wed, 2013-07-31 at 14:59 +0200, michaelc37 wrote:
>
> I have cloned you qtd-experimental to try a build with ldc2. However it
> seems cmake/FindD.cmake needs amending to cope with ldc2 in a user
> defined place :-(

I haven't tried ldc2/gdc yet, I'll have a look a bit later.

On Monday, 12 August 2013 at 19:08:14 UTC, David Nadlinger wrote:
> On Monday, 12 August 2013 at 15:28:34 UTC, Russel Winder wrote:
>> https://code.google.com/p/qtd/ (which has a Subversion repository)
>> clearly points to http://www.dsource.org/projects/qtd – which I guess has a checkoutable (Subversion) repository.
>
> It's a Mercurial repository. QtD moved to BitBucket because of DSource stability problems impairing development. I suggested Eldar to nuke the DSource one to avoid confusion – i.e. either disable it, or replace it with a singe "repo has moved" text file in the root directory, or something like that –, but somehow this never happened (I don't recall whether there was actually disagreement about this or if we just never got around to do the change).
>
>>But then there is https://bitbucket.org/qtd/repo
>
> As far as I am aware, this is the "current" repository, i.e. the last that Eldar, Max, Alexey and I actually committed to. However, I don't think any of us are actually working on QtD right now, and even simple patches/pull requests take inexcusably long to merge.
>
>> and https://github.com/qtd-developers/qtd
>
> This seems to be an attempt to revive QtD, possibly by Michael Crompton, who contributed a few patches on BitBucket before. The URL is unnecessarily long, though – I just reserve github.com/qtd, if somebody wants admin rights for the organization, just drop me a line.
>
>> Before any activity gets going on QtD might it be an idea to decide with
>> which VCS and support tools?
>
> Yep. I can't speak for Eldar and Max, who are really the ones who "own" QtD (I only contributed a few smaller fixes), but I'd say, if somebody wants to genuinely pick up QtD development, they should go ahead and choose whatever they feel most comfortable with. Git/GitHub certainly would be a good fit for the D ecosystem.
>
>> Perhaps more should be done on http://www.dsource.org/projects/qtd to
>> make it clear where action is to happen?
>
> I just tried to; the person behind the GitHub repository (Michael?) is welcome to amend that page. Note that the actual installation guides linked from that page all referred to the proper repository before as well.
>
> David

That github repo is not mine, and I assumed the current repo was still on bitbucket. However, I agree moving to github would be ideal.