> I'll have to think about including it. It's a pretty specialized
> thing, and seems to me to be very much
> an "expert" capability (the way local layout was for a while).
I'm not sure. It could be very useful for novices, too. For
instance, let's assume that each branch contains the same text, but in
different language. It seems natural, that the user would like to have a
'title' field in the PDF (metadata) translated according to the active
branch. The "Preamble" env would be both simple and elegant solution for
this and similar problems.
Also I might be wrong, not knowing LyX internals and all, but to
me the ERT itself looks like kind of an 'expert' feature, and it can be
an overkill for novices, yet it is included in LyX by default. To give
you an example, look in the (oficially included) modernCV.lyx: there,
using the specific amount of ERT insets with '}{' is mandatory...
Anyway, it is not that important to include this simple module. It
can obviously be copied into a fresh LyX installation anyway.
> As far as the inset alternative goes, this is harder to do. I'm not
> sure we'd want this inset turning up
> on the last page of a document, and we don't really have any way to
> prohibit its being there.
If it is hard to do then just ignore this idea. The whole point of
it was that it would be simple to implement. However, when you say about
'prohibiting' something, I have my doubts... still, never mind - LyX is
now in beta phase, so including something hard could be dangerous.
Thank you for your time,
Michał Skrzypek
