On 10/12/07, Jeffrey Harris <[EMAIL PROTECTED]> wrote: > Hi Morgen, > > Moving this to the design list, since I don't think ultimately it's a > Cosmo issue... > > > 1B) Publisher plus read-write ticket subscribers get to rename it > > How about 1B plus a bit of 2, we pop up a dialog when a shared > collection rename happens and ask if we should change the name on the > server? If we don't have permission to change it on the server, we > don't pop up the dialog. > > If we make a local change, we permanently disconnect the local name from > the server name. Perhaps one day we'd add a feature so you can reset > the name linkage from manage shares. > > Sincerely, > Jeffrey
Well, rather than pop up a dialog, I'm tempted to just let the owner change the name on the server. Since I don't think my proposal made it to this list here it is: Anyone can locally change a collection's name but only the owner of the collection is allowed to update the master name on the server. When the client syncs and receives an inbound collection name change, the change is applied locally iff the client hadn't previously renamed the collection. This means that if I subscribe to your collection and don't rename it, but you later rename it, I'll see that name change. However, if I have renamed it (to include your name in the title for example), I will disregard any future renames you make. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
