|
|
|
|
|
In my opinion often one of the most valuable assets in a toolkit. No matter how good you are as programmer, or how thorough your read the documentation, nothing beats a good sample! An experienced programmer knows the following:
Personal belief: The Art of Copying ?
Programming is the art of copying - The difference between a experienced- and a rookie programmer is that the experienced programmer knows where to look and what to copy!
In essence; The art of programming is evolution - not revolution.
Ok, some programmers even invent stuff - but those guys are pretty few ...
The samples may vary in quality from very very short samples, hardly showing you anything, to the full fledged applications showing you everything! In fact, both too little and too much aren't good, since you can't focus on what the toolkit feature really does.
It is generally very hard to make samples efficient enough (contain the topics it meant to show, whilst being complete enough to see the context).
I have all kinds of experience with the toolkits. The first Notes C toolkits where shipped with very few and small samples. I had the impression that the samples where almost taken out of the Notes client source code, since it very often was completely out of context, and barely showing the current topic at all. Very often the construction and filling of complex structures where omitted in silence, and heavy experimenting was the only salvation.
These days I would say that Notes C and C++ toolkits has come a very long way. Both the numbers of samples has increased, as well as the quality.
Look for samples in the samples-directory
E:\Toolkits\LibraryX\samples
Note that this sub directory often contains several sub directories all focusing on certain areas of the toolkit.