VMware Communities
blackpuma
Contributor
Contributor

It'd be nice if Fusion... displayName

Here's a wish list item:

It'd be nice if Fusion would support the VM names ("displayName" in the vmx file).

/Volumes/150GB External F... 400/vmware/mail/Mail.vmx is OK... but it's not terribly user-friendly.

Reply
0 Kudos
7 Replies
rcardona2k
Immortal
Immortal

I second this. It's been so long since I thought about this oddity that I've forgotten about it and just live with it. The list of VMs in Fusion reminds me of the output of vmware-cmd -l on other VMware platforms. Smiley Happy

Reply
0 Kudos
HPReg
VMware Employee
VMware Employee

Where do you see a file path instead of a display name?

1) VM window title bar

This one should use the display name. If not, please file a bug.

2) Window menu

This one should use the display name. If not, please file a bug.

3) File > Recent menu

This one should always use the file paths. This is common to all Mac OS applications.

4) Welcome window list

We want to re-design the whole window. Right now it uses the same model as #3, but we should use display names here. Can you please file a bug?

Reply
0 Kudos
rcardona2k
Immortal
Immortal

I was referring to case 4. This is now open SR request 346421.

Reply
0 Kudos
blackpuma
Contributor
Contributor

1) VM window title bar

Display name. OK.

2) Window menu

Display name. OK.

3) File > Recent menu

This one should always use the file paths.

Sort of. It has the file name, but not the full path. Personally I'd go with the full path or the display name, not just the file name. When I see two or three "Windows 2000 Professional.vmx" items listed, it's really quite useless (see #4 below).

4) Welcome window list

I see full paths, shortened by elipses (...) in the middle. It's kind of useless since two or three of these look identical. The critical inormation is hidden by elipses.

i.e.

/Volumes/150GB External F...dows 2000 Professional.vmx

/Volumes/150GB External F...dows 2000 Professional.vmx

/Volumes/150GB External F...dows 2000 Professional.vmx

So, which is which?

Reply
0 Kudos
HPReg
VMware Employee
VMware Employee

About #3 and #4: most of these issues come from the fact that we have trained users to name their VM file path by the guest OS they install in their VM.

That is, to my dismay, what the "new VM wizard" does by default.

If people named their VMs by what they do (i.e. what service they perform, like "router" or "database", or "CRM client"), we would not have that problem.

To make an analogy, nobody names their .doc documents "dissertation.doc". They call them "Renting vs buying comparison for year 2006.doc"

Reply
0 Kudos
blackpuma
Contributor
Contributor

If people named their VMs by what they do (i.e. what

service they perform, like "router" or "database", or

"CRM client"), we would not have that problem.

Yeah. I forget to do that half of the time, and just accept the defaults if I'm in a hurry. The use of the display name in the Favourites list makes it "no big deal" in practice. Now I find it's biting me in the butt.

On the other hand, I consistently give descriptive names when I add[/b] virtual disks beyond the primary disk.

Reply
0 Kudos
admin
Immortal
Immortal

Just for the record: blackpuma wins the award for the most amusing thread title so far.

Dude, you can claim a cash prize for this award. Just send an email to ... .com.

Reply
0 Kudos