|
1) What is QtEZ? 2) What kind of license does it have? 3) What have you used to develop it? 4) What about gtk? 5) What about KDE? 6) Are all Qt widgets available? 7) Can I make my own components? 8) I get XXXXX run time error.. 9) Is there a c++ to .qtz converter? Q: What is QtEZ? A: QtEZ is a wrapper for many features and functions of Qt. It also offers an easy interface to a C++ compiler, with this it allows you to develop a visual interface GUI style, then write the event code, and finally hit run and it'll show you your application as it will appear, it can also be used as a simple dialog editor, so you can create the interface and then dump the source code and work on the events in a different editor. QtEZ is quite flexable though it really isn't a full IDE, as everything isn't as integrated as I'd like but work will continue on it to make it more and more feature-full. Q: What kind of license does it have? A: I guess I would say it's GPL'ish, I freely distribute it and it's source, and you can feel free to change it however you see fit, though I would prefer if changes came back to me so that I could incorporate important additions back into the major distribution. Q: What have you used to develop it? A: Primarily I have used XEmacs on a p133 to develop it, this computer is Linux and I use (to date) egcs. QtEZ has (to a certain extent) written itself as well, most dialogs have been laid out in the environment, and some have been written fully in QtEZ. QtEZ is CVS'd, so if there is a request I can start adding more people with input to the development, and perhaps allow snapshots of features out as they come along. If you are interested in working on QtEZ please mail me. Q: What about gtk? A: I have a certain respect for gtk+, it is definetly interesting. I much prefer to develop a GUI environment with an object oriented language though. Gtk+ is nice and their widgets look good and I wish them luck, but I am very happy with Qt and I think I will stay with it. There are hooks in QtEZ to allow me to have multiple languages and/or libraries, I can put in gtk+ support and have QtEZ dump gtk code, but somehow I suspect the gtk+ team would not be happy to develop a gtk app in an environment using Qt. If there is enough interest though I would do it, or be more than happy to tell another how. Q: What about KDE? A: I like KDE some as well, since KDE is based on Qt I can easily put in KDE support, as I have. What it consists of currently is two features. First QtEZ itself can link to KDE and utilize a few features of KDE including using your configurations as default settings in KDE. Secondly you can 'turn on' KDE in your application, this will have the program use KDE libs, and have a similar effect as the first mentioned method. Q: Are all Qt widgets available? A: Well, no not really. Quite honestly I have spent more time developing the big portions of QtEZ to work on each component. In fact I spend more time developing it then I have using it. However there are a number (to date there are about 10) components available to users, if you would like to see more you can mail in a request to me, or the mailing list and perhaps someone will fulfill your request. Your other alternative is see the next question which will talk about developing a component on your own. Q: Can I make my own components? A: Sure, I would LOVE it if people would start developing some more Qt widgets, and maybe more interstingly some external components of your own, I would like to see a socket and/or a database component, perhaps someday I will create one. However there is a document outlining how to create a component. Q: I get XXXXX run time error.. A: Feel free to mail me the error and I can try to run it out (specifically if it's a compile time error) but honestly I can't figure out every situation, your best bet is to compile your own QtEZ if this happens. The binary distributions you can download have been done with egcs as will your Qt need to be if you want them. Q: Is there a c++ to .qtz converter? A: No, but if you want to make one I'd love it. The qtz format is ok, but I would much prefer to be able to open and import c++ code, but that will probably take more time then I have right now. |