>>>>> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> I have thought a bit about how our basic, fundamental document
Asger> text representation data structure should look like. My best
Asger> bet so far is this:
Asger> A document is a list of paragraphs. A paragraph is a list of
Asger> insets!
Yes, I like that.
Asger> In order for this to work, we would declare a basic
Asger> InsetString. This inset would be able to hold nothing but an
Asger> LString and a character level properties reference. In reality
Asger> this inset owuld would be the bulk of the InsetText.
Good.
Asger> Now, the good question is whether a paragraph should be an
Asger> inset in itself. I don't know. Similar for the document:
Asger> Should a document be an inset in itself? Again, I don't know.
Asger> They probably should, but this makes designing the Inset base
Asger> class more complex.
I do not think a paragraph should be an inset. If we need to wrap a
paragraph somewhere, it will be in a parbox inset, for example, which
will have to contain some info (alignment htb, width of the box) which
are not part of a normal paragraph. Thus a paragraph cannot be
inserted directly in another paragraph. Thus a paragraph should not be
an inset, but a list of insets.
JMarc
