Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add RFC: Separate context bar code into UI and plugins #61

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

norihiro
Copy link
Contributor

@norihiro norihiro commented May 1, 2024

Description

This RFC proposes to separate the implementation of the context bar into UI/ and plugins/.

Motivation and Context

UI has the implementation of the context-bar for each source type.
As the result, property names are hard-coded in both UI and plugins.
In possible future modification, it might require to change both plugin and UI, which might lead a potential bug.

It is a good implementation to separate the plugin-specific implementation from the UI.

This will also enable 3rd party plugins to have their context bar.

Rendered RFC

@gxalpha
Copy link
Member

gxalpha commented Jun 11, 2024

I like this approach! I thought of a similar concept (to the first variation of the two) a while back so was happy to see this RFC.
It might make sense to specify a number of items perhaps? So that only up to maybe 3 properties would get returned.

Additionally, this doesn't handle what happens to things that are currently custom crafted, like media controls. Sources like the media source currently indicate that they can be media controlled, should those just not implement this new API? What should happen if they both implement this but also can be controlled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants