ofRenderCollection seems redundant

in the group review we started to discuss ofRenderCollection and if it was really necessary as a file -- it's alot of reimplementation of code and it means that as we make changes to the render pipeline, there's now three places we need to change it (in the ofCore, in the render and in the collection).

also, the name "ofRenderCollection" feels very java :)

Could we move the logic of ofRenderCollection closer into OF, ie, ? At the moment, there's for sure something repetitive happening here, and if multiple renders is something we really care about and wish to support, we could switch all the calls that do:

renderer->

to

for (int i = 0; i < renders.size(); i++){ }

and just remove this file?

Start by comparing the repeated rendering logic in ofRenderCollection, ofCore, and the render implementation. Trace the renderer-> call sites and determine how multiple renders should be supported; the refactor is done when the redundant collection logic is removed or consolidated without leaving those call sites inconsistent.