User forums > Using Code::Blocks

is there a way of associating a workspace to a given project?

(1/2) > >>

zlieb:

for example, if you open a given project file that it opens the similarly named workspace?  This is (I think) the default behaviour in VS2008 -- when I have a project and a solution in the same directory that references it, and I double click the project, it opens the appopriate solution (VS's version of a workspace).   At the moment, my when I double click the codeblocks project, it doesn't load any workspace (but creates a new, empty workspace).   my main problem is, it's very easy to trip up workspaces, to open multiple projects into a workspace, etc, and it seems a bit problematic for our end users --   if there was a way of somehow automating the relationship of a project to it's workspace, that would be great.

I know projects can belong to multiple workspaces, so this is not a totally cut and dry thing --  but I think the VS solution, which searches the same directory for a solution that references the project, seems pretty reasonable as it leads to alot less confusion.

thanks!
zach

Jenna:
Where is the problem with double-clicking the workspace-file ?

stahta01:

--- Quote from: jens on December 25, 2009, 10:15:37 pm ---Where is the problem with double-clicking the workspace-file ?

--- End quote ---

By default windows does not show the file extension.
I call this the stupid windows give me a virus mode.

Edit: To disable the above

In a Computer window
Tools -> Folder Options
Tab View
Uncheck Option: Hide Extensions for Known File Types.

Tim S.

Jenna:

--- Quote from: stahta01 on December 26, 2009, 01:14:50 am ---
--- Quote from: jens on December 25, 2009, 10:15:37 pm ---Where is the problem with double-clicking the workspace-file ?

--- End quote ---

By default windows does not show the file extension.

--- End quote ---
But the shown icon is (should be) different.


--- Quote from: stahta01 on December 26, 2009, 01:14:50 am ---I call this the stupid windows give me a virus mode.

Edit: To disable the above

In a Computer window
Tools -> Folder Options
Tab View
Uncheck Option: Hide Extensions for Known File Types.

Tim S.

--- End quote ---

That's one of the first things I do on all my new windows installs.

zlieb:


--- Quote from: jens on December 25, 2009, 10:15:37 pm ---Where is the problem with double-clicking the workspace-file ?

--- End quote ---

the problem is not with double clicking the workspace file (which I don't have a problem with), the problem is that there is no association (or implied association) from a project to a given workspace, which can lead to novices  making mistakes with a library of code that I make (openframeworks.cc).   Also, since the "adding a project" to a workspace is as simple as opening the project, it's *very* easy in CB to mistakenly add a project to a workspace it shouldn't be in.   

Having used xcode's project dependencies and VS solutions, I find CB's workspaces to be the most problematic for beginners.

I noticed that VS has a very nice behavior, which is to scan the folder of the given selected project for solutions (ie, workspaces) that reference that project and open them, and I wondered if CB had that behavior, or if it was one you could consider adding.

give it a try -- I think it greatly improves the overall usage of these kinds of files.

thanks
zach

Navigation

[0] Message Index

[#] Next page