On Tue, Mar 16, 1999 at 07:12:01PM +1000, Allan Rae wrote:
[...]
>
> InsetEnvironment and even an improved InsetCommand will build most of our
> documents hierarchy. Headings and such are ultimately one of these two
> types and a simple linear list of paragraphs doesn't allow for the needs
> of environments in particular "\end{environment}". Thus a Buffer that is
> a list<InsetParagraph> is okay if we also allow InsetEnvironment to
> contain a list of paragraphs thus ensuring a much simpler scheme to
> output appropriate hierarchy markings like the \end{..}.
>
> Hmmm... Each of these can hold a list of Insets (which may be paragraphs)
>
> InsetParagraph
> InsetEnvironment
> * hierarchy support
> InsetCommand
> * maybe not this one but if we could come up with a scheme so we
> could figure out which commands can use a hierarchy (something in a
> .layout) we'd be in a position to better support collapsing and get
> out of hardcoding specific sectioning support into the kernel.
> TOC would then be based on info from the .layout rather than on
> specific info in the kernel.
There aren't any InsetCommands, in docbook or xml (here it's even worse
because it isn't possible to omit the closing tag).
Docbook enables to omit the closing tag for some tag ( the most notorious
case are sections, subsections ans such) and so the port to docbook was easier
than I expected (okay, someday, as soon as I have some time you will see
that implementation is not simple vapouware...).
All the fuss I have been doing is because of this: InsetCommand doesn't give
me any information where it ends and where it starts the next.
There are cases where it is very difficult even with external aids to solve
every possible ambiguity. Specially in docbook there are free floating sections,
where you don't its level, it is simply one more than the previous section...
Now that we are defining the new structure is the right time to tell my concerns
about this.
> Now then can a paragraph (text concept) or an InsetParagraph
> (implementation concept) contain/be a heading or a list or is it just a
> paragraph of text?
>
> That is should the three be peers/siblings in a Buffer or not?
[Mostly things I agree]
>
> Allan. (ARRae)
