* Class Library Documentation ** Summary While using inline XML tags to document classes is certainly convenient, properly verbose documentation quickly overwhelms the code, making the source quite difficult to read. Furthermore, multilingual documentation makes for significant additional text. With these considerations in mind, Mono will use external XML files for type documentation, rather than documenting the source inline. Several tools will be created for managing, verifying, generating, and updating class library documentation, including: ** XML Documentation Files and Formats *** Monodoc XML This XML is Mono's documentation format. Documentation and a DTD/Schema for Monodoc XML is located in cvs and can be found here. This XML could be generated by MonoDoc or the ASP.NET client. More about the XML format here. ** Documentation Tools *** MonoDoc A graphical documentation editor and viewer. Currently, MonoDoc consists of a Qt# application and is in heavy development. *** MkMaster This tool creates the Master.xml file that MonoDoc uses as a reference for documentation generation. This is a reflection engine that is used to gather metadata from assemblies and create an xml representation. *** ASP.NET This tool is planned. *** An XSL converter This tool is planned. If someone wants to step forward and adopt this project, it would be very helpful ;) ** Status and Roadmap *** 16, September 2002 A preliminary version of MonoDoc is in Mono's cvs. It is under heavy development. Once this is complete we will start documenting the API! ** Get Involved Help us develop Mono's documentation tools! Subscribe to mono-docs-list and wade right in.