On Wed, Aug 20, 2003 at 12:59:04PM +0300, Martin Vermeer wrote: > That requires > > 1) the ability to draw a more general outline / paint a more general > background than a rectangle. Almost trivial.
Indeed. > 2) A more general metrics model than the asc/desc/width (i.e., > treating insets as super-big quasi-characters, or 'TeX boxes') model > we have now. We'd settle for what we have plus baseline/indent of the first and third box. > I must admit to seeing only vaguely how it would be done. Somehow the > first box should receive the current x position of the text (for > redoParagraph to work out how much text it should contain), > and the third box should hand out that x position to the text following > it (OK, that would be trivial; the third box is just output from the > left edge with its dim.wid). The middle box would just go as a LyXText > on a line of its own using the needFullRow mechanism. > > Do you really envisage these three boxes to behave as three > quasi-characters each with its own metrics? No, its a unit. The boxes are just an implementation detail. Instead of simply gluing boxes as we'd glue "threeboxes" (and if we had proper abstraction this would even be transparante to user code. But currently to many objects fiddle with coordinates...) > That would work, I think. In that case the first box would know its > width in advance (from the current x position) and should "clip off" a > suitable amount of paragraph using redoParagraph/rowBreakPoint. OK. Is > that your thought too? We are doing full paragraph rebreaks after any "interesting interaction" anyway, so "knowing the width in advance" is a non-issue... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
