At 09:59 AM 10/5/2005 -0700, Bryan Stearns wrote:
However, in other places in our grand hierarchy of blocks, we need to be
able to dynamically change a subtree hanging off that particular point. It
happens that there are three places where we do this currently:
- The most obvious case of this is the detail view: depending on what kind
of item you've got selected in the summary or calendar, a particular "tree
of blocks" is built for displaying that kind of item, and that's what you
see in the detail view.
- If you think about it, you'll realize that this also happens at the
point between the sidebar and the main content area: depending on what
collections or views you've got selected in the sidebar, you'll see a
different tree of blocks displayed in the main content area: the summary
table + DV, the calendar + DV, the repository viewer, etc.
- We also have one of these points at the very root of the block
hierarchy; this is the way John implemented "skins".
So, back to naming: The block off of which we hang these trees of blocks
is currently named TrunkParentBlock, because it's the parent to a single
block, the 'trunk', of one of these trees of blocks.
We can't use "view", which already has special meaning for certain blocks
at other points in the tree.
Any other ideas?
Well, you used the word "point" 3 times above. How about "visual extension
point", or "GUI plugin point", or some combination of similar words?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
