[Cppqed-support] cmake/doxygen and python

[Raimar S. <rai...@ui...>]

Hi András,

as you might have noticed I integrated doxygen into cmake in the development 
branch. To build the documentation, just call make doc. You can edit the 
Doxyfile.in as you would edit the original Doxyfile. Only make sure that you 
prefix any path into the source directory with @CMAKE_CURRENT_SOURCE_DIR@, as I 
have done with the INPUT variable. The dependency cmake on doxygen is 
optional, if doxygen is not found the doc target will not be available.

The documentation will also be installed with make install. These changes make 
it easier to package the documentation along with everything else. You can 
soon see this in action when the new Ubuntu packages are built, there will be 
a new package cppqed-doc-2.99.

I have also created a new PPA "C++QED-daily-builds" (ppa:raimar-
sandner/cppqed-daily). This PPA will from now on contain automated daily 
builds of the development branch, for precise and saucy. This is also a good 
test if everything compiles for both 64bit and 32bit, you might have noticed 
that I found a quite peculiar bug on 32 bit platforms.

Finally, I am currently in the process of porting my python I/O branch to the 
current development branch. I have thought about splitting everything which is 
necessary and sufficient to define a trajectory state and the methods to read and 
write it into a new class (or new classes). The goal here is to create a 
minimal non-virtual base class that can be easily instantiated in the python 
code, not hijacking the Simulated class for this purpose. But I'm not yet sure 
how to do the split in practice, as it goes through both the Trajectory and 
Evolved, respectively. Do you think this is the right way to go?

Regards
Raimar