Bug 75454

One of the things I find very annoying with iFolder (sorry), is that I cannot
specify the name of the iFolder Collection at creation time or the folder name
at setup time.  Let me walk you through a couple scenarios and you'll see where
I'm coming from.

Scenario #1:

Bob has a folder on his computer named, "mycoolpictures," where he puts his
pictures.  He'd like to share the folder with other people so he converts the
folder to an iFolder.  He adds Joe as a member.

Joe receives the invitation for "mycoolpictures" but coincidentally, he's
already got another folder named "mycoolpictures".  So, now Joe has to break his
own conventions and setup the iFolder in a non-standard location on his computer.

It would have worked better if the following happened on Bob's computer when he
created the iFolder:

1. In addition to specifying the domain in which the iFolder should be created
in (i.e., on the same dialog as that), there's an additional text field entry
labeled, "Shared Name", "Share Name", etc.  The "Shared Name" is filled in with
the actual name of the folder by default.
2. Bob can either just press the Create Button to accept the default, or he
could change the shared name from "mycoolpictures" to "Bob's Photos".

Assuming Bob created the iFolder with a shared name of "Bob's Photos", he now
has a local machine mapping for the iFolder.  On his computer, the iFolder
named, "Bob's Photos," is stored as "mycoolpictures."

Continuing with this thought, Joe now receives a new iFolder whose name is much
more descriptive.  In addition, when Joe is prompted to setup/place the iFolder
on his computer, he should also get a prompt for the local folder name that
should be used.  In other words, Joe creates his own local mapping for the
"Bob's Photos" iFolder.  Joe could setup the local folder to be named, "Bob's
Overrated Pictures".

Scenario #2:

Assuming we have the new capability described in scenario #1, Bob, on his Linux
computer has a folder named "pictures" that he wants to share.  He likes using
lower-case folder names in Linux, but he creates the iFolder with a shared name
of "Bob's Pictures".  When Bob logs in to iFolder from his Windows computer, he
sees "Bob's Pictures" as an available iFolder.  In Windows, Bob likes to use
upper-cased folder names, so when Bob sets up the iFolder, he creates it with
the name of "Pictures" (upper-cased 'P').

By adding this local name mapping feature to iFolder at creation and setup time,
we remove these limitations/problems:

1. Users cannot give meaningful shared names to their iFolders
2. The names of available iFolders (not setup yet) may be meaningless
3. Users are restricted where they're able to setup the folder on their
computers because of naming conflicts
4. Users are not able to follow their own naming conventions they may have
established on their different computers

Just as a note, the newer version of Glyphmarks, shares Bookmarks Collections
this way.  At creation time, users can accept the default name, or give it a
name that it should be shared as.  At setup time, users can accept the default
shared name or give it a local name that it will be stored as.  I only mention
that here to say that this feature is possible.