Up to now, we have three separate documentations for each of the three main
modules. It would be nice to merge them in a unified structure.
Furthermore, we should give meaningful names in the TOC (asizeof,muppy and
classtracker won't mean anything to most people). Here is a quick draft of
how this could look like (the layout is derived from muppy's docs):
* Sizing individual objects - Low-level interface (Asizeof)
* Detecting leaks/On-line analysis (Muppy) [couldn't think of a good name]
* Tracking class instances (ClassTracker)
* Library Documentation (for each module)
* Tutorials
A first step would be to split or replicate the library docs for asizeof
and lift the muppy documentation one level.
Original issue reported on code.google.com by lhae...@gmail.com on 7 Feb 2009 at 10:10
Original issue reported on code.google.com by
lhae...@gmail.com
on 7 Feb 2009 at 10:10