Bo Peng wrote:
But the inset presentation will change, right?
Only when the document is organized for bundling. And please note that this
can be done externally by a python script such as the one proposed by
Enrico.
But the document is changed. Viewed from another machine, the insets
are different.
You are missing the point. My point is that once the document is
organized for bundle, it will not change.
and 2. backward compatibility,
I don't understand that one. If you talk about losing the original
filenames, yes that's a fact.
And this is not a problem?
This is not a problem for the external contributor, he is not interested
on your file hierarchy, only you are. And this information is not lost
for you of course, it is saved in the session info. This enables the two
contributors to organize the file in any way they want in a contely
different manner if they want. In a way, this is even more flexible than
your solution. As I said, if the external contributor is interested in
your file hierarchy, then you should discuss it and use a proper
solution for that (using an SCM or simply zipping the directory).
3. change of user's input.
Right, but as I said, IU view the bundling business only as a transportable
LyX file. And if you look back at my original proposal, the user won't loose
anything if the original embedded file paths are saved in the session.
So this is again not a problem to you?
Right.
I
mean, if a user craftes a beautiful directory structure, for example
bib, figure_chap1, figure_chap2, pack it and send it to another
machine. When he unpacks the file and sees changed insets and
directory structure, will he be happy?
Did you miss the "merge back" part of my proposal? I, as a user, prefer to
first view the change before accepting them. So no problem here as well.
On the other machine, the session file is not there. Even on the same
machine, the session file can get lost.
If it is lost because the user erased it then he is on his own.
Basically, why do you want to
separate the filename information to a session file?
Alleluia! :-)
I mean, why the KISS structure is the only rightful structure a user
can have? There are millions of reasons a user wants his own
structure.
And they should be able to keep their structure. I am distinguishing on
purpose the two things. This KISS structure is _only_ about the bundle not a
general way to organize your document of course.
Not an another machine, not on the same machine without merging.
Exactly.
I don't follow you, I was talking about limited editing _within_ LyX. LateX
won't call LyX's lfuns AFAIK ;-)
Of course the user will still be free to go the temp directory and edit
the embedded files if he really wants to. That'd be an expert user.
When lyx export to latex, the existing latex output may not work when
the files are in the temporary directory.
??? We do that kind of things all the time with the converter cache...
Abdel.
