QT4 Designer and C::B on Linux

[Larri]

I don't speak english fine, but like know how I can work with a project of QT4 Designer together with C::B or if existing some type plugin to do it

[yop]

Designer is by far the best RAD tool for Qt. Use it as a standalone application and configure C::B to use it for .ui extensions using Settings->Environment->File Extension Handler

A C::B integration is not an easy task since C::B and designer use different GUI toolkits.

[Larri]

but, I work in Linux...... look I'm working with a C::B that it have QT, but I don't know how work it, I need someone  tell me  how work a project of QT4 Designer with C::B or how I can work with C::B that contain QT

[jk1981]

Hello yop: could you write something more about setting codeblocks up for .ui extensions? "Settings->Environment->File Extension Handler" and than what?

And another question is: how do you deal with that qt moc thing(The meta object compiler) so that is handy in codeblocks??
I tried to use qtworkbench plugin(.http://qtworkbench.googlecode.com/files/QtWorkbench-0.5.1_alpha.cbplugin) in Win but it didn't work with CB4545(Oct 19) and open source qt4.

[yop]

Hello yop: could you write something more about setting codeblocks up for .ui extensions? "Settings->Environment->File Extension Handler" and than what?

And another question is: how do you deal with that qt moc thing(The meta object compiler) so that is handy in codeblocks??
I tried to use qtworkbench plugin(.http://qtworkbench.googlecode.com/files/QtWorkbench-0.5.1_alpha.cbplugin) in Win but it didn't work with CB4545(Oct 19) and open source qt4.

Then add *.ui extension and assign as the default program to open them: <your qt path>/bin/designer.exe Unfortunatelly global code::blocks variables are not expanded here so you have to provide the full path.

As for QtWorkbench I know that the binary plugin doesn't work but this is expected when you provide a binary plugin for a product that is still evolving. This was my main argument to explain why I wouldn't provide a binary version of the plugin. Things are much more stable in C::B right now so the plugin was usable for quite a while (and it still works if you build it from sources). Anyway I 'll release a new binary plugin in a short while (hopefully this week) so you will be able to use it again. Untill then you can work using an older C::B nightly build.