Markus Humm wrote: > What is so hard in documenting just a single property or work on those > property overview pages which aren't complete yet? Copying the table of > a already started property list to a not yet started one and modifying > it so that the correct properties are listed is not hard.
My very personal reason is that I don't like APIs documented in a Wiki as they are incomplete most of the time (e.g. lack of type information for properties and events) and the required effort to keep this in sync with the code is very high. As I am already browsing the code in 95% of the lookup cases I tend to document my personal code in-line instead of separated from the code and use a tool to output fancy HTML directly from the sources (http://www.naturaldocs.org). Writing tutorials and how-tos is a different thing. In my opinion a Wiki makes sense here. Regards, Tobias -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
