Workspaces

support saving workspaces

Could you clarify, please what do you mean? Thanks.

It would be great also to have settings be configurable for whole workspacce, not only for whole application or per directory in workspace.

In fact it works exactly like this: Fleet can apply settings to global instance, user-specific, the separate workspace or sub-directories, please see the Settings layers.

I'm quite astonished about the lake of reaction concerning workspace.

Does everyone things its intuitive? For myself I find it whether intuitive nor documented.

I read: A workspace is created when you open a folder. In fact, a .fleet folder appears only, if you change something in the workspace setting. Exclude folder for example.

Its also there, that I would expect entries describing the folder added to a workspace. But no, where those are is a bit of a mystery.

And why should the name of the workspace be the list of the folders it contains. I have already a space with five folders. The name isn't to pretty anymore. Ok, Setting a pretty workspace name is not a priority, but iits  hopefully on the todo list.

So I understand wojciechK questions and hope there will be some clarifications.

Hello!

I've somehow missed last comment. Just for clarification I'd say that directory shouldn't be considered as a workspace. 
What I think a workspace is: a bunch of directories of my own choice. 

What I'd like to see:

1.  When I open a "new workspace" I'd like to choose one or multiple directories to work on (this works as expected) and to be able to save this directories bundle for a future (this is wat I requested as a feature). Right now if I'd like to go back to this bundle, I have only an option to choose from recently used ones, but if I'm having multiple sets that I might be working on, this might be not enough. 
2.  I'd like to see 3 different type of settings (top one in this list should be most important):  
   - Per directory
   - Per workspace  (bundle of directories)
   - Overall settings

Thank you very much wojciechK and Christoph von Siebenthal for your feedback!

> In fact, a .fleet folder appears only, if you change something in the workspace setting. Exclude folder for example.

>Its also there, that I would expect entries describing the folder added to a workspace. But no, where those are is a bit of a mystery.

Christoph von Siebenthal not sure I 100% understand what you mean. Do you mean the icons for the 'Files' view items? If so, please feel free to vote for FL-15084 bring back folder icons request.

>And why should the name of the workspace be the list of the folders it contains. I have already a space with five folders. The name isn't to pretty anymore. Ok, Setting a pretty workspace name is not a priority, but iits  hopefully on the todo list.

Christoph von Siebenthal you can rename the workspace. Just click on its name. Does this help?

>When I open a "new workspace" I'd like to choose one or multiple directories to work on (this works as expected) and to be able to save this directories bundle for a future (this is wat I requested as a feature). Right now if I'd like to go back to this bundle, I have only an option to choose from recently used ones, but if I'm having multiple sets that I might be working on, this might be not enough. 

wojciechK could you please give some use case examples of how you would like to use it and why the existing functionality cannot help here? Thank you!

>I'd like to see 3 different type of settings (top one in this list should be most important):  
- Per directory
- Per workspace  (bundle of directories)
- Overall settings

In fact it is possible in Fleet:

Workspaces allow for nested settings in their subdirectories. You can use them to achieve any level of granularity when you need custom settings for subdirectories.

Have you tried it, does something not work for you? Thanks.

Hey, I stumbled over this while searching an answer to more or less the same question.

I think the feature request is about the possibility to have the workspace as something like an own entity, with the ability to:
- add the directories one needs for work
- configure workspace wide settings
- being able to share this workspace with e.g. the team by simply pushing it to the "team-workspace-git-project".

Imagine something like this:

~/code
├─ team-workspace
│   ├─ .fleet   (workspace structure and settings)
│   ├─ readme.md
│   ├─ ..
├─ service1   (added to workspace as ../service1)
├─ service2   (added to workspace as ../service2)
├─ ..

It's a pretty common feature in all the IntelliJ IDEs (Project / Module, persisted in .idea dir) and VS Code (Workspace, persisted in .code-workspace file).

Especially the persistence is something that I miss in the current implementation. This enables one to setup a working structure and settings for the whole team and have one place to maintain them. Currently one would have to maintain the settings in every directory's .fleet dir to stay consistent, as the next higher settings layer is the user's one. The settings per subdirectory is usually not the way to go as every "main" directory is an own git repository.

Hey, thanks for answering.

Well, we use a workspaces per project, wich then includes a number of repositories that everyone working on that project needs.
Currently we use VS Code for that as it provides a whole lot of features. Speaking of what we share, or features we use, our workspace files usually consists of the:
- `folders` for the workspace structure
- `settings` for config, e.g. database connections, language specific settings
- `tasks` for run configurations of the local dev environment
- `launch` for the debugger configurations of the services (sometimes placed in the services themselves)
- `extensions` for.. well.. extension recommendations for this project :)

I would say the must-haves would be the structure and settings / configuration part, as this would really improve usability and maintainability of this feature.
The whole run- / debugger-configuration part is something that we definitively use every day as well, but using VS Code to do only this would be an ok-workaround for me, even if it would be super awesome to be able to switch to fleet completely.. ;)

I would like it to function similar to VS Code project manager plugin. https://github.com/alefragnani/vscode-project-manager. I agree with the OP - only having "Recent" workspaces available is awful. We need a place to manage / add / remove workspaces in a single location. For the VS Code plugin, there is a JSON file that contains all projects with the below schema for each project: