> > I say this is simple because packing and unpacking only happen when a > > .lyx file is opened or saved. After the file is opened, all embedded > > objects are external so NO modification to the current inset code is > > needed. > > > > > > > And here's my view: Because this is so simple, because working with an > embedded file and working with an ordinary LyX file would, to the user, be > almost identical, and because it would keep us from having to mess with the > inset code, etc, I think it is absolutely obviously the best solution, IF > the problems Bo mentions can be solved. And I'm not at all convinced they > can't be. What I do know is that, unless I apply various workarounds I know > only because I understand the limitations of the current implementation, I > couldn't use embedding with my co-author.
Actually, I know only one limitation (assuming others are bugs), and this limitation exists from lyx 0.1. I mean, you simply cannot use a file with absolute-path on different systems. Bo
