> | Skipping all the failed attempts, right now, when you insert a figure, > | or later any child document like program listing, it can be marked as > | 'include this file when saved in bundled format'. This does not change > | anything until you select 'Document -> Save in bundled format'. > > Mmmm... I even thing that should have been the default.
I tried really hard not to change the way users work ... Right now, use of bundled (zip) format, and embed external files only happens when a user choose 'Save in bundled format'. > | Now it comes to the 'embedded child document' inset introduced by this > | patch. You are right that this is a trick to bundle arbitrary file, > | but this is a natural way to do it. > > And this I dislike. IMHO we should not support that. > We don't need support for embedding arbitrary files to support this. > IMHO we should add explicit support for the above instead. We can add [x] embed layout file [x] embed class file but the problem is that it is difficult to determine which files to include. We may need .layout, .module, .cls, .sty, and they may exist in the users or system directory... > | I can of course use a new inset type, but that would be a stripped > | down version of InsetInclude. I can also allow user to enter such > | files in Document->Settings->Embedding. Maybe you would like the > | latter option? > > If by "such files" you mean "embed other files directly related to the > document", then yes I would. OK, I will reconsider this possibility. I have pointed out the problems with this approach in another email. Bo
