Robert, *nothing* you are describing is a technical justification for
why implementations should support arbitrary nesting of collections. I
could very well just mark one of the collections in the workspace as
default="true" so that my user interface knows to show that one first;
or we could dictate that the order of collections in the workspace is
significant and that the first in the list is the "default"; or I could
just ask the user which collection they want to see as a configuration
option; the point is that there are lots of ways of solving the problem
you are presenting without introducing collection nesting. I want to
know why you feel that collection nesting is the best approach.
I don't really care what you think the right way to implement a user
interface is; that's not the issue.
Robert Sayre wrote:
On 10/26/05, James M Snell <[EMAIL PROTECTED]> wrote:
How I've implemented the current workspace stuff is irrelevant. You
still haven't answered my question about collection nesting.
However, to satisfy your curiosity,
James, it totally is relevant. Here's why. That entry you have with
"My Blog Entries" under main site... no one does it that way.
My Blog
|
+ Main Site
| + My Blog Entries
| | + { uri template }
| | + { uri template }
| + Documents
|
+ Side Bar Blog
+ Entries
+ Booklist
Same here with "Entries"... no one does things that way. When the user
clicks on "Main site" they want to see their entries... why not just
pop that up top? Then you could have multiple entry collections
without worrying about which to show by default.
Robert Sayre
