>>>>> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Do you mean that a change of font would mean a change of inset?
Asger> Yes. This makes displaying of a InsetText simple, and we avoid
Asger> the ugly font-lists. I feel things are simpler this way.
Asger> (Notice that we can use an iterator as Kevin presented to
Asger> expose the text of a bunch of insets as one big string.)
One thing that I'd like to see taken in account is the proper handling
of fonts (at least in LaTeX): the scheme we use should be able to
output
Use \textsf{\underline{F}ile\lyxarow{}\underline{O}pen...} to open a
file
instead of the current
Use\textsf{\underline{F}}\textsf{ile\lyxarow{}}\textsf{\underline{O}}\textsf{pen...}
to open a file
How could we handle that? text insets inside text insets? How can we
get the optimal order of fonts right?
>> As I said earlier, I think it should hold either a plain box (in LR
>> mode) or a parbox (with fixed width). It makes not sense to include
>> a paragraph in a paragraph. And paragraphs should not be insets.
Asger> I agree that holding a single paragraph in a paragraph does not
Asger> make sense, but multiple paragraphs does. Consider a table.
Asger> That consists of an array of cells. Each cell consists of a
Asger> bunch of paragraphs.
Two things:
- a table is an inset; I never said that having paragraphs inside an
inset is not a good idea (think about footnotes)
- basically, a table cell contains *one* paragraph in LR mode. If you
fix the width of the cell, it will contain a list of paragraph (like
in a parbox).
Asger> I think the best way to get further in this discussion is
Asger> trying to outline the interface of the base class Inset. Then
Asger> we should do the interface for the paragraph class, and then we
Asger> can better see if things are similar, or very different.
Agreed.
JMarc
