Changes
* Rewrote doxywizard. It should be more easy to use and has much better
support for running doxygen from the GUI. Feedback is welcomed!
* Members of a namespace are now also added to the file in which they appear
* Included patch by Mikhail Glushenkov that fixed item 5 on the todo
list (titles of html pages are now internationalized).
* A macro defined in the config file can now be undefined in the source
code via a #undef.
* Optimized calling of dot using multiple -T flags at a couple of places
New features
* New option FILTER_PATTERNS which can be used to specify multiple input
filters, and let doxygen select the right one based on matching the
source file name with a specified pattern.
* id 142939: New commands \protocol and \category which can be used to
document Objective-C protocols and categories in the same way the
\class command does for classes.
* Included patch that removes some cosmetic annoyances in the man page output
* Added internationalization support for Afrikaans and Lithanian. Included
language updates for Dutch, Czech, Italian, Brazilian, Croatian, Japanese,
Norwegian and Russian.
Bug fixes
Changes
* The \param command now has an optional input and/or output attribute. The
syntax for an input & output parameter is for example: \param[in,out] name
Description.
New features
* Added new option CREATE_SUBDIRS which when enabled makes doxygen
distribute the generated output evenly over 100 subdirectories.
* Added support for Qt's properties (i.e. Q_PROPERTY) which can be documented
by putting a documentation block in front of the macro or by using a comment
block with the new \property command.
* Added new commands \manonly and \endmanonly to enter man page specific
text and commands in the generated man pages (thanks to Carsten Stiborg).
* Included new python based translation report script, which now replaces
the old perl based version (thanks to Petr Prikryl).
* Improved parser to also support parsing of Objective-C implementation files.
* Added new config option EXTRACT_LOCAL_METHODS which can be used for
Objective-C code to extract methods definition in the implementation section
that are not present in the interface.
* Added new config option STRIP_FROM_INC_PATH which allows to specify a list
of paths that, if matched, will be striped from the #include statement in
the generated documentation of a class.
* Added new command \includelineno with works as \include except it will add
line numbers to the code (thanks to Giancarlo Niccolai for the patch).
* Added BeOS support, thanks to a patch by Mark Hellegers.
* Included update for the French translation, thanks to Jacques Bouchard.
And many bug fixes. For a complete list see:
http://www.stack.nl/~dimitri/doxygen/changelog.html
Changes
* For projects with many nested classes, namespaces, typedefs and using
statements, doxygen could become very slow. This should now be improved
significantly.
* Made some cosmetic changes to the HTML output.
* STRIP_FROM_PATH now by default strips the path from which doxygen is run
New features
* Make a start with adding support for Objective-C. Doxygen can now parse
Objective-C header files (including protocols and categories).
* Include a patch by Hauke Duden which adds preliminary support for the
D programming language (see http://www.digitalmars.com/d).
* C Comments inside #defines are now preserved. This could be useful
to document boilerplate code.
* Included patch to replace tabs by the proper amount of spaced inside code
fragments in the XML output (thanks to Alexandr for the patch).
* Examples (documented via \example) are now included in the XML output.
* New option SORT_BRIEF_DOCS which when enabled will list the
declaration section of the documentation (with the brief descriptions)
in alpabetical order, instead of declaration order.
* Included patch for Hungarian translation (thanks to Akos Kiss) and for
the Serbian language. Added support for mixed Korean/english (thanks
to Jihoon Chung). The translator report script was also updated.
- teTeX 1.0.x packages have been moved to teTeX1* directories.
- teTeX 2.0.x packages have been moved to teTeX* directories and their base
name has been changed to teTeX (instead of teTeX2).
- Bug fixes
- New features
* Added new debug flag "-d Time" which will report the elapsed time for each
message printed, and will also show the total running time along with the
time spend on external tools such as dot. Note: If you have a project that
takes doxygen a long time to process, please send me the output so I get
a global idea where to optimize.
* New option SUBGROUPING which can be set to NO to have \nosubgrouping for
all classes (thanks to Torben Koch for the patch).
* Added XML schemas for validating the XML output, and to help writing XSLT
files. The generated index.xml now has a complete schema, the compounds
not yet. Thanks go to Alexej Humbach for doing a lot of the work. Note
that a couple of "id" attributes in the XML output have been changed to
"refid", and section tags are now nested.
* Included language updates for Traditional Chinese and Japanese.
doc/translator.pl, which has the side effect of allowing the docygen
package to be installed properly if you don't have '.' in your path.
Bump PKGREVISION.
all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
Doxygen is a documentation system for C++, Java, IDL (Corba, Microsoft and
KDE-DCOP flavors) and C.
It can help you in three ways:
1. It can generate an on-line documentation browser (in HTML) and/or an
off-line reference manual (in LaTeX) from a set of documented source
files. There is also support for generating output in RTF (MS-Word),
PostScript, hyperlinked PDF, compressed HTML, and Unix man pages. The
documentation is extracted directly from the sources, which makes it
much easier to keep the documentation consistent with the source code.
2. Doxygen can be configured to extract the code structure from
undocumented source files. This can be very useful to quickly find your
way in large source distributions. The relations between the various
elements are be visualized by means of include dependency graphs,
inheritance diagrams, and collaboration diagrams, which are all
generated automatically.
3. You can even `abuse' doxygen for creating normal documentation
