On 18 Feb 2003, Jean-Marc Lasgouttes wrote: > >>>>> "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes: > > Christian> PS. Speaking from my experience with a multipart document, > Christian> it's a real pain with GUI's when one file gets a different > Christian> layout than another... it's simply not fun clicking through > Christian> all the dialogs and tabs, trying to figure out where you > Christian> have a difference. DS > > What would be a good solution to that? We could decide that, when a > file you want to typeset has a parent loaded, it will use the buffer > parameters of the master instead of its own. But wouldn't that create > more problems that it would solve?
A good solution would be an external inset that imports (user-selected) settings from another lyx document... :-) It doesn't have to be an external inset of course, but since I just replied to your other mail... Using a separate file (.tex-file \input in the preamble) to define the style/layout was also good when I only wanted to focus on layout... i.e. you're tweaking the settings and want a simple document that's quick to compile --- but you totally ignore the actual content. I also liked having a separate text-file for controlling layout. One reason was just given, another is that it appeals to me to be able to separate control of content and appearance. The fact that it was plain text made it easy to find settings in it. However, it was probably also easy to find settings because the text file only contained changes from the default document class, i.e. only the relevant settings where in the document. A drawback is of course the need for using obscure packages and writing latex... from that point of view it'd be easier clicking through dialogs in a "document-layout-template". To conclude, I think that for the "medium-level" user, it'd be enough to specify the name of another .lyx-file in a dialog and choose some pre-defined sets of settings that he'd like imported. To give the "advanced-level" user room to maneouver, I think the solution based on an external-inset is more usable. Then you can have the decision on what settings be made automatically. It's probably less work in the long run with the external-inset solution, since you don't have to spend time updating dialogs as more settings appear. /Christian -- Christian Ridderström, +46-8-790 91 37 http://www.md.kth.se/~chr Mechatronics lab, Dept. of Machine Design http://www.md.kth.se