At 02:04 PM 10/5/2005 -0700, Donn Denman wrote:
Combining other's suggestions, I think the term "branch point" captures
the idea best.
Speaking as someone not intimately familiar with CPIA, I don't think that
"branch" gives me much useful information. It's understandable after an
explanation and drawing, but it doesn't seem to me to convey the aspect
that it's selectable or extensible.
That having been said, I don't have any better suggestions myself. :)
So, in the absence of a better name for the concept, I'd suggest
BranchPoint and Branch as the class names; the 'Block' part will be
redundant as soon as the blocks framework follows the proposed API
guidelines, since under those guidelines the classes would be referred to
as 'blocks.BranchPoint' and 'blocks.Branch'.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
