Ticket #1664 (closed feature: fixed)
Controls API class
| Reported by: | jeroen | Owned by: | jeroen |
|---|---|---|---|
| Priority: | Normal | Milestone: | Player 6.0 |
| Component: | general | Keywords: | |
| Cc: | pablo, doug | Forum thread: |
Description (last modified by jeroen) (diff)
An API class to show/hide the controls (dock/display/controlbar) will be great for plugins/scripts to influence the player appearance. We need the full set:
- getControls(): true/false
- setControls(true/false)
- onControls(): controls == true/false
In addition to the controls state, we must have an event to broadcast in which regions the controls are active (this differs from skin to skin):
- getSafeMargins(): { top:123, bottom:123 }
These margins are NOT updated when controls fade in and out. It's therefore not possible (per our UX decisions) to change the location of plugins in response to controls fading in or out.
Change History
comment:1 Changed 9 months ago by jeroen
- Cc pablo, doug added
- Owner changed from pablo to jeroen
- Milestone changed from Backlog to Player 6.0
comment:3 Changed 8 months ago by jeroen
- Description modified (diff)
One item to decide is what to do with the click when controls are disabled: do we toggle play/pause in response to a displayClick or not? Best is likely to do so. YT chromeless API does the same and JW5 does that too when icons/dock/controlbar are false.
We may have to look into this for JW 6.0, since the controlbar/dock/display show/hide API is widely used by plugin developers. Ideally, we want to replace these component API's with a single, internal API. Let's await feedback on the beta first...