Jean-Marc Lasgouttes wrote: > Angus> * InsetInclude should include LyX files only. Stored data: the > Angus> name of the LyX file. Nothing else. > > Currently, it can either \input or \include LyX files. Although I > understand that many people do not what the difference is, the > possibility is here.
Ok, I see this. > Concerning the simplification argument, I am not sure that having 20 > different external inset in a list is really a better UI than a dialog > inset that we can arrange to our taste. I'll have to think about this a bit... > As far as the code reduction is concerned these are a few dozens of > lines of trivial code, which do not cause any maintainance headache, > as far as I remember... Well, apart from the fact that I have just spent 10 hours getting it to work properly of course. > So my vote is on the good UI. If you can prove that it will be > simpler, then it could be a good move. My problem is that I don't think it _is_ good UI. We can actually do things with the LyX files, extracting labels and keys. The LaTeX files are just output and as such are handled perfectly by InsetExternal. -- Angus
