System.IO.Packaging is easy to work with because the resulting files are ZIPped folders, so you can simply rename the file to .zip and then open it. I do this with XLSX files to see how they are built.
Unfortunately, the reverse is not true; if you re-compress the folder and rename it .XLSX, Excel with say it has unreadable content. This is true even if the file is unchanged. If you simply rename, extract all, recompress, rename, the resulting file does not work.
Poking about inside, it seems the format of the file is not a canonical zip, header information is missing?
Anyone know an easy trick to recompress these files in Explorer? It would be nice to be able to test changes.
Is where a way to read/write multiple files in UIDocumentBrowserViewController.
Recently, I know UIDocumentBrowserViewController as rootViewController can read files. But how to write files.
For example, i want to read zip file and then unzip it to current folder.
I'm want to compile meshlab(http://sourceforge.net/p/meshlab/code/HEAD/tree/) and put the generated file outside the source directory to keep the source clean. Is it possible to just specify a build directory as the way in cmake?
The answer in this post Qmake and Make using separate folders for sources and headers, requires to modify the .pro file and doesn't work in my case. Users may want to specify the build dir path as they like, right?
I think what are trying to do is a QMake Shadow Build. This question about Manually Configuring Shadow Builds in QMake should help you.
Got a .jad and a bunch of .cod files. Can I view the contents of the .cod files? Thanks
.cod files are basically .jar files that have been processed through RIM's compilation tool chain. Additionally RIM tools strip some information from the .jar files before cod-ifying them and if the size is too big, it splits and zips the pieces. So if you have a bunch of .cod files for the same .jad file you should first try unzipping them using a standard zip program then join them using some concat utility and finally try using a .jar file decompiler to see if you can hack the byte code. That is pretty much your best bet.
When compiling latex documents the compiler emits a lot of "object" files. This clutters the directories I'm working on and it difficults the use of VCS like SVN. When I work with C++ code I have separate directories for the code and the objects, I can run make on the source directory but the .o files go to the build directory.
Is there a proper way to perform this separate compilation with Latex documents? Can it be done by using Makefiles or by passing options to the latex compiler?
Thanks
You can use:
pdflatex --output-directory=tmp file.tex
and all the files will be stored in the folder tmp (pdf included).
Because this is not an optimal solution, I made my own tool, pydflatex, that compiles the LaTeX source by stashing away the auxilliary files (using the trick above), and brings the pdf back to the current directory, so after compiling you only have file.tex and file.pdf in your directory. This plays very well with version control.
I can't help much with LaTeX (having last user it seriously 20 years ago;-), but for Subversion, you should read up on the svn:ignore property -- it makes it easy to ignore files with extensions you do not want to version (object files, bytecode files as Python can often put in the same directory as the sources, backup files some text editors use, &c).
Latex generates the temporary files in the directory where the main document is located. If you want the contents to be placed in a different location, try with a main file like below.
\documentclass{article}
\input{src/maindocument.tex}
Using this method, you could maintain a directory structure like below
/
main.tex
/src
maindocument.tex
Two options, besides the above.
Use Lyx: it looks after the separate files. I think it copies the Latex file over to its own private directory and runs latex on it. In any case, nothing is created in the current directory.
Use a makefile or one of the special Latex make programs, and have your regular targets run make clean.