< :the previous in number
^ :the list in numerical order
> :the next in number
P :the previous artilce (have the same parent)
N :the next article (the next thread)
|<:the top of this thread
>|:the next thread
^ :the parent (reply-to)
_:the child (an article replying to this)
>:the elder article having the same parent
<:the youger article having the same parent
---:split window and show thread lists
| :split window (vertically) and show thread lists
~ :close the thread frame
.:the index
..:the index of indices
>
>
> no, i think you missed the structure.
>
> Miter <- Table[] <- Section[] <- Cell[] <- Element[].
>
> a couple of people have suggested bringing everything into Top, i
> thought about it, but that defeats the whole purpose of OO design.
Rather than pass data down through a series of innocent by-standers, simply
to have low-level objects create yet-lower-level objects, why not pass the
objects themselves, fully formed?
el = El.new( a )
cell = Cell.new( el )
sect = Section.new( cell )
table = Table.new( sect )
miter = Miter.new( table)
I'm not entirely thrilled with a series of construction expressions, since
it seems to bundle too much control logic in one place, but it does avoid
having to needlessly expose data to objects.
Perhaps this could work in a MiterFacrory class, which accepts general
instructions on how to create the Miter and its constituents, returning the
fully-formed Miter instance.
my_miter = MiterFactory.create( someObjectHoldingEssentialMiterData )
James