X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=doc%2Fclasslib-doc;h=b002b8efd552a37852b5a8317a21955f9d90493b;hb=f16a6fd00fccbc4aa09933183d5633f521bf5cb3;hp=49735af98b158feeec6444346c370b3b3789f8a5;hpb=0d446f192a5d7e9389c5f17c64637aaa709c882b;p=mono.git diff --git a/doc/classlib-doc b/doc/classlib-doc index 49735af98b1..b002b8efd55 100644 --- a/doc/classlib-doc +++ b/doc/classlib-doc @@ -2,104 +2,39 @@ ** Summary - - [This documentation is in progress. Comments to - jbarn@httcb.net.] - - 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. - + for type documentation, rather than documenting the source + inline. The XML file format used is inspired by the XML format used + to document the ECMA APIs. + 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 similar to the XML documentation described in the - C# standard, with added tags for internationalization and a - slightly different structure. Documentation and a DTD/Schema - for Monodoc XML is forthcoming. - - Monodoc XML does not contain any definitive type information, - and is only useful in conjunction with the Type definition for - whatever is being documented. - - This XML could be generated by hand, by monostub, or by monodoc. - - *** Assembly XML - This XML is generated by combining runtime type information for - an Assembly with a collection of Monodoc XML files. The resultant - XML (in the best of cases) contains both complete type and - documentary information for each type in the assembly. - - This XML contains enough information to be transformed into - user-accessible documentation. It is likely that scripts - will be created to generate reference docs as HTML and other - formats. - - Documentation and a DTD/Schema for Assembly XML is forthcoming. - + You can download the tools to document Mono from the CVS + repository from module `monodoc'. + ** Documentation Tools - *** docstub - Given a type name and an assembly, generates stub Monodoc XML - documentation for the type. Optionally, docstub can attempt to - populate initial documentation from an XML file in the format - published along with the ECMA standard. - - *** docverify - Given a Monodoc XML file and an assembly, verifies that the - documentation matches the compiled type. Checks signatures, - parameters, et cetera. - - *** docconv - Converts from Monodoc XML to the standard C# compiler-emitted - XML format and vice versa. - - *** docgen - Given an assembly and a collection of Monodoc XML files, creates - an Assembly XML file containing all documentation and type information - available. This output is suitable for transforming into user - documentation. - - *** monodoc - A GUI tool for documentation and translation, this encapsulates - the capabilities of docstub, docverify, docconv, and docgen in - a friendly user interface. In addition, monodoc provides features - to ease translation, such as side-by-side editing and coverage - statistics. - -** Status and Roadmap +*** MonoDoc -*** 2 January 2002 + A graphical documentation viewer written in Gtk#. In the + future we will have an ASP.NET front-end to present the + documentation on the web as well. - As I write the initial version of this document, very little has been - implemented. Currently, there is a: - - - - Here's hoping for frequent, productive updates. +** Status and Roadmap ** Get Involved - Help us define Mono's documentation structure! Subscribe to + Help us develop Mono's documentation tools! Subscribe to mono-docs-list - and wade right in. \ No newline at end of file + and wade right in.