> But if a layout composer comes later (we hope so) the problem remains. So I > don't see how the situation has changed.
The only feature I want for lyx 1.7.0 is a layout composer, but nobody has a clear idea on what is actually needed. Will we toss *.layout altogether and embed .layout to .lyx? Will we keep .layout and use this interface to modify it? In the first case, we can remove all system and local layout files. In the second case, this feature helps because we are more likely to derive a local layout from a system one and modify it. > Pro: > It allows for self contained bundle that work anywhere. LyX layouts + latex > classes + lyx document The bundle feature encourages the use of local layout and class files. It is supposed to let users open a .lyx file with embedded customized .layout files. It only makes sense to allow creation of a .lyx file from a local .layout file (which is likely to be bundled later). > Con: > We need stricter tools to update the layout files. We have already the > layout2layout files but we need a strong architecture before allowing the > widespread of isolated layout files. A system layout file is ignored if there exists a local copy. I do not see a big problem here. Cheers, Bo
