Abdelrazak Younes wrote:
Previously, it just held an index into TextClassList, and extending
that would lead to solution (i). I suppose you could have some kind
of next TextClass-thingy that kept a list of modules that are in use.
But that presumes that the contents of the modules don't change while
LyX is running
Why that? If we point to the relevant module, why would you want to
discard changes in the contents of the modules. Sorry, I am an
absolute beginners with layouts.
You modify it on disk, then want to see the changes.
---and I'd like to avoid that, since it makes layout editing a pain
in the rear.
I take your word but I don't really understand the problem.
As things are, every time you modify the layout, you have to close and
restart LyX. Very painful. Worse than autotools. ;-)
Indeed, with the present change, there is no reason one cannot reload
a layout file after making changes to it, something that would have
been impossible before, and would still be impossible with any
index-based solution. This is something that EVERYONE who has EVER
done any real work on layouts desperately wants, with Steve Litt
being at the head of the line. And the difficulty of creating and
modifying layouts is one of the main barriers to LyX's wider acceptance.
I'd say, in fact, that this is the REAL reason to use a shared pointer.
Don't need to shout, I trust you ;-)
I was shouting for me. I only just realized this application, and how
important it is. Thanks for pushing me.
Richard
--
==================================================================
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==================================================================
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
