>>>>> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> I have an evil plan to use these InsetParboxes to allow more
Asger> sophisticated geometry: For instance, footnotes will either
Asger> derive from InsetParbox, or contain one, and then draw itself
Asger> intelligently inside ordinary text.
Asger> So, we would have things like this on the screen:
Asger> -- This is a demonstration[foot] of the new display structure.
Asger> --
Asger> In this situation, the foot note is collapsed. When we expand
Asger> it, I want the display to be something like:
Asger> -- This is a demonstration[foot|and what a demonstration it is.
Asger> Hopefully, it will demonstrate that a Parbox need not be
Asger> rectangular.] of the new display structure. --
I vote against that. I think the current display gives a better
WYSIWYMness to the foot note. As you show it, the user will not have a
clear view of how the footnote will look: imagine there is an
enumeration or a displayed formula in the footnote, for example. And
indents will not look right either.
Asger> The advantage of these three rectangles is not only that we can
Asger> do the footnotes like above, but also that we naturally can
Asger> handle things like hanging indents, and similar stuff this way.
Hanging indents do live in a rectangle, not in a strangely shaped
region.
>> Do you mean that ParagraphParams will be shared and use reference
>> couting like LStrings?
Asger> Yes, that's one feasible implementation. The point is that we
Asger> want to share the identical instances.
I'm not sure it will be easy...
Asger> The Paragraph class is the one that does the main logic of
Asger> flowing the text on the screen: It asks the InsetTexts what
Asger> they would like to have, and then distributes the areas
Asger> accordingly. In this process, it will also sometimes ask some
Asger> InsetParboxes to draw themselves in a given area.
Agreed.
JMarc
