Although most developers will probably just end up using BeanProperty (and the convenience methods that use it under the hood) for the purposes of animating beans, we purposely provided the Property interface as an abstraction, and BeanProperty is just a minimal implementation thereof. In other words, if you have your own preferred way of modifying properties, you can roll your own Property impl and still make use of the rest of the animation package. No need to throw the baby out with the bathwater.
BTW, I imagine there’s some overlap between Scenario and PulpCore (at least in the sense that both provide an optimized scene graph and an animation package). Think there’s any chance of porting parts of PulpCore to use Scenario?
The current scene graph implementation isn’t tuned for games, but it might be an interesting exercise to see where it’s lacking in that regard, and maybe to tune for that case.
Thanks,
Chris