Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
QtWorkbench plugin
yop:
Have you checked the documentation? (http://code.google.com/p/qtworkbench/wiki/PluginUsage)
I guess the most interesting part for you would be: http://code.google.com/p/qtworkbench/wiki/QtWorkbenchProjects
Hope this helps...
GeeF:
Hidiho,
first of all, I wanna thank you yop for your efforts. The Plugin works quite well for me now, although I had a bit of a hassle.(next time, read wiki first ^^)
Anyway, couldn't we just add a new project template which sets all the configs we need for workbench? Would ease up the process for Qt and c::b beginners. Also, if it's possible, it would be nice if the generated ui_*.h and moc_*.h could be added automatically.
oh, last but not least. I've got a little bug. I'm on a resolution of 1280x1024 and when I try to access the qtworkbench tab in the project properties, it won't fit the standard window size of the dialog, i.e. it doesn't resize that well ^^ So I almost crawled up the wall wondering where to activate the plugin, because the damn checkbox wasn't visible. I'm on c::b release 8.02. Don't know if this is a bug or an easter feature ^^
Apart from that, the Plugin really rocks. Keep up the good work.
schroeder:
Well... I've stumbled upon this while looking for some advice about why the QT4 tutorial's examples compile nicely under C::B until you get to the damn example #7: at which point, apparently because for the first time C::B sees a secondary .cpp module and a header, it starts complaining about an "undefined reference to 'vtable for LCDRange'[/i]" - BTW, as long as I can see from a quick Google search, already a very notorious issue - and the nice fairy tale suddenly ends with the wolf growling ;^)
Anyway, I have a question: under C::B there already seems to be a "File > New > Project > QT4 project" option, which is actually the one I've used. So, why another plugin to obtain what apparently should be the same effect? Or, dually: if the need has been felt of implementing a new QT4 plugin, what does that default functionality, "File > New > Project > QT4 project", serve for?
Second point: is there any possibility of successfully compiling a QT4 application using the default
Codeblock's wizard option?
Thanx :°)
GeeF:
--- Quote --- So, why another plugin to obtain what apparently should be the same effect? Or, dually: if the need has been felt of implementing a new QT4 plugin, what does that default functionality, "File > New > Project > QT4 project", serve for?
Second point: is there any possibility of successfully compiling a QT4 application using the default
Codeblock's wizard option?
--- End quote ---
The default QT4 Project wizard just makes shure you have qt installed and if needed, asks you for its location. Nothing more, except for creating a nice little hello qt app with its main.cpp.
If you wanna use the unique features Qt provides, ie. signals and slots, you have to run the files through the moc and if you're using the designer, you have to uic the .ui files first and import all those, or simply use qmake for the whole build process.
Qtworkbench does all that for you, so you can compile inside of codeblocks without having to hassle with the build tools.
schroeder:
--- Quote ---The default QT4 Project wizard just makes shure you have qt installed and if needed, asks you for its location. Nothing more, except for creating a nice little hello qt app with its main.cpp. If you wanna use the unique features Qt provides, ie. signals and slots, you have to run the files through the moc and if you're using the designer, you have to uic the .ui files first and import all those, or simply use qmake for the whole build process. Qtworkbench does all that for you, so you can compile inside of codeblocks without having to hassle with the build tools.
--- End quote ---
...ah-ha, I get it. I wonder if the last 0.6.0-alpha works also with the 8.02 release ^_^
Anyway: is there any place where this point, about the wizard's default behavior, is made clear? I can't see any. So, I'd suggest that some more information, maybe even just a simple brief note, will be added in future releases. Something like "please: don't expect this wizard to help you create a true QT4 project. It's simply intended to help you make the fine tuning of your C::B in function of your QT installation, provided you have one". Actually, I think that from a wizard one tends to expect (maybe erroneously, yes... but, that's it) sort of a "plug and play" behavior...
As an alternative, I'd suggest that, should the plugin show to work reliably and to be without major bugs, its functionalities be included in the next release of C::B by default...
Am I wrong? ;^)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version