Ticket #597 (closed enhancement: wontfix)
Allow plugin ordering (z-index)
| Reported by: | zach | Owned by: | pablo |
|---|---|---|---|
| Priority: | Normal | Milestone: | Backlog |
| Component: | general | Keywords: | |
| Cc: | pablo, jeroen | Forum thread: |
Description (last modified by jeroen) (diff)
We can either allow plugins to set their z-index, or have a transparent and predictable way to z-index plugins (e.g. by honoring the orde of plugins).
We should keep any eye on this in the context of 6.0 and its support for overlays. Z-indexing may not be needed anymore.
Change History
comment:5 Changed 13 months ago by jeroen
- Owner set to pablo
- Priority set to Normal
- Type changed from feature to enhancement
- Description modified (diff)
comment:6 Changed 10 months ago by jeroen
- Milestone changed from Backlog to Player 6.0
Looks like this is something we may have to do in JW6.
We need to investigate a basic form (above/below controls) at minimum.
comment:8 Changed 9 months ago by jeroen
Pablo/Zach, is this still critical for 6.0? Looks like we don't need it if I move down the list of plugins...
comment:9 Changed 9 months ago by zach
This has been open for three years. I would say we should either do implement it or mark as won't fix.
Note that it may not be that important for a public API, but may be more important for a private API given the new model for plugins. Since plugins will be baked in, we could:
- Give the player a list of all known plugins and their z-index priority OR
- Allow plugins the ability to specify it's priority as a getter
Either one of these would allow the player to deterministically z-index each plugin in a way we know looks "good".
comment:10 Changed 8 months ago by pablo
- Status changed from new to closed
- Resolution set to wontfix
- Milestone changed from Player 6.0 to Backlog
As currently scoped, this ticket doesn't solve any outstanding use cases on the v6 roadmap. I'm closing this ticket for now. We should open a new ticket for any major use cases that we've missed as they come up.
From Rodrigo Polo: Add a parameter or property to the plugin class so when you add something to the "view" you can choose in which layer you want it to put it on (add the child element), it can be the actual layer or a new set of empty layers between the main player layers.