Providing useful information to APL programmers can be done in a number of ways. In a Wiki, there is no way to enforce people to follow particular conventions. You might think about this as an invitation to create chaos. A very different view would be that this way good things will defat the less good ones sooner or later.

How to Provide Code

At the time being (2006-12-24) examples are provided as code block with lots of comments. This means that one can create the code in an APL workspace which can be saved for later use, like maintaining or enhancing.

On the other side you might find all the comment lines annoying the code is coming with.

Author

If you have created a particular page, please put a "Author: FirstnameLastname" at the end of the article if you are willing to keep an eye on the page. Write it like KaiJaeger, because this let the Wiki link automatically to your "homepage". This is another good reason to create such a homepage.

Linking

Overview

Wikis do *not* contain highly sophisticated structured pages which are all anchored into a menu. This makes not much sense because thi is very hard to maintain, at least in a large Wiki. Two different methods are available in MoinMoin-driven Wikis:

Sub Pages

Use the "!Mainpage/Subpage" mechanism when appropriate. That makes navigation for the user much easier.

For example, if you want to add a "MySpecialPage" to the DotNotSamples page, specify "DotNotSamples page/MySpecialPage" as page name. Consult the help pages for more information.

Categories

Adding a string "CategorySomething" offer a link to a so-called category page. When such a page is created, a MoinMoin macro can be inserted to produce dynamically a list of pages which also contains such a link. That is very usefule because new pages are automatically added to the list as soon as the become available.

Conclusio

For top-level links, use sub pages. For all other pages, make sure that they belong to at least one category.

.NET pathes

Address .NET methods/classes/enumerations/interfaces always fully. This makes it not only easier to understand the code, it makes also much easier to find related articles. For example, if you use the āˇ•USING mechanism, you can call the method "ShowHelp" from System.Windows.Forms.Help by adressing it as "ShowHelp". Surely there are plenty of other methods with exactly the same name! So it is more appropriate to search for System.Windows.Forms.Help.ShowHelp if your are looking for an example how to use this .NET method.