Re: [Swig-devel] Fw: Special Qt mode for SWIG

[Dimitar D. <dpl...@ya...>]

From: Peter McKinna <pet...@gm...>

To: Dimitar Dobrev <dpl...@ya...> 
Cc: "swi...@li..." <swi...@li...> 
Sent: Friday, May 17, 2013 3:18 AM
Subject: Re: [Swig-devel] Fw: Special Qt mode for SWIG
 

Hi,

 Yes certainly feasible. In fact I have already swigged a fair few of the 
qcore h files, and enough of the qgui  ones to build a few working test 
programs. Not sure if you need a qt mode, although there might be a case for it. 
  I have only done this for modula3 so a lot of your qt 
specific typemaps would have to be redone for python, java et al. Also 
you need some glue code for the signals and slots. The stuff I have at 
the moment it built on subclassing a dynamic qobject and is pretty 
clunky, no compile time support like pyeside. 
  When I began I had to null out a lot of the qt macros. 
Caused a lot of grief to swig. Once you have a decent set of typemaps, 
judicious use of apply works wonders and the average .i file for a qgui 
.h file is only a few lines long. Your mileage may vary in other 
languages of course. I confess I am not an expert swigger and hardly 
ever use c++ so I'm sure there are better ways of building a qt 
interface.

Regards Peter

________________________________
 
    Hi, Peter,
    
    Thank you for your reply. If your code is not closed source, may I ask you to share it? I do understand your approach is a little different but I'd love to have your work as reference. Thanks.

    Regards,
    Dimitar