projects
/
mono.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
update known-issues
[mono.git]
/
web
/
documentation
diff --git
a/web/documentation
b/web/documentation
index 4bf6aab6760bfa5b8480486d7b207e2c1caf90ce..40085e851267d8d531235348427d9044e53fa07f 100644
(file)
--- a/
web/documentation
+++ b/
web/documentation
@@
-25,7
+25,11
@@
libraries as well as the class libraries produced by
the project).
libraries as well as the class libraries produced by
the project).
- * Tutorials on Mono and the specifics of running it.
+ * Tutorials on Mono and the specifics of running it
+ (The <a href="http://www.monohispano.org">Mono
+ Hispano</a> team has produced lots of <a
+ href="http://www.monohispano.org/tutoriales.php">tutorials
+ in spanish</a>
* A guide to Mono as compared to the Microsoft.NET
Framework SDK
* A guide to Mono as compared to the Microsoft.NET
Framework SDK
@@
-55,7
+59,7
@@
repository (on gtk-sharp/doc) and we need volunteers to help
populate the documentation for it. Since Gtk# is a wrapper
for Gtk, plenty of documentation exists in the <a
repository (on gtk-sharp/doc) and we need volunteers to help
populate the documentation for it. Since Gtk# is a wrapper
for Gtk, plenty of documentation exists in the <a
- href="http://developer.gnome.org/doc/API
/2.0/
">Gnome developer
+ href="http://developer.gnome.org/doc/API">Gnome developer
site</a>.
To get started:
site</a>.
To get started:
@@
-110,18
+114,18
@@
As you document Gtk# you will have a number of tags that you can
use inside the summary and remarks sections, these are:
As you document Gtk# you will have a number of tags that you can
use inside the summary and remarks sections, these are:
-_Pre_
-
<para> </para>
+<pre>
+<para> </para>
</pre>
Used to separate paragraphs.
<pre>
</pre>
Used to separate paragraphs.
<pre>
-
<paramref name="param_name"/>
+<paramref name="param_name"/>
</pre>
Used to reference a formal parameter to a function.
<pre>
</pre>
Used to reference a formal parameter to a function.
<pre>
-
<see cref="T:SomeTypeName"/>
+<see cref="T:SomeTypeName"/>
</pre>
Use this to reference a type, this will include an hyper
link to the page for type SomeTypeName.
</pre>
Use this to reference a type, this will include an hyper
link to the page for type SomeTypeName.
@@
-129,11
+133,11
@@
_Pre_
For example, to reference "System.Enum", do:
<pre>
For example, to reference "System.Enum", do:
<pre>
-
<see cref="T:System.Enum"/>
+ <see cref="T:System.Enum"/>
</pre>
<pre>
</pre>
<pre>
-
<see cref="P:SomeTypeName.Property"/>
+<see cref="P:SomeTypeName.Property"/>
</pre>
Use this to reference a property, this will include an hyper
link to the page for the property `Property' of type `SomeTypeName'.
</pre>
Use this to reference a property, this will include an hyper
link to the page for the property `Property' of type `SomeTypeName'.
@@
-141,11
+145,11
@@
_Pre_
For example, to reference the BaseType property in System.Type, do:
<pre>
For example, to reference the BaseType property in System.Type, do:
<pre>
-
<see cref="P:System.Type.BaseType"/>
+ <see cref="P:System.Type.BaseType"/>
</pre>
<pre>
</pre>
<pre>
-
<see cref="M:SomeTypeName.Method(type,type)"/>
+<see cref="M:SomeTypeName.Method(type,type)"/>
</pre>
Use this to reference a method, this will include an hyper
link to the page for the method `Method' of type `SomeTypeName'.
</pre>
Use this to reference a method, this will include an hyper
link to the page for the method `Method' of type `SomeTypeName'.
@@
-153,27
+157,27
@@
_Pre_
For example, to reference the ToString method in System.Object, do:
<pre>
For example, to reference the ToString method in System.Object, do:
<pre>
-
<see cref="M:System.Object.ToString()"/>
+ <see cref="M:System.Object.ToString()"/>
</pre>
<pre>
</pre>
<pre>
-
<see langword="keywro
d"/>
+
<see langword="keywor
d"/>
</pre>
Use this to link to a keyword in the C# language, for
example to link to `true', do:
<pre>
</pre>
Use this to link to a keyword in the C# language, for
example to link to `true', do:
<pre>
-
<see langword="true"/>
+ <see langword="true"/>
</pre>
<pre>
</pre>
<pre>
-
<example> ... </example>
+<example> ... </example>
</pre>
Use example to insert an example. The example can
contain explanatory text and code.
<pre>
</pre>
Use example to insert an example. The example can
contain explanatory text and code.
<pre>
-
<code lang="C#">.. </code>
+<code lang="C#">.. </code>
</pre>
Use this to provide a sample C# program, typically used
</pre>
Use this to provide a sample C# program, typically used
@@
-187,38
+191,38
@@
_Pre_
You can link to an example like this:
<pre>
You can link to an example like this:
<pre>
-
<code lang="C#" source="file.cs"> </code>
+ <code lang="C#" source="file.cs"> </code>
</pre>
<pre>
</pre>
<pre>
-
<item>
+<item>
</pre>
<pre>
</pre>
<pre>
-
<list type="bullet"> </list>
+<list type="bullet"> </list>
</pre>
Use this to create lists. Lists contains <item>
</pre>
Use this to create lists. Lists contains <item>
- elements
+ elements
which have to contain <term> containers.
<pre>
<pre>
-
<list type="table"> </lits>
-
<listheader>
-
<term>YOUR FIRST COLUMN</term>
-
<description>YOUR DESCRIPTION</description>
-
</listheader>
+<list type="table"> </lits>
+ <listheader>
+ <term>YOUR FIRST COLUMN</term>
+ <description>YOUR DESCRIPTION</description>
+ </listheader>
</pre>
For two-column tables. Inside use:
<pre>
</pre>
For two-column tables. Inside use:
<pre>
-
<item>
-
<term>First</term>
-
<description>First descritpion</description>
-
</item>
-
<item>
-
<term>Second</term>
-
<description>Second descirption</description>
-
</item>
+<item>
+ <term>First</term>
+ <description>First descritpion</description>
+</item>
+<item>
+ <term>Second</term>
+ <description>Second descirption</description>
+</item>
</pre>
** Words of warning.
</pre>
** Words of warning.
@@
-246,6
+250,11
@@
_Pre_
please don't open the Microsoft docs and refer to them for each member
you document.
please don't open the Microsoft docs and refer to them for each member
you document.
+ The best way of documenting is to read our source code
+ implementation and explain in your own words what our implementation
+ does, and what the user can do with it.
+
There's a lot of domain expertise among the class library contributors;
let's put the same personal stamp on the class library documentation
There's a lot of domain expertise among the class library contributors;
let's put the same personal stamp on the class library documentation
- that we have on the class libraries themselves.
\ No newline at end of file
+ that we have on the class libraries themselves.
+