Clean up player API

[jeroen]

Player 5 plugins will have a new API to interact with the player, which simplifies player interaction and removes the need for plugin developers to understand the player's internal structure.

Initialization

Initialization of the player happens before the first LOAD and before the first REDRAW occurs. It is different for plugins, ActionScript and javascript:

• Plugins have an initPlugin(player, config) call, which returns a reference to the Player API class and the plugin's config object.
• ActionScript can subscribe to the PlayerEvent.JWPLAYER_PLAYER_READY event.
• Javascript can set the 'playerready' flashvar with the name of a callback function which is executed when the player setup is complete.

Public Player properties (read-only)

• playlist:Playlist
• config:PlayerConfig
• skin:ISkin
• isBlocking:Boolean
• fullscreen:Boolean
• mute:Boolean
• controls:PlayerControls

Public Player methods

• addEventListener(event type,listener):Boolean
• removeEventListener(event type,listener):Boolean

• play()
• pause()
• stop()
• playlistNext()
• playlistPrev()
• playlistItem(index)
• seek(position)
• load(toLoad)

• blockPlayback(plugin)
• unblockPlayback(plugin)

[jeroen]

every event should also be its own class, so the event parameters are strong typed.