I was about to write some comments about this when I saw Anatoly's post.
I like the idea of grouping related projects through the workspace
concept. It seems simple, straightforward and quite useful. But I don't
think it has to be forced on the user. If you don't want or can't define
a group of projects, you shouldn't do it just to work on a single one. I
mean, it should be possible to create a project in any directory without
the hassle of defining a workspace first.
It would be really good too if we could add an "Open recent
projects/workspaces" option to the File menu.
What do you think Pierre?
Cheers
Carlos
El 05/09/11 03:42, anatoly techtonik escribió:
It seems to me that workspace explanation is too verbose and complicated.
workspace is nothing but a list of projects whose associated
folder share the same parent directory.
Why not to say that "Workspace is a directory, which contains projects
dirs and configuration file with global settings. Project is a folder
with source code and config file with project settings. Projects
folders live directly inside workspace directory."?
--
You received this message because you are subscribed to the Google
Groups "spyder" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/spyderlib/-/YBnr7apNQg0J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/spyderlib?hl=en.
