Just my two cents worth: 1) I like the lyx format as it is BECAUSE it is not compressed, so I would definitely not change the default format.
2) I like the idea of an export format, which effectively compresses all files necessary into a single file. This is very nice for archiving final documents (lets call it .lyxa for lyx Archive). 3) .lyxa should represent a directory tree, in which subfolders hold pictures, bibtex, ... files. 4) .lyxa should be usable directly, i.e. the .lyx document should be modified during export to contain only a) relative paths which b) only are in subdirectories of the location of .lyx 5) .lyxa should contain information of the original location of the foles on the system where it was created, to be able to update the files not in the subdirectory. 6) One should be able to open a .lyxa file (which would modify the files in the .lyxa but not the original location information (from 5)) or imported (showing the differences of the files in the .lyxa and the original files and update the files when confirmed from the ones in the .lyxa) In this way, the .lyxa could be used as a colaborative tool (original author exports, sends .lyxa to other authors, they open it, save it, send it back, oroginal author imports it and confirms the files which should be overwritten) and as an archive tool of finalised documents. Cheers, Rainer On Fri, Apr 17, 2009 at 8:24 AM, Niko Schwarz <niko.schw...@googlemail.com> wrote: > On Mon, Apr 13, 2009 at 7:32 PM, Etienne lepercq <e.gu...@gmail.com> wrote: > >> >> >[self-contained lyx-files] >> I think this feature should be at least re-discussed. > > > I for one have had large troubles when asking people to cooperate with me, > because I had to give them precise instructions how to set up lyx. The image > relative path thing I could solve by making lyx find the pictures using > relative paths and otherwise sharing the folder using dropbox, so i didn't > need to tar/untar anything. What was REALLY difficult was the .module I had > written for the document. It cannot be accessed by a relative path; it needs > to be inserted directly into the lyx tree. On OSX, I have to redo the module > installation procedure on every update. > > I would like to point to how pages treats its documents. Pages documents are > identified with directories, which contain the required images, texts and > properties. No zipping into one archive is done. OSX then makes the > directory look like a file (called a package) in finder. > > I think, sharing lyx documents would would be simplified by providing > self-contained bundles that can be shipped around. > > Niko > -- Rainer M. Krug, Centre of Excellence for Invasion Biology, Stellenbosch University, South Africa
