An object, function, etc, can only be in exactly one namespace. e.g. "File" or "Net", but not both. What if a class can be used to accomplish multiple goals? The example code will end up in some obscure corner of your deeply-linked language reference pages.
No... a single .html file that contains all examples in all categories (or namespaces in your case) is much more useful than any alphabetical reference.
Note that the single examples.html page does not try to provide a reference. It provides example code, and that's it. No noise.
Ah, looks like we were talking past eachother. You were saying that you preferred "cookbook" style books, and gave examples of how to organize one of them. I was saying I liked "language reference" style books, and gave examples of how that should be organized.
What you want are examples sorted by usage.
An object, function, etc, can only be in exactly one namespace. e.g. "File" or "Net", but not both. What if a class can be used to accomplish multiple goals? The example code will end up in some obscure corner of your deeply-linked language reference pages.
No... a single .html file that contains all examples in all categories (or namespaces in your case) is much more useful than any alphabetical reference.
Note that the single examples.html page does not try to provide a reference. It provides example code, and that's it. No noise.