Trolltech Home | Qt-jambi-interest Home | Recent Threads | All Threads | Author | Date
All threads index page 1

Qt-jambi-interest Archive, December 2006
juic remarks


Message 1 in thread

Hi Everyone!

I have just some remarks on the juic meta-compiler and the Eclipse
integration.

When using juic I had some problems using it without the -d option.
The error message was:

> tbaier@level42:~/[...]/robotgui> juic RobotGuiUi.ui
> QDir::mkpath: Empty or null file name(s)
> Failed to create output directory:

with "juic -d . " everything worked fine.

Another note is about the eclipse integration.
When starting a new form and entering a package name, all subdirs
corresponding to the package name are created. In my opinion the package
name should just be included in .ui file and be integrated into the
.java file generated by juic.
This is also not done (yet), so I had to add the package name to the
.java file by myself.

Best Tim


Message 2 in thread

Tim Baier-Löwenstein wrote:
> Hi Everyone!
> 
> I have just some remarks on the juic meta-compiler and the Eclipse
> integration.
> 
> When using juic I had some problems using it without the -d option.
> The error message was:
> 
> 
>>tbaier@level42:~/[...]/robotgui> juic RobotGuiUi.ui
>>QDir::mkpath: Empty or null file name(s)
>>Failed to create output directory:
> with "juic -d . " everything worked fine.

Thats a bug, we'll fix it ;-)

> Another note is about the eclipse integration.
> When starting a new form and entering a package name, all subdirs
> corresponding to the package name are created. In my opinion the package
> name should just be included in .ui file and be integrated into the
> .java file generated by juic.
> This is also not done (yet), so I had to add the package name to the
> .java file by myself.

The package name is based on the location of the .ui file in the package 
strucutre. We felt that duplicating this in the .ui file too would only 
cause extra confusion and potential for failure.

Juic runs in two different modes, either you do the classpath pass, 
using -cp [paths], in which case the package structure is decifered from 
  the directory structure, hence if you have:

c:\qtjambi\com\trolltech\examples\SimpleDialog.ui

and you run juic like this:

 > juic -cp c:\qtjambi

It will update all .ui files in that subdirectory, and generate the 
proper package name for the file.

The other option is to run juic on a single file and then specifying the 
output directory (-d [dir]) and/or the package (-p [package]) like this:

 > juic -d c:\qtjambi -p com.trolltech.examples $PATH_TO\SimpleDialog.ui

--
 [ signature omitted ] 

Message 3 in thread

Hi, Tim.

Tim Baier-Löwenstein wrote:

>When starting a new form and entering a package name, all subdirs
>corresponding to the package name are created. In my opinion the package
>name should just be included in .ui file and be integrated into the
>.java file generated by juic.
>  
>

This is consistent with how projects are generally structured in Eclipse 
and Java, to my knowledge, but we'll definitely consider your suggestion.


-- Eskil