RE: About the paragraph object.

["Frank A. Christoph" <christo@xxxxxxxxxxxxxxxxxx>]

> Thanks, I forgot to mention the "inlines" objects you mention. I
> upgraded my
> mental model, and do modification on the paragraph object document. I
> already did some additions this morning (at early hours) like
> including more
> explainations and illustrations on "Area" and "Area containment"
> concepts. I
> am actually working more on the visual model. Later on, with the help of
> Peter Nilson, I'll include the "tactile" model. What's missing now is an
> "aural" model ;-)
>
> By the way, what is your suggestion on how to illustrate a "port".

"Port" is just an obscure way to denote an edge in the flow object tree, and
"port specifier" means edge label. For example, in a syntax tree, a "+" node
has two "ports" labelled "left summand" and "right summand." The only
significant difference is that a FO port's target is actually a sequence of
nodes, rather than just a single node.

There is also a "typing" condition that some ports only accept inline or
display objects or what-have-you, but that is analogous to a well-formedness
condition for syntax trees, and doesn't really have anything to do what we
might call the topology of the tree (whether it has multiple edges between
nodes, etc.). For example, a sum is usually not well-formed if either
summand is a string node. (Well, it is in Java, but that's another story.)

--FC


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist