[openbeosstorage] What I've Been Up To

Hi everybody,

I got doxygen up and working on my machine this morning and
so far I'm pretty impressed.  For a little bit of work, you 
automatically
get html docs with a ton of cross referencing built in. 

/storage=5Fkit/docs/doxygen=5Fconfig:
this is a generic config file generated by doxygen with a few
customizations. It currently only looks for *.cpp and *.h files in
./source/lib (and thus doxygen must be run from the docs folder).

/storage=5Fkit/docs/html:
this is what was generated by executing 'doxygen doxygen=5Fconfig' 
in the storage=5Fkit/docs folder of my working copy of CVS. Now that 
I've added them, I'm not sure it's really necessary for us to keep 
these 
generated docs directly in CVS.  The build system should generate them 
automatically once it's finally in place, and until then, we all ought 
to be 
able to set up doxygen on our own machines and generate off a CVS 
copy. I'll probably delete all the files in storage=5Fkit/docs/html in a 
few 
days, and tell Ithamar not to recreate the html folder when we
switch to the new system.

/storage=5Fkit/source/lib/Path.cpp,Path.h
I started working on BPath to get a feel for doxygen and try and
figure out what a reasonable amount of initial documentation might
be. What do you think=3F

/storage=5Fkit/source/lib/Error.cpp,Error.h,Test.Error.cpp
I renamed the *SKError* files to *Error*. Since they're going
to be for private use and in the private hierarchy under the
new build system, I thought it made sense. I also updated
the Error class to be a little more robust, added doxygen
dox comments in Error.h, and updated everything to conform
to OpenTracker style guidelines.

-Tyler

Other related posts: