>>>>> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
[Andre' said]
>> I think, we missed some crucial point:
>>
>> If all is nicely structured as a tree internally, we do not even
>> need different types (insets? ;-P) of headings: The type of a
>> heading is indicated by its position in the tree, yielding a couple
>> of advantages:
There a a few things missing here:
- numbered/unnumbered heading (\section* vs. \section)
- optional caption (for LaTeX, at least)
- any other info that DocBook might want to place there
So, we *will* need a special class for headings.
Asger> We can achieve the exact same benefits in a simpler way: Have
Asger> one kind of HeadingInset that keeps a counter to indicate the
Asger> nesting level.
Yes, that's right [although I am not convinced by the 'inset' part;
but you know that already, don't you :P]
[andre' again]
>> - There won't be a hard-coded limit on the number of levels.
We'll have to control it in some way, in fact. But I agree that we
need more flexibility that we have now.
>> - Currently, moving from "article" to "book" *is* annoying, you
>> basically have to change every heading. With a tree structure it is
>> mainly a matter of specifying a book layout (of course, some
>> implementation of "book" has to define 'when exporting to latex,
>> level 1 is called chapter').
The semantics of 'moving from article to book' are not very clear to
me. The only time I did that was for my thesis, were I wanted to
insert articles as chapter of the thesis. Although I did not use LyX
at the time, the way it does it would have been fine with me.
Asger> This is also solved with a HeadingInset with a number.
>> - It would be easy to collect articles in some bigger document, say
>> conference proceedings. Just include seperate articles into the
>> master document at the right place. No need to mess around with
>> "section" and the like.
In this case the sections of the articles would have to remain
sections. I thought you wanted them promoted as chapters?
Asger> Also, having using the topology to denote the level of a
Asger> Heading is dangerous: What if we cut the heading to the
Asger> clipboard? How will we handle the level then? Do we need to
Asger> insert a bunch of blank nested headings for this? I say this
Asger> complicated.
Asger> We should not use the topology of the tree to hold this kind of
Asger> information, IMO.
Agreed.
JMarc
