[Openframeworkwg] provider independence

[Bernard Metzler]

>
> > Are we all agree on the following requirements
> > for the upcoming interface:
>
> I'm in agreement with these requirements.
>
> I'll make sure to capture them in the ofwg-issues (I should rename
> that) spreadsheet, so that these get tracked.
>
> > (1) must be provider agnostic (well, some providers may only
> >     implement a subset of functionality, but that is managed
> >     in a generic way),
>
> Can you expand on this in order to create a more refined list of
requirements?
>

The provider should be free to leave functionality not implemented
and that should be handled by the framework in a save way.


btw, I liked your suggestion how that could save size. you wrote

"The trade-off is that the ops pointers can reference static structures,
 which should always be a cache hit.  Verbs places the ops in dynamically
 allocated memory.  So, we reduce the memory footprint, and can leave ops
 NULL where entire sets of operations are not supported."


> > (2) multiple providers can be used from one application
> >     in parallel,
> > (3) changes to provider code does not enforce recompilation
> >     of the application.
>
> - Sean
>
Bernard.