I'm trying to integrate the fc1 drop into our Flex application.
1) It would be great to be able to bind on the MediaPlayer properties.
I've made a subclass, FlexMediaPlayer, that declares ChangeEvents for a bunch of properties:
override public function get muted():Boolean
I've just (re)discovered FC1's MediaPlayerSprite and see that it does what I list in #2 and #3!
So I've marked this question as answered.
But if someone knows why #1 is a bad idea -- or has a better way -- many thanks...
#1 is a great idea, I even push for it during the original MediaPLayer design phase. Given that [ChangeEvent] is a flex specific tag, that generates flex specific bindings, we left these out to help keep framework pure AS3. ChangeEvent/Binding tags had dependencies on some mx.binding classes that we didn't want to have to force every player developer to include in their project. A wrapper is a great idea, and it would help ease flex developers into using OSMF from the MXML standpoint.