Description: A simple PyQT program that permit to write QT applications in XML!
Simple like write an HTML page. See screenshots.
*** THIS IS A DEAD APP. !!! *** Recently I googled and found a nice app: Kommander. This seems like uibuilder, but *MUCH* more rich and kde-supported. So I decided to stop development of UIBuilder.
You need QT/PyQT intalled to run this app. I really appreciate any help on coding it. There are many thins to do, yet. A full PyQT binding is near The Impossible! Also I like to see if somebody can make a C++/QT or Java/Applet AWT porting.
Get me feedback, please!
This is only an initial implementation!!!
NOTE: - due to use of "hidden" properties on some widgets, this version is only QT 3.x compatible.Last changelog:
6 Mar 2005: -- version 0.2.2 -- - added a new script extension. Now You can insert Python scripts inside XML! - edited the XML parser
25 Feb 2005: -- version 0.2.1 -- - added a new FX extension (some nice gui effects) - improved network support - new tutorial files (some only in Italian!) - some fix
23 Feb 2005: -- version 0.2 -- - new package structure (more flexible) - added a simple network support - added support for zipped packages (full application now as a zip file) - changed example5.xml - added attributes "enabled", "hidden" on some widgets - added condition - now arithmetical operation between variables is avaiable
22 Feb 2005: - released as 0.1 - added a FileDialog to open the xml file - added examples file for a quick learn - some minor cleanup
21 Feb 2005: Initial implementation. *Not* a release version (but working)
Thanx for what??! :-P
I'm only writing a stupid app!
Btw, I WANT your support! Inform me for any question or feature request.
And I can go to bed in serenity :-))))
After a quick review of UIBuilder code I noticied a not well-formed parser, so I starting in coding another parser, but implementing the QTDesigner XML format (DOCTYPE version="3.3").
In this way I implemented a full XML/QT binding, but with a huge XML syntax.
Now I ask You:
do you prefear the first XML format (simplest, but far away form full QT binding), or this new format?
Why Qt 2.0?
Well, because as for now I only used QT 2.0 widgets :-) and is still portable to non-commercial QT 2.3 Windows version (and is even QT 3.x compatible).
But as I noticed early, this UIBuilder version is *not* compatible anymore with QT 2.x, because of use of hidden properties on some widgets.
I have fixed this in my develop version, but I think next version will be QT 3.x only.
BTW thanks for your interesting!!! I really need people like you!
Ratings & Comments
5 Comments
great tool, thanx!
Thanx for what??! :-P I'm only writing a stupid app! Btw, I WANT your support! Inform me for any question or feature request. And I can go to bed in serenity :-))))
After a quick review of UIBuilder code I noticied a not well-formed parser, so I starting in coding another parser, but implementing the QTDesigner XML format (DOCTYPE version="3.3"). In this way I implemented a full XML/QT binding, but with a huge XML syntax. Now I ask You: do you prefear the first XML format (simplest, but far away form full QT binding), or this new format?
This looks quiet interesting! But why QT 2.0 only ? I think this is something linux really needs: a scriptable gui ienviroment
Why Qt 2.0? Well, because as for now I only used QT 2.0 widgets :-) and is still portable to non-commercial QT 2.3 Windows version (and is even QT 3.x compatible). But as I noticed early, this UIBuilder version is *not* compatible anymore with QT 2.x, because of use of hidden properties on some widgets. I have fixed this in my develop version, but I think next version will be QT 3.x only. BTW thanks for your interesting!!! I really need people like you!