Qt-jambi-interest Archive, January 2008
How to avoid the juic complitation ?
Message 1 in thread
Hello,
I'm slowly discovering jambi ( without any previous QT knwowledge).
Seems very promising and a lot cleaner than swing...
I'm trying to integrate the project in a "real" java development
environment: maven ( see my previous request for a online repository),
hudson build system,...
At the moment, the .jui precompilation is done by using the
exec-maven-plugin. -> I need to install the qt jambi package on every
build machine.
Is there an alternative ?
- pure java version of juic ( ant task or maven plugin) ?
- a way to embed the jui file as classpath resources and load them at
run time ( and avoid the precompilation phase) ???
Kind regards,
Etienne
Message 2 in thread
Charlier, Etienne wrote:
> Hello,
>
> I'm slowly discovering jambi ( without any previous QT knwowledge).
> Seems very promising and a lot cleaner than swing...
>
> I'm trying to integrate the project in a "real" java development
> environment: maven ( see my previous request for a online repository),
> hudson build system,...
>
> At the moment, the .jui precompilation is done by using the
> exec-maven-plugin. -> I need to install the qt jambi package on every
> build machine.
>
> Is there an alternative ?
> - pure java version of juic ( ant task or maven plugin) ?
Hi Etienne,
There is no pure java version of the juic tool.
> - a way to embed the jui file as classpath resources and load them at
> run time ( and avoid the precompilation phase) ???
There is:
http://doc.trolltech.com/qtjambi-4.3.3_01/com/trolltech/qt/designer/QUiLoader.html
I would rather go with putting the generated source code into the
package as this is significantly faster though.
-
There is a third option which is to put the juic executable into the
.jar file with the .dll's and unpack that at runtime into the same
folder as the .dll's and execute it from that location. Requires a bit
of setup, but should easily be done. Then you could run the juic tool on
all the machines witout any prior setup.
best regards,
Gunnar
Message 3 in thread
Hello,
Thanks a lot!
I will have a more deeper look at your options !!
Regards
Etienne
-----Original Message-----
From: Gunnar Sletta [mailto:gunnar@xxxxxxxxxxxxx]
Sent: jeudi 17 janvier 2008 10:40
To: Charlier, Etienne
Cc: qt-jambi-interest@xxxxxxxxxxxxx
Subject: Re: How to avoid the juic complitation ?
Charlier, Etienne wrote:
> Hello,
>
> I'm slowly discovering jambi ( without any previous QT knwowledge).
> Seems very promising and a lot cleaner than swing...
>
> I'm trying to integrate the project in a "real" java development
> environment: maven ( see my previous request for a online repository),
> hudson build system,...
>
> At the moment, the .jui precompilation is done by using the
> exec-maven-plugin. -> I need to install the qt jambi package on every
> build machine.
>
> Is there an alternative ?
> - pure java version of juic ( ant task or maven plugin) ?
Hi Etienne,
There is no pure java version of the juic tool.
> - a way to embed the jui file as classpath resources and load them at
> run time ( and avoid the precompilation phase) ???
There is:
http://doc.trolltech.com/qtjambi-4.3.3_01/com/trolltech/qt/designer/QUiL
oader.html
I would rather go with putting the generated source code into the
package as this is significantly faster though.
-
There is a third option which is to put the juic executable into the
.jar file with the .dll's and unpack that at runtime into the same
folder as the .dll's and execute it from that location. Requires a bit
of setup, but should easily be done. Then you could run the juic tool on
all the machines witout any prior setup.
best regards,
Gunnar
