Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
QtWorkbench plugin
yop:
--- Quote from: ldindon on April 21, 2006, 10:36:29 am ---A better integration could be that it could be possible to open .pro file directly with C::B (I guess I dream to much...)
--- End quote ---
File->Open->your.pro for now. It is possible and easy to have an option to edit the .pro file in the plugin and I will provide it. Just write your custom things outside the identifiers.
--- Quote from: ldindon on April 21, 2006, 10:36:29 am ---Another solution, could be (like decpp plugin) to have "import from .pro / export to .pro" options.
--- End quote ---
"Export" is possible (just needs another menu entry). Import is not at the moment (it would need a better parser than the one I already have).
--- Quote from: ldindon on April 21, 2006, 10:36:29 am ---Another quick alternative could be that we will be able to specify a .pro to the plugin and that he only manages SOURCES and HEADERS .pro entries according to file add/remove in C::B project. Other qmake options could be managed by hand (allow to use whole power of qmake). The plugin could be in charge to setup C::B (ie: add the pre-build command "qmake <custom.pro>" to generate the Makefile and check "use a existing makefile"). Thus we will be able to use C::B original "Build", "Clean" commands.
--- End quote ---
This option as said above is only one menu entry away. You just have to decide what to provide to the plugin from the C::B envinroment and the rest of the stuff is up to you ;)
--- Quote from: ldindon on April 21, 2006, 10:36:29 am ---Working on a cross-platform IDE with Qt is crutial for me, so maybe (If you and my boss agree) I may contribute to this Qt integration.
--- End quote ---
Gladly :) I 'm in the same place as you are (a cross-platform IDE with Qt is crutial for me). Believe it or not the requests have just started coming in, so stick around I 'll sure need your help (even using the plugin and posting what you think would be enough, if you are willing to get your hands dirty that's even better). Thanks for the sugestions.
yop:
There is a new release available (I had some Easter holidays here in Greece and this also was a long weekend so I finally had some free time). All the issues mentioned up to now have been dealt with (more details in the first post). A big thanks to all for the valuable feedback.
The new sources should go in the contrib plugins folder of the CodeBlocks sources.
As you 'll see I've added workspace support and due to this bug it won't work. I decided to add it to make testing and confirming it easier and also see if anyone else has any idea about it (with Yiannis we already spoted a false behaviour of the compiler plugin here).
That's all, hope it got better :)
Yorgos
MortenMacFly:
...I wonder if there is a new version available? Because I receive a strange error that wxMenu could not be found when I try to integrate the latest version into the current SVN head.
yop:
Could you try again? New file (qtworkbench-0.4.1.alpha.zip) uploaded.
MortenMacFly:
--- Quote from: yop on July 18, 2006, 07:50:39 pm ---Could you try again? New file (qtworkbench-0.4.1.alpha.zip) uploaded.
--- End quote ---
Done that and it works again - thanks a lot!
If you now change the output DLL name (for Windows) from "qtworkbech" to "qtworkbench" it's perfect... ;-)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version