I'm trying to distill the rules for insets and paragraphs...

* Inset classescan only hold a single inset object.
* Paragraph objects are not an inset, but may contain more than one
inset.
* Paragraph objects may be inserted into an inset tree using an
InsetText object.

All this must make it rather difficult to traverse the object tree.
Surely we need a CompundInset or similar, the father of all insets which
can contain more than one sub-inset. This simplifies ieterators
enormously.BNut then what happens to the text between the insets?
Perhaps a new inset is required for straight text.

I am reminded of the design patterns book here, which has an extensive
example of one way of doing this. if this has been discussed here
before, could people point me to the discussion?

Thinking aloud,
Ben.

Reply via email to