IPSW storage flexibility

[mcnahum]

I like the new way to create the VMs in the version 2. I'm used to select my own IPSW but I could use that new system and it will facilitate my life.

2 suggestions will help here:

• define the storage location of the IPSW files
• rename them on a more friendly name. I love the way used by MIST () :

[insidegui]

define the storage location of the IPSW files

This sounds reasonable, although it makes the implementation a lot simpler to have the downloads directory be managed by VirtualBuddy.

rename them on a more friendly name. I love the way used by MIST () :

This would actually cause issues with some upcoming changes, as the name of the IPSW file from Apple follows a certain format that will be used by VirtualBuddy to match user-provided images with those in the software catalog. This is crucial to allow the app to check for compatibility between host and guest, compatibility of the guest with virtualization features, and TSS signing status, all of which make the new setup experience significantly better.

In general, VirtualBuddy is more of a "shoebox" type app. It expects users to rely on the app itself to manage the VM library. I understand this is not ideal for everyone, but luckily other options exist for those who prefer to do things more manually.

[mcnahum]

Thanks,
I store my IPSW on my NAS to avoid to have to duplicate them between my Macs .. but maybe is not a frequent need.
I also do "cleaning" especially with all the Beta. maybe a delete option on the contextual menu could help there too.

For the naming it is less important, I just find my brain working easier with Name instead versions ..

I love VirtualBuddy and recommend to all people who need to test ... will not go to another tool 🥇

[insidegui]

I also do "cleaning" especially with all the Beta. maybe a delete option on the contextual menu could help there too.

Definitely. I plan on adding a way to manage previously-downloaded images in the app.