What should we call the thing formerly known as the Home Directory
Browser? bcm would like to get us away from thinking in terms of
traditional filesystems with hierarchical directories. I'd like to
not confuse the Casual Collaborator / end-user with terminology that
overlaps with UI-level concepts.
What sounds smells walks and talks like a Collection, but isn't
actually called a Collection? Any ideas out there?
+ Account Browser?
+ ???
Snippet of IRC conversation below:
14:04
hamstar >
bcm?
14:04
bcm >
yes
14:04
hamstar >
what do you think about Directory browser instead of Collection browser?
14:04
bcm >
directory is a filesystem concept
14:04
bcm >
i'm trying to move us away from that
14:05
bcm >
(i know that may be news to you)
14:05
hamstar >
I'm wondering if we want to keep the Collections users interact with
in the CC UI, separate from the things you interact with in the browser
14:05
Priss >
([EMAIL PROTECTED]) left irc:
14:05
bcm >
i don't think so
14:06
bcm >
i'd rather see us converge on a central notion of collections
everywhere in the server
14:06
bcm >
that's been a big part of 0.6 on the protocol side
14:06
hamstar >
yes
14:06
bcm >
in all the protocols we address things by collection now
14:06
bcm >
the only thing that uses the old hierarchical path-based addressing
is dav
14:06
hamstar >
but i think for the end-user, it might be confusing
14:06
bcm >
why?
14:06
hamstar >
because a collection browser could be something like the browser in
iTunes
14:07
hamstar >
whereas this is sort of an under the hood view behind the CC UI
14:07
bcm >
that doesn't mean the vocabulary needs to change
14:08
hamstar >
well i think it does if we don't want to confuse the CC end-user
14:08
hamstar >
it doesn't need to be Directory
14:08
hamstar >
but something that's different from Collection
14:08
bcm >
heh
14:08
hamstar >
yeah
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
