Author Topic: workspace on steroids  (Read 7031 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5529
workspace on steroids
« on: April 24, 2013, 10:57:24 pm »
Hi,

It has been already proposed to give the workspaces more power, what do you think of the following :
- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
- grouping of projects (aka like virtual folders), so project A, D, H go together in some group, and project B, O,P in some other group. Where the grouping makes some sense to the user, this grouping should then also be visible in the project tree



Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: workspace on steroids
« Reply #1 on: April 24, 2013, 11:02:38 pm »
I had plans on working on this, bug got sidetracked by the ui stuff. :(
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6077
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: workspace on steroids
« Reply #2 on: April 25, 2013, 03:59:38 am »
http://idioms.thefreedictionary.com/on+steroids
"on steroids" means:  in a much more powerful or extreme form :)

- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
I love this feature. Is it related to some discussion of using some global variables (GCV, like -O2, -g...)?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: workspace on steroids
« Reply #3 on: April 25, 2013, 07:48:16 am »
- compiler options/defines on the workspace ==> applies to every project in the workspace (has already been mentioned)
- grouping of projects (aka like virtual folders), so project A, D, H go together in some group, and project B, O,P in some other group. Where the grouping makes some sense to the user, this grouping should then also be visible in the project tree
For the first: Yes.
For the second: What would be a use-case?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: workspace on steroids
« Reply #4 on: April 25, 2013, 07:56:12 am »
For the second: What would be a use-case?
To group related projects, like one group for libraries, one group for plugins, etc.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]