On 11.09.08, rgheck wrote: > Rich Shepard wrote: >> On Thu, 11 Sep 2008, Steve Litt wrote:
> I think part of what Steve wants, which other people have also wanted, > is to be able to keep the layout file with the document ... Yes, I want to have additional styles for personal use but at the same time to keep the option to send my document to a colleague without with just the LyX standard layouts. > The layouts module in 1.6 will alleviate this problem somewhat. In most > cases, I suspect, the reason people will have lots of layouts is because > they have various customizations to some base class that they want to > apply in different combinations for different projects. This is > precisely what layout modules are for. I am looking forward to this much cleaner way of adding my styles to the standard classes (hopefully a stable 1.6 is out soon). > That said, sometimes you just want to add some layout information to one > document. or, as stated above, to ship your private extensions with the LyX file. > ****** > WARNING: Read what follows at your own risk! > ****** > LyX 1.6 includes a facility that can also be used for this purpose. I > call it "local layout". > ..., this is just layout information, embedded directly into > the document. LyX reads it, if it's there, and uses it. > There is, as yet, no UI for this, because it is really quite > experimental and may prove dangerous. How about an "embed" button for selected modules? This way it would be easy to create self-contained lyx documents with private styles. You can create and test a module in ~/.lyx/layouts/ and if you want it in a document for others to use, simply embed it. (It will still show up in *your* modules list but not in everyones.) > it'll be a trivial matter to add a simple UI, like the one for preamble. > With appropriate warnings. Maybe this is not even needed with an "embed" button for modules. But still a possible supplement for one-off layouts. > Personally, I don't want to see this overused. Part of the point of the > way LyX uses layouts (and soon, modules) is to promote reusability. > Local layout is not reusable except by cut-and-paste, and that's not > really what one means by "reusability". But there is also the problem with compatibility. My private reusable modules can (currently) not be used in files that should work everywhere. Maybe there could be an "extract-module" tool, that can extract embedded modules to ~/.lyx/layouts/ Günter
