https://www.dendron.so/ logo
Join Discord
Powered by
What is the difference between a code workspace an...
# questions
m
What is the difference between a code workspace and a native workspace? I read this (https://wiki.dendron.so/notes/c4cf5519-f7c2-4a23-b93b-1c9a02880f6b), but I still don't understand when I should prefer one over the other.
k
main difference: - code workspace has a 
dendron.code-workspace
file and 
dendron.yml
file - native workspace only has a 
dendron.yml
file reason: we started off with only code workspaces but got feedback that users wanted to use dendron within *existing vscode workspaces. we therefore introduced native workspaces - as long as dendron discovers a 
dendron.yml
file in one of the folders that is managed by your current workspace, it will load it as a native workspace. > Well, if I just add to my VSCode workspace the path to the Dendron workspace (i.e., "path": "path/to/my/dendron/notes") then open a Dendron note and reload the window, Dendron gets activated and the look-up bar works. @User this is the intended behavior
@User ☝️
to make this even more confusing/simple - we are currently removing the workspace concept all together (because its been a major source of friction) and just having everything be a vault: [[42 Self Contained Vaults|dendron://dendron.docs/rfc.42-self-contained-vaults]] early preview of this feature will start with today's release 😅
m
Based on the main difference I think I would lean towards a native workspace. But does this mean that all the settings inside 
dendron.code-workspace
will be managed by 
dendron.yml
? Or will they have to instead be placed in a 
.vscode/settings.json
corresponding to each vault? I am referring to settings like 
"pasteImage.path": "${currentFileDir}/assets/images"
or 
"dendron.rootDir": "."
. I just tried moving, for example, 
"dendron.rootDir": "."
to a vault's 
.vscode/settings.json
and it didn't work.
Oh, I would be very curious to try out the new setup without workspaces.
k
the settings inside 
dendron.code-workspace
wouldn't apply if you open them up in a different vscode workspace. you would need to copy those settings into the parent workspace
preview signup here -> https://airtable.com/shr0cwk0a9tujeipZ 🙂
m
Ah! That was the missing piece. Now it makes sense. But I would still be curious to try the new setup without a workspace.
Thanks!
I feel like much of this would be way easier if VSCode supported opening multiple workspaces (https://github.com/microsoft/vscode/issues/43188).
k
agreed!
x
I like this, would it be possible to configure 
dendron.yml
so that I can have it in a 
.dendron
folder inside my "vault"? And also have all the files that dendron needs be created inside 
.dendron
? I tried doing this and tried setting 
vaults: -> - fsPath: ../
but it didnt work 😁
k
we currently expect 
dendron.yml
to be at the top level when used by itself. is this an important part of your workflow?
x
more a question of hierarchy and hiding stuff, for some reason which I cannot really put into words, I would prefer if the "vault folder" was the main folder. I could say "Here are my notes, and I use Dendron to mange them". Now it's "Here is Dendron, and in these boxes inside Dendron are my notes".
When you wrote "and just have everything be a vault", I imagined that each vault was self contained - "everything needed for the vault is inside the vault", and for multivault, you would just add multiple folders that each had a .dendron inside. So.. I'm not really sure of how the "self contained vaults" are different from the current structure? From the RFC it also looks like an additional folder is added (
dependencies
)?
If I am reading the RFC correctly, the situation is still that if I want to move my vault, I actually have to copy stuff from the parent folder of the vault. It's like saying a house is self contained -> off grid when it's still connected dependent on things outside the house, I can't just take the house container and move it, I also have to consider stuff outside the house container and replicate those at the destination.
if vaults had an id, defined in the vault's dendron.yml, just like notes, perhaps that could also be used to link between vaults (for multivault scenarios). ... I am aware that I am coming into this without any real understanding of the inner workings of dendron, so I do not know if this requires huge changes in the codebase 🙂 I also know the feeling of reluctance when somebody suggests a feature that requires that level of development 😂
k
> more a question of hierarchy and hiding stuff, for some reason which I cannot really put into words, I would prefer if the "vault folder" was the main folder. I could say "Here are my notes, and I use Dendron to mange them". Now it's "Here is Dendron, and in these boxes inside Dendron are my notes". got it. most of our users have been giving us the opposite feedback (eg. i want to share my notes as a github repo but currently, since the vaults is a flat folder of thousands of files, this is unwiedly) today's vaults:
Copy code
- vault/
    - lots of files...
self contained vaults
Copy code
- my-vault/
    - README.md
    - dendron.yml
    - notes/
        - lots of files...
    - dependencies/
        - other vaults...
the idea is that you can share 
my-vault
and you have everything you need to access notes, even when they are spread across multiple vaults
> If I am reading the RFC correctly, the situation is still that if I want to move my vault, I actually have to copy stuff from the parent folder of the vault. It's like saying a house is self contained -> off grid when it's still connected dependent on things outside the house, I can't just take the house container and move it, I also have to consider stuff outside the house container and replicate those at the destination. you shouldn't have to anymore with this change. we currently have the notion of workspace & vaults - a vault can't work by itself unless its part of a workspace. with this change, all vaults are "self contained" (aka they act as their own workspace)
> if vaults had an id, defined in the vault's dendron.yml, just like notes, perhaps that could also be used to link between vaults (for multivault scenarios). vaults have a 
name
property and you can link to a vault by name. see https://wiki.dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2.html#cross-vault-links
x
Ok 🙂 I don't agree that having a .dendron inside the vaults folder is different from "i want to share my notes as a github repo but currently, since the vaults is a flat folder of thousands of files, this is unwiedly" ... but isn't the structure with the self contained vaults the same as the not self contained vaults? Today:
Copy code
- folder A
    - dendron.yml
    - folder B/
        - lots of note files ...
    - folder C/
        - lots of note files ...
self contained vaults:
Copy code
- folder A/
    - README.md
    - dendron.yml
    - folder B/
        - lots of note files...
    - dependencies/
        - folder N
            - lots of note files ...
How is the situation different with regard to "i want to share my notes as a github repo but currently since the vaults is a flat folder of thousands of files, this is unwiedly"
k
so today, 
folder A
is a workspace. we currently recommend that you version workspaces and vaults separately. so users would need to share a workspace which then pulls down a vault (which is a different repo) after self contained vaults, 
folder A
would be a vault. you can version just the vault and collaborators would only need to pull down that to access all functionality
x
Ah, ok, got it!
m
Looking forward!
3 Views
PreviousNext
Powered by