i can create something like this in C#, can the community come together and form a list of requirements on some kind of application like this?
the main problem i have is, i have 250gb of vars and there are some looks i dont like, there are even some clothes i dont like but i am too scared to delete anything, i had a bad experience when i had my previous installation of VAM and i deleted some looks cause i didnt like them and all hell broke lose with the looks i liked. let me see if i can get some thing done about this some kind of var manager.
How cool to hear! Thanks,
mambo_no_1 ! Your scenario isn't exactly like the one I describe. You seem to have an established structure that you don't want to risk changing. My request is for a VAR management tool that manages which VAR symbolic links exist in your VAM installation.
Main things i would think of as features would be :
- scan for duplicates
- do a full scan of vars and extract all images so i can select what to delete and not by the image.
- show dependancies for a var and depenants, so i can see a var and see how many other vars this depends on and how many vars depend on this, so i can make smart choices.
- allow creator filters
1. Scanning for duplicates is cool and all, but there are already other tools for this.
2. Extracting the images from VARs sounds interesting. But could be very intensive on resources and not sure if it's always needed. Now if you were creating a VAR explorer, where you could step through the list of your VARs and it shows you what the first-depth images in that VAR, that might be very helpful for identifying what the VAR is (if it has images).
3. Dependency graph visualization seems pretty large in scope. Though a really cool feature is what you are suggesting that there is some understanding, based from all the VARs you have in your REPO, how many different VARs rely on the VAR, and which are they. That'd be cool for deciding if a VAR is worth keeping.
4. Creator filters are cool, but so would be like tag filters. If the program allowed for you to have meta-data associations that don't change the file itself, maybe those are things to filter on as well.
I'd like to see the following:
A. The ability to designate a REPO, where all my VARs exist.
B. The ability to peruse my REPO vars, and choose from them which I want to add to a specific VAM installation (TARGET).
C. The ability to resolve needed dependencies, that also exist in my REPO vars, or might exist on the Hub, and have them also added to the VAM installation --- without having to open VAM.
D. VARs would be installed by symbolic link in order to save hard drive space and not create redudant files.
might have been said, but you don't need to resolve missing dependencies. I have a ton cause I generally don't need something a scene comes with (I won't install postmagic for instance).
True, but most people won't know what is in each VAR expressed as a missing VAR reference. When I get the names, it doesn't tell me exactly what it is trying to use from that VAR.
mambo_no_1 , this would be another cool feature!
E. The ability to know what is being referenced from a dependency VAR by the VAR I am wanting to open.
anything else you guys can think of?
Thanks for engaging the community and being open to build something like this! I would love to hear what other users would like!