I've put the following links up for anyone to use. It took a while to mold the documentation generated by doxygen into what I liked (by playing with the config file for doxygen). If anyone has any suggestions on how to improve the output, that would be great. I'm open to comments and suggestions as always.
This is the latest run for my doxygen adventures. I'm continually trying to tweak the output to get better and more streamlined results. This is the fourth test of the tool I've done, with slightly better results this time. Mostly, this is due to some tweaking of the dot output for the graphs.
Please be aware when navigating this documentation that certain core or central classes
(for instance THD) have extremely large collaboration and/or inheritance diagrams.
This means that you will experience LONG wait times when requested certain pages. Please be
aware of this fact while I work on a method for compression of the enormous PNG images generated by
dot.
You can find all the major collaboration diagrams and inheritance trees in the documentation, plus I deployed the doxygen SEARCH_ENGINE option to create an automated php search tool, which you can find in the top menu bar. This is extremely useful for finding a class or struct quickly and efficiently, considering the thousands of classes there are in the distribution
I built the docs with the Source Code generation as well (the SOURCE_BROWSER config option), so you can see both the source code for the headers inline, as well as the implementation files, that are linked to the classes and class members inline.
Here is the configuration file I used in this latest run. You can see I've excluded a few directories, notably, the /bdb directory, which, during my first few runs of doxygen, flooded the class member list with an array of poorly named functions and compounds. Since I don't use Berkeley storage engine for anything, and it has pretty much been replaced by the InnoDB storage engine, I omitted it from the generation. If anyone would really like to see it included, I might make a separate directory especially for that, but only if there's interest in it. You can email me with a request at 'jay' @ 'jpipes.com'
I've also included the internals.texi HTML formatting. Used texi2html to convert it.