New project wizard (Qt)

[sethjackson]

Hello. I have created a Qt project wizard.
You will need to apply the patch file, and then copy the two *.png files to the [C::B src]\plugins\scriptedwizard\resources\qt folder.
Please try it out. I don't have Qt on my system so let me know if it doesn't work.
Other than that the only thing that needs fixed is the wizard.png file. It is the generic console *.png.

EDIT:

Removed files.

[killerbot]

if it works, please let us know, I will commit it then to svn.
You might always ask Morton to have a look at it, he's a project wizard wiz ;-)

[sethjackson]

if it works, please let us know, I will commit it then to svn.
You might always ask Morton to have a look at it, he's a project wizard wiz ;-)

Well the script works. I just wanted a few Qt users to test it to make sure I had everything (project) set up correctly.
Like I said above though the wizard.png isn't right I just copied the generic console one.

[MortenMacFly]

Well the script works. I just wanted a few Qt users to test it to make sure I had everything (project) set up correctly.

The script works, but you cannot create a QT(4) application with it. There is no "QApplication" path below "/include". I'm not sure qhat you want to verify there but this in fact will never allow to create a valid project. Could you try again, please?
As a hint: There is a MinGW installer version of QT which has a nice image in the installer -> this you could nicely use for the wizard, too. Then please adjust the path/verification process to something meaningful and we are one step further...
With regards, Morten.

[sethjackson]

Well the script works. I just wanted a few Qt users to test it to make sure I had everything (project) set up correctly.

The script works, but you cannot create a QT(4) application with it. There is no "QApplication" path below "/include". I'm not sure qhat you want to verify there but this in fact will never allow to create a valid project. Could you try again, please?
As a hint: There is a MinGW installer version of QT which has a nice image in the installer -> this you could nicely use for the wizard, too. Then please adjust the path/verification process to something meaningful and we are one step further...
With regards, Morten.

Sure thing wiz man. I Guess the script doesn't work after all.

EDIT:

Is Qt Windows only for MinGW?

[MortenMacFly]

Is Qt Windows only for MinGW?

The Open Source installer variant seems to be "optimised" (speak: compiled) for/with MinGW which seem to be logic for Open source application development, though. Anyway: The commercial variant supports and integrates into Visual Studio nicely.
Anyway: I'm not a QT developer so all this may be wrong... ;-)

[sethjackson]

Is Qt Windows only for MinGW?

The Open Source installer variant seems to be "optimised" (speak: compiled) for/with MinGW which seem to be logic for Open source application development, though. Anyway: The commercial variant supports and integrates into Visual Studio nicely.
Anyway: I'm not a QT developer so all this may be wrong... ;-)

Ok. Thanks for the info. I'll upload the revised stuff soon. I'm really not sure what to validate the Qt location against though. Hints?

[MortenMacFly]

I'm really not sure what to validate the Qt location against though. Hints?

Hmmm... if I look at you main.cpp I'd say to verify the existence of /include, /include/qt and the main header file "qapplication.h" in that folder. (Which on second thought may be what you had in mind to verify?!).
Nice would be to verify if all thoise libaries the main application will be linked against are really required (I'm thinking of e.g. libQt3Support4 here). This seems to be an aweful lot. Finally you could verify that the main library (libQtCore4 or libqtmain - I really can't tell) is available and issue a descriptive message, if not. Anyway, maybe another (QT experienced) dev could answer this better. Who is the current maintainer of the QTWorkbench plugin? ...a forum search should reveal this... hopefully... ;-)
With regards, Morten.

[sethjackson]

I'm really not sure what to validate the Qt location against though. Hints?

Hmmm... if I look at you main.cpp I'd say to verify the existence of /include, /include/qt and the main header file "qapplication.h" in that folder. (Which on second thought may be what you had in mind to verify?!).
Nice would be to verify if all thoise libaries the main application will be linked against are really required (I'm thinking of e.g. libQt3Support4 here). This seems to be an aweful lot. Finally you could verify that the main library (libQtCore4 or libqtmain - I really can't tell) is available and issue a descriptive message, if not. Anyway, maybe another (QT experienced) dev could answer this better. Who is the current maintainer of the QTWorkbench plugin? ...a forum search should reveal this... hopefully... ;-)
With regards, Morten.

Yop was the maintainer I thought...

Anyways new version. Maybe it will work now.

Forum won't let me upload. The upload folder is full.

Get it here.

EDIT:

Ok I modified the script some more.

The project created by the script pretty much mirrors the file-based one. Could someone that uses Qt try this please?

[lfm]

thank you!
two question :
1.for windows, how to apply the patch file?
2.for QT4, no "/include/Qt/ActiveQt" ..., but have "/include/ActiveQt"
about this, please look here: http://forums.codeblocks.org/index.php?topic=3206.0
additional file is a qt4 project template.

[attachment deleted by admin]

[sethjackson]

thank you!
two question :
1.for windows, how to apply the patch file?
2.for QT4, no "/include/Qt/ActiveQt" ..., but have "/include/ActiveQt"
about this, please look here: http://forums.codeblocks.org/index.php?topic=3206.0
additional file is a qt4 project template.

You are welcome.

1. Well you would need to check out the SVN sources then apply the patch. The easy way is to go to the share\CodeBlocks\templates\wizard\config.script file and add this in the RegisterWizards function:

Code

RegisterWizard(wizProject,     _T("qt"),           _T("Qt project"),            _T("GUI"));

2. Fixed. Thanks for telling me.

Same link as above to download.

For completeness here is the link.

[lfm]

2. Fixed. Thanks for telling me.
Same link as above to download.
For completeness here is the link.

Sorry, I forgot say that  following dir have same problem:
"/include/Qt/Qt3Support", "/include/Qt/QtAssistant", "/include/Qt/QtCore", "/include/Qt/QtDesigner", "/include/Qt/QtGui", "/include/Qt/QtMotif", "/include/Qt/QtNetwork", "/include/Qt/QtNsPlugin", "/include/Qt/QtOpenGL", "/include/Qt/QtSql", "/include/Qt/QtXml"

And ,please add library: libQtSvg4.a, libQtTest4.a, libQtUiTools.a

[lfm]

There is a console window when run Qt GUI project, I find all GUI project created from script wizard also have this  problem.

[MortenMacFly]

There is a console window when run Qt GUI project, I find all GUI project created from script wizard also have this  problem.

This is not a problem but by design. If you run the "Debug" target it will open a console for you. The "Release" target won't. Now why is this? Because for debugging usually a lot debug messages go to the  console. You wouldn't see them if you wouln't run the application from within a consoe. Thus if you don't like the console just run the "Release" target otherwise you'd better stick with the console - it's helpful! ;-)

[sethjackson]

2. Fixed. Thanks for telling me.
Same link as above to download.
For completeness here is the link.

Sorry, I forgot say that  following dir have same problem:
"/include/Qt/Qt3Support", "/include/Qt/QtAssistant", "/include/Qt/QtCore", "/include/Qt/QtDesigner", "/include/Qt/QtGui", "/include/Qt/QtMotif", "/include/Qt/QtNetwork", "/include/Qt/QtNsPlugin", "/include/Qt/QtOpenGL", "/include/Qt/QtSql", "/include/Qt/QtXml"

And ,please add library: libQtSvg4.a, libQtTest4.a, libQtUiTools.a

Done.

Get it at the same place as before.

For completeness here is the link.

EDIT:

Morton why does the wizard keep adding Makefile.am to the project (I think it just copies everything from the /files folder no)? How do I fix that?

[MortenMacFly]

Morton why does the wizard keep adding Makefile.am to the project (I think it just copies everything from the /files folder no)? How do I fix that?

I guess you are operating on the development version of C::B (inside the "devel" directory). If you run update.bat after the compilation within the "output" directory you'll get a version that has all those Makefile.am removed. This is in fact the "release" version which will then work as expected: It doesn't copy Makefile.am.

With regards, Morten.

[sethjackson]

Morton why does the wizard keep adding Makefile.am to the project (I think it just copies everything from the /files folder no)? How do I fix that?

I guess you are operating on the development version of C::B (inside the "devel" directory). If you run update.bat after the compilation within the "output" directory you'll get a version that has all those Makefile.am removed. This is in fact the "release" version which will then work as expected: It doesn't copy Makefile.am.

With regards, Morten.

Oh ok cool. Thanks for the answer.

[yop]

I don't see any problems (it's much better that the last template used). The problem with Qt's meta compiler automagic still remains. With the QtWorkbench it won't work (not the wizard's problem but the plugin's since it was written before the wizard) but I have no time to make it work for now (on my vacations that start this week after a few really stressing months at work, I 'll prefer visiting some islands ).

[sethjackson]

I don't see any problems (it's much better that the last template used). The problem with Qt's meta compiler automagic still remains. With the QtWorkbench it won't work (not the wizard's problem but the plugin's since it was written before the wizard) but I have no time to make it work for now (on my vacations that start this week after a few really stressing months at work, I 'll prefer visiting some islands ).

Ok cool. lfm does it work for you now?

[lfm]

Ok cool. lfm does it work for you now?

Now not found any problem!   

[sethjackson]

Ok cool. lfm does it work for you now?

Now not found any problem!   

Great.

[MortenMacFly]

Ok cool. lfm does it work for you now?

It worked for me, too. I also like the new wizard's image!!!
Thus I've committed this to SVN after the following modifications:
- renamed to qt4 (because it isn't compatible with qt3 and in fact uses qt4 libs)
- using new verification scheme (using new global functions)
- removed unneccesary inlcude directories and libraries that were linked against to keep the project minimalistic

Thanks for help! Could you try to update from SVN and run it - if it works in this version too?

With regards, Morten.

[lfm]

- removed unneccesary inlcude directories and libraries that were linked against to keep the project minimalistic
Thanks for help! Could you try to update from SVN and run it - if it works in this version too?

works fine.
But I think that ought to add all inlcude directories and libraries, because add them manual is really troublesome, and this isn't increase the outfile's size.

[MortenMacFly]

But I think that ought to add all inlcude directories and libraries, because add them manual is really troublesome, and this isn't increase the outfile's size.

Yes, but it also gives a false impression to users that all this is required and the dependencies are not getting clear. I think we can assume that if a user adds another functionality and receives a "Whatever.h include file not found" error he'll know what to do. In addition I searched through the Qt examples and they also not always include all directories and libs but only the required ones... so I thought it's better this way...?!
Are there other Qt devs arguing against this? All of them? ;-)

[sethjackson]

Ok cool. lfm does it work for you now?

It worked for me, too. I also like the new wizard's image!!!
Thus I've committed this to SVN after the following modifications:
- renamed to qt4 (because it isn't compatible with qt3 and in fact uses qt4 libs)
- using new verification scheme (using new global functions)
- removed unneccesary inlcude directories and libraries that were linked against to keep the project minimalistic

Thanks for help! Could you try to update from SVN and run it - if it works in this version too?

With regards, Morten.

I will try it out soon. Thanks for comitting.

[yop]

Are there other Qt devs arguing against this? All of them? ;-)

The main "problem" with Qt is that the Trolltech guys provide the qmake tool that handles all these include directories and stuff so they think that noone is going to add the dirs manually. Setting up a Qt project manually is a punishement... Bottom line adding all the possible dirs would be of great help to anyone who tries to set up a Qt project manually. The main problem is that with every new version they 'll add new ones.

[iw2nhl]

Hi,
there is a similar project: VisualStudio plug-in for Qt4 (the commercial closed-source version has it included, while it is not available in the GPL version).
This project tries to make a GPL plugin like the one (non GPL) bundled with the commercial version.
You could take some ideas from it or, even more, work together with that developers!

Download:
https://sourceforge.net/project/showfiles.php?group_id=49109&package_id=165202
SourceForge project (Q../Free):
https://sourceforge.net/projects/qtwin/
Home Page of Q../Free:
http://qtwin.sourceforge.net/