User forums > Using Code::Blocks
Suggestions for next release.
ossLover:
Hello guys,
I haven't worked with C::B a lot, but when trying it out I found one missing feature. I can't configure my own key-bindings. The problem is, at my office I use Visual Studio 6 and 2005, and use for compiling like F7, debugging with F5 etc... But when using C::B I have to do other key combinations. So, it's confusing and frustrating to use other keys. It would be really great if I can modify the key-bindings into my flavor.
Another thing is there should be serious support for BOOST libraries. BOOST is mandatory for now, as they provide powerful and professional libs, which is already being partly a C++ standard. I mean C::B is mainly focused on programming C++, than BOOST must be included in the installation package.
I know I have easy talking, but I swear if I had free time I would put a lot of effort to help improve C::B as I like it very much. Especially because it's written by developers for developers.
Thank you.
MortenMacFly:
--- Quote from: ossLover on August 11, 2009, 11:01:39 am ---It would be really great if I can modify the key-bindings into my flavor.
--- End quote ---
You can do this by using the keybinder plugin.
--- Quote from: ossLover on August 11, 2009, 11:01:39 am ---Another thing is there should be serious support for BOOST libraries. BOOST is mandatory for now, [...]
--- End quote ---
I don't think so. C::B is also widely used for teaching at universities where boost plays no important role.
In the end if we start bundling boost why not wx, and a few other thousand libraries, too? This makes no sense to me. Shipping just C::B or in a bundle with a compiler and debugger makes sense, but not in addition with 1..n libraries because this can be literally unlimited.
Jenna:
--- Quote from: ossLover on August 11, 2009, 11:01:39 am ---Hello guys,
I haven't worked with C::B a lot, but when trying it out I found one missing feature. I can't configure my own key-bindings. The problem is, at my office I use Visual Studio 6 and 2005, and use for compiling like F7, debugging with F5 etc... But when using C::B I have to do other key combinations. So, it's confusing and frustrating to use other keys. It would be really great if I can modify the key-bindings into my flavor.
--- End quote ---
If you have installed the contrib-plugins, you can use the keybinding-plugin: "Settings -> Editor -> Keyboard shortcuts".
--- Quote from: ossLover on August 11, 2009, 11:01:39 am ---Another thing is there should be serious support for BOOST libraries. BOOST is mandatory for now, as they provide powerful and professional libs, which is already being partly a C++ standard. I mean C::B is mainly focused on programming C++, than BOOST must be included in the installation package.
I know I have easy talking, but I swear if I had free time I would put a lot of effort to help improve C::B as I like it very much. Especially because it's written by developers for developers.
Thank you.
--- End quote ---
I don't think boost should be included in the installation-package. Neither should any other lib.
It's enough (maybe too much) that C::B ships with MinGW, because every package we bundle will most likely be outdated soon or has issues like the Vista-problems of the MinGW-version shipped with the 8.02 release.
thomas:
--- Quote from: jens on August 11, 2009, 11:35:30 am ---I don't think boost should be included in the installation-package. Neither should any other lib.
--- End quote ---
Agree.
Seronis:
--- Quote from: thomas on August 11, 2009, 12:01:02 pm ---
--- Quote from: jens on August 11, 2009, 11:35:30 am ---I don't think boost should be included in the installation-package. Neither should any other lib.
--- End quote ---
Agree.
--- End quote ---
Just a hobbyist but I also agree. The wiki articles on getting Boost, WX, SDL and OGL working are great and have worked for me on WinXP (all service paks), Vista (pre and post sp1), and Ubuntu. I've updated the wiki myself when a new version of Boost was released so it would point to the most recent packages. Works great this way. Bundling would just make the packages fall out of date too quickly.
Navigation
[0] Message Index
[#] Next page
Go to full version