ext Dusan Zatkovsky skrev:
> I have still problem to run designer (build in 4.6) as "jambi-designer". It
> still tries to open/save .ui, not .jui files.
>
This means the Qt Jambi Language plugin has not been loaded. This is
called JambiLanguage.dll (on Windows) and is located in
$JAMBIDIR/plugins/designer after a complete build. There is a second
plugin in this directory which needs to be loaded, and which is called
JambiCustomWidget.dll.
You can check if it has failed to load by opening the "Help -> About
plugins" dialog box. A common reason why it would fail is that the Qt
Designer you are running is built against a different configuration of
Qt than the plugin. In that case, it will refuse to load the plugin to
avoid binary compatibility issues. Another reason could be that such a
problem (or something different) has arisen in the past, and that the
plugin is therefore blacklisted. This can be resolved by clearing the
plugin cache.
See more here:
http://doc.trolltech.com/4.5/plugins-howto.html#the-plugin-cache
> But - my question is - what is the main difference between qt designer and
> jambi designer? As I see, xml files are very similar. I think (but can't find
> any documentation about it) that jambi-designer should use custom widgets
> written in java, but I am not 100% sure about this.
>
The difference in the .ui-files is that all language specific parts are
in Java code.
There are several differences in Qt Jambi Designer and Qt Designer. In
general, the tool has been adapted to handle Java programs. This
includes as its main parts:
1. Loading Java classes as custom widgets (JambiCustomWidget plugin)
2. Java syntax in the signals and slots editors (JambiLanguage plugin)
3. Classpath resources used in resource editor. (JambiLanguage plugin)
> So, my second question is - is it necessary to use "hacked" jambi designer?
>
Yes.
-- Eskil
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
