On Thu, Jan 06, 2000 at 10:46:03AM +0100, Andre Poenitz wrote:
> > There are other issues, the insets aren't supposed to be configured
> > from the textclasses.
>
> I am aware of this but I do not know how this situation arose.
> Is it just heritage?
Partially it is heritage but I think that there are several reasons for
this. IIRC there were a discussion on this last year... Asger had some ideas
regarding this...
Also it is assumed that there is some data handling from the inset and
this can only be configured if you have a script language for the configuration.
I could be wrong but I think those were the reasons, and since a script
language is not very high in our priority list...
> Given that layouts are powerful and everything on a sub-paragraph level
> is much more messy, I'd say it'd be nice to be able to have
> sub-paragraph stuff in layouts, too. Is there any rationale behind the
> current distinction?
That is true, one of my most expected features is a better inset, and also
the possibility to have general insets.
The following applies mainly to docbook and certainly is relevant in a
xml context.
One of the most interesting sites about docbook is www.docbook.org, the
homepage of "DocBook: The definitive guide" published by O'Reilly.
When considering the different docbook elements, Norman Walsh places
a simple classification between paragraph level and inline level.
For me those are the same as layout and insets, and while I have been able
to put most of the paragraph level as layouts the only inline elements
that docbook supports are the existing insets.
I think that this is the distinction, layout are paragraph level elements
and insets are inline level elements, eventually presenting a better presentation
of the information...
For the moment this is worst problem I have with the present structure,
most of the inline docbook elements aren't supported in lyx.
Notice that the general insets I refered to could also be useful to latex
documents.
For example for the documentation we could have different insets to refer
to author name, for filenames, for button, menus or popup names. Ok, maybe this
is too much markup, but it is an idea, what do other think?
> Andre'
>
> --
> André Pönitz ......................... [EMAIL PROTECTED]
--
José
