Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Shared studio shelves #1

Open
paulgolter opened this issue Oct 18, 2022 · 2 comments
Open

Feature request: Shared studio shelves #1

paulgolter opened this issue Oct 18, 2022 · 2 comments

Comments

@paulgolter
Copy link

Feature request

Would be amazing to enable the workflow:

A shared studio shelf that all artists can load

As I understand currently all shelf properties (script names, icons, etc) are saved in addons preferences.

Maybe we could have the option per shelf: Instead of saving all properties it in the preferences, save them in a .json file in the shelf direcoty on disk?

That could be essentially a new "shared" type of shelf. So if somebody updates the shelf properties everyone receives the update.

@Plyrolith
Copy link
Owner

Yup, good idea.
Thoughts:

  • JSON files for each shelf/directory
    • Write on save (? check write permissions first)
    • Load on init, after reading Blender preferences
    • Should some properties still be customizable per artist? Selective JSON dump? "Overrides"?
  • Environment variable for shelf path(s)

@paulgolter
Copy link
Author

  • Environment variable for shelf search paths is a fantastic idea and makes it way easier to use it in a pipeline
  • Load on init is a good idea, I don't think we need post load behavior, on blender start should be enough (Maybe optional reload button?)
  • Wirte on save is a good question. I think it would be good to have a functionality to "lock" a shelf. So artists don't accidently overwrite studio shelfes or remove scripts. Maybe rather having write on save a dedicated save button could be better. I think saving should be a concious action, especially for shared shelves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants