Ticket #904 (closed feature: fixed)
Unified plugin API
| Reported by: | jeroen | Owned by: | zach |
|---|---|---|---|
| Priority: | Milestone: | Player 5.5 | |
| Component: | general | Keywords: | |
| Cc: | pablo, jeroen, zach | Forum thread: |
Description
We must figure out a way to support basic plugin interaction. Given the nature of javascript (it's already totally possible), this might be more about best practices than about actually adding code. A couple of items to think about:
- positioning - how does the plugin know where the player is on the page?
- api - looks like we're not missing anything here, but we should pay attention.
- instantiation - what's the nicest way to instantiate plugins? Concatenating them to $().jwplayer()? Inserting a 'plugins()' array? Or is it up to the plugin?
- hosting - we probably want to host plugins, but what does that mean in terms of loading them? Still separate javascript includes, or is there another way?
- buttons - we'd probably want the addControlbarButton() and addDockButton from the 5.x player (see #903).
A couple of ideas for plugins that could get traction fast:
- Captions
- GAPro
- HD
- Playlist
- OVA
- Sharing
Perhaps an adnetwork as well - like Scanscout?
Change History
Note: See
TracTickets for help on using
tickets.
