#1: extendible GemState
- Contents
use key/value attributes for putting variables into GemState
- Proposed by
- IOhannes m zmölnig
- Proposal type
- Architecture
- Assigned to release
- State
- completed
Motivation
the current GemState-class cannot be extended without breaking ABI compatibility.
Proposal
GemState should use a key/value mechanism, where one could set "attributes" based on a symbolic-name.
examples
OLD: state->image
NEW: state.getData(gensym("pixBlock"))
this will break API and ABI compatibility, but only once and for all
Risks
performance penalty (shouldn't very high: openGL uses a glGet(NAME) as well)