I have a piece of code that tries to load an image for a 'node' in my visualisation using the node label as the filename. If an image is present it will be used as an icon for that node, otherwise I just use the label as text. This allows me to change the appearance of specific nodes just by dropping in image files - no code needs to be touched.

It all works fine (loadImage() returns null if the image isn't present) but I get a bunch of error messages complaining about the missing file.

This is annoying as the 'missing' files aren't a problem. I knew I could fix this by simply checking for the image file first, but to do that you have to know how loadImage() works. As it turns out there is a public method, dataFile(), that encapsulates this knowledge, so I can simply write:

PImage img = null;
if (dataFile(imageName).exists()) {
 img = loadImage(imageName);
}

This is easy enough, but to find the solution I had to dig through the SVN repository and read the code. It would be a lot easier if this method was documented (and referenced in the methods that access data files).

If the Javadoc is intended as the primary resource for 'advanced' users then perhaps this should be more prominently linked from the 'Reference' and 'Learning' pages.

At the moment it looks as though the Language A-Z is the whole language, which is a little bit misleading, and a little bit offputting if you have a problem that you can't solve using this 'beginner' subset.

I think it's a good idea to define such a basic subset of the language so as not to overwhelm newcomers, but a clear link to the full documentation would also help to keep 'geeks' from being put off by what currently looks at first glance to be a 'toy' language.

I can see why having abridged, extended and complete documentation could be confusing. I would just have found it useful to have a prominent link to the complete reference documentation, perhaps with a short description of why there are different documentation 'levels' in the first place. Something like:

Quote: