Okay, the simple resolution is this:

stick to the current documentation and examples first. Understand those first. If you don't have much understanding now, you will have understanding after going through the current examples, and will very possibly (if not probably) be able to answer many of the questions you have now for yourself.

Stop looking at the "examples that seem interesting" that are not current. If they are not current, you should consider getting them to work an advanced topic, best saved for later. Accept that "I simply want to get this example working in Processing 1.x" IS cherry-picking, regardless of what you think it is.

Accept also that your use of language does imply certain things; it is not merely our impression, that is the intent of the language. One possibility is that you often/usually use such language without realising its intent, or even do realise and use it in an aggressive manner whilst claiming not to. That isn't an assumption about your intentions, that is a possible scenario which you may or may not have considered, but one which myself (and it seems others here) have considered. Deal with it.

If you want an argument about who said what, that is called trolling, and my suggestion to all here is to stop answering.

Your way forward is to stick to the tutorials and other current learnig material. If you are interested in these other examples enough, it should encourage you to learn as much as possible to work out what to do.

If you want to see support for things that the Processing team don't do, try offering helpful suggestions such as "this particular media host X allows substantial and reliable storage without lots of ads and annoyance" instead of insisting that someone "should" have already found it and (necessarily) have used it.

Your expectation, whether reasonable or not, is that the Processing team should do a bunch of things. There is no law or rule which says these things must be done. You're not paying for them, and you also don't understand them. Your language is demanding, and you've had several people try to explain the situation. If you are still unhappy, there isn't much we can do about it.

-spxl

Thinking about that, perhaps authors could use Sourceforge, Google Code or similar to host older distributions, since Processing is open source. Hosting is free and SF has various mirrors to support download charge. But it still some work to install that, might need to put code there too (depending on policies), and so on. Quite some work.
And as said, the issue is less with Processing itself than with the needed libraries.

The Processing applet page was originally designed with the absence of libraries. We didn't have libraries back when the site was orange and brown (not any I can remember anyway).

Whenever I upload any source code these days, I do it with a zipped folder of the project. I'd recommend that perhaps processing should start producing applets in the same fashion, and thus we get less of these situations, because the dependant libraries can be bundled in the zip file. And most importantly - they will be versions of the library that work with the code presented.

You can run any project with libraries by just putting the library in a folder called "code", locally to the sketch pde - so this suggestion would be perfectly workable.

I've uploaded a zip file and changed the Eye 4 An Eye project page so a zip can be aquired, and thus this issue hopefully won't visit me again.

http://www.robotacid.com/PBeta/eye4anEye/index.html

I would probably keep this sort of work up to date and work on my site some more if I wasn't so deep into this project:

http://forums.tigsource.com/index.php?topic=8467.0

When I'm done with it, I'll come back and tidy my open source repository up properly. Promise.

Divine inspiration: code that comes with Processing is current.

I'm sorry you are so obstinate. I'm not answering you any more.

If you would like to pay me for the time I spent updating the project for you to try, that will be about $300.