> As Asger has explained (or at least as I understand it) Asger's InsetText
> is just a fancy InsetString (a string of text with some extra local font
> change info). Its got almost nothing to do with the InsetText from the
> current code base.
Yes, that's right.
> Asger's InsetParbox is more like an improved version
> of the existing InsetText (your InsetText (and Juergens)).
No, that's wrong. The InsetText that Alejandro and Juergen implemented is much
more complex than the one I propose.
> Asger's InsetParbox flows text and insets by managing the flow of the
> different insets in its vector<Inset *>.
No, it's the Paragraph object that manages the flow. The InsetParbox contains
a list of Paragraph objects, but InsetParbox only knows how to flow a list of
rectangles beneath each others.
The Paragraph object is more clever, since it knows how to flow the
three-rectangles-on-top objects.
> A bit more complicated than the
> existing InsetText -- it would probably be easier if each inset could flow
> itself and then Asger's InsetParbox would have a simpler job of managing
> the flow. That may in fact be what he wants I'm not sure.
The InsetParbox flow control is simple: Ask each paragraph how high it is, and
then ask them to draw them selves under each others.
Greets,
Asger
