On Wed, 14 May 2008, Bo Peng wrote:
I see some convergence of our approaches. This is a good sign.
But, my approach does not change .lyx file at all because it does not
have any bundled mode. Your approach will change a .lyx file when you
turn on the bundled mode.
I'm _so_ lost now... someone smack me if I post on this thread again...
Maybe this whole thing related to bundles should be dealt with through one
or more separate applications... when a consensus arrives on what the
typical use cases really are, their functionality could be integrated with
LyX. I guess the application would be some kind of file manager or
package manager that let's users choose what files to include.
LyX would need to be able to export a list of the files that are needed -
that's a starting point for sure. However, users may want to include
_additional_ files in the bundle. This could be a README or a data files
or whatever. Or additional .lyx-files if you do a multi-part document that
can be built from several .lyx-files[*]. If you think about this aspect,
it makes a bit more sense to consider it as a separate application.
/Christian
[*] I did my thesis this way. I could build the whole thing, different
parts or separate chapters. It actually was quite convenient. Would either
of the current bundles be able to support multi-part LyX documents, that
include files not explicitly referenced?
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
