Suggestion for the future

For oldOfx.h over time...

Perhaps we should do ofxOld_v1.3.h, ofxOld_v1.2.h
and ofxOld.h that is just:
# include ofxOld_v1.3.h
# include ofxOld_v1.2.h

ofxOld_v1.2.h would be just the YUV stuff
and documented as safer to ignore (comment out) when building against 1.4 but not to ignore 1.3 because of old hosts and plug-ins

Start by reading oldOfx.h and the compatibility requirements described in the issue. Consider how ofxOld_v1.3.h, ofxOld_v1.2.h, and the aggregate ofxOld.h would represent the YUV compatibility guidance for different hosts and plug-ins. Done should mean the header organization and version-specific inclusion behavior are clearly defined and documented.

Written by the indexing model from the issue text.