Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: digitalraptor on September 23, 2010, 07:11:21 pm
-
Hello,
I'm very happy using C::B, it's save me a lot of time to manage C code easily, track every little project I done to recover functions put some ideas into C code.
I added a support to Microchip C Compiler in the Compiler list,or in the Ext.Tools, I added a call of an external C program that save me every modification(in C::B is not possible to use CVS or SVN embedded on it, ...only a dream) in the project and zipping it in a nameprj_date_time.zip format at every successfully compilation.
I'm very happy.
I would suggest to the developers to include a new feature in C::B exactly in the Workspace area.
My idea is to add a custom categorized view list of every project I include into a workspace instead in a flat list now.
Original:
[MyWORKSPACE]
project1
project2
project3
project4
the suggestion is:
[MyWORKSPACE]
[networking_apps]
project1
[gui_apps]
project2
project3
[custom_apps]
project4
...
I have lot of code that I want to access in a easy way(like the idea I want to propose) when I want to write code. Calling the Name of a every project as consolle_app1 consolle_app2, or calculator(GUI or consolle????), menu(wx? QT? consolle??), and other cases.
it's not very good(for me) I think.
Inside C::B I see this list rappresentation exactly in the virtual folders of the internal Project list to show a beauty list of the headers and the source files.
Does it is easy to add this new feature?
thanks a lot.
Callisto.
(sorry, I checked now the C::B forum probably this Topic is posted in the bad area (probably Help/Wanted) according the description of the subforums... If the admin or moderators thinks to move it, could you move it in the right area, please. sorry again.)
-
[MyWORKSPACE]
[networking_apps]
project1
[gui_apps]
project2
project3
[custom_apps]
project4
This is possible. Just not oinly consider workspace/project but also targets and virtual targets. So your layout should be:
[MyWORKSPACE]
[networking_apps_project]
target1
[gui_apps_project]
target1
target2
[custom_apps_project]
target1
Using virtual targets you can still group e.g. debug/release targets together.
The second part I didn't understand. :roll:
-
[MyWORKSPACE]
[networking_apps]
project1
[gui_apps]
project2
project3
[custom_apps]
project4
This is possible. Just not oinly consider workspace/project but also targets and virtual targets. So your layout should be:
[MyWORKSPACE]
[networking_apps_project]
target1
[gui_apps_project]
target1
target2
[custom_apps_project]
target1
Using virtual targets you can still group e.g. debug/release targets together.
The second part I didn't understand. :roll:
sorry MortenMacFly, I'm replying only now(preparing exams...) .
The focus I'm trying to show you is only the tree list of the opened projects.
I know that on C::B it is possible to manage into an easy way different compilation targets and conditional compilation(one project for a lib development and the projects that use it, it's just an example).
The division "for targets" is not exactly the feature I want but I agree that it's very important.
In the workspace panel every project opened appears on a FLAT list.
On your previous message:
[MyWORKSPACE]
[networking_apps_project]
target1
[gui_apps_project]
target1
target2
[custom_apps_project]
target1
I would only propose an extension to add a good division of many projects opened ...
If I understand your table, the solution is only to simply rename the project adding in append to the name of the project after creation, the "category" you want assign,
Renaming the projects after their creation is a good idea.
thanks MortenMacFly
Saluti,
Callisto.