Plugins + Scripts VaM Backstage - VAR Package Manager

[Miztress]

1.- Works great, thanks for the update. Labels are really nice and it remembers window state on reopen, and it really feels lighter and more agile.
2.- Maybe it´s obvious but how do the offload folders work? I created one in the preferences but how do i send packages to the offload folders and restore them from the interface?
3.- Another request hehe, would it be possible to add a button to add a Label to all dependencies of a package at the same time? That way it would help a lot to organize stuff... i attach picture to this purpose.
4.- Is it possible to show dependencies of a loose file the same way a package does? Maybe can´t be done cause of vam file structure or something like that, but if it is possible i would really love it

Thanks again for your work!

 

[poma]

Once you add offload folder you can change disable behavior to move files to that folder instead of renaming to .var.disabled

Label inheritance already works, if you assign a label to package all its content items will show up when you filter content by that label. I'm considering how to improve the way labels from package and its content can interact, like how to select all packages that have a content item with certain label to bulk enable/disable easily. Btw did you know you can multi select contents and packages to enable/disable or apply a lable to all selected items at once. Of if you want to label content items specifically and not package you can use multi select in content library to filter by package - select all - assign label.

Detecting dependencies of loose files would require digging into VAM scene and other formats, I'd like to avoid doing that. But if some open source plugin does that I may consider looking at its code and porting functionality to Backstage.

Update: oh wait I misunderstood, you want to label dependencies and not content items. I don't understand use case then. For example Timeline or Embody dependencies would likely be used by multiple packages at the same time. And in general Backstage assumes the user doesn't want to look at dependencies too much, and wants them out of sight and automatically managed.