-
-
Notifications
You must be signed in to change notification settings - Fork 810
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
[Feature] UI Plugin API Improvements #4510
Comments
We need functionality to move and create elements to all parts of all pages so that those who work on making themes and scripts can fulfill their creative ideas. |
|
Another request: Scene page as a patched component, with access to some of the current components on that page. I think the essentials I would need are the video player and... maybe the queue? I think if I had those I'd have a good amount to work with. Extra tooling like the tab/pane functionality could be useful, but lower priority. |
Text blocks as a type to allow for users to create more complex configurations for things like pathParser without needing to edit the plugin code manually which should hopefully be on the way out with a built-in installer. |
Can I get a confirmation: when I register a route, that route can only be viewed when navigating from an existing one. I cannot view the page by visiting |
Thanks for adding the Thanks |
Sorry to keep asking for stuff! It would also be useful to have a Currently, default values are Thanks |
Would it be possible to add the hooks to more components like the Scene detail tabs. I would like to add a few features to the |
Integration of library features into core PluginAPI csUiLib
7dJx
|
Please could I request the components for the performers page Appears With tab and pane be made available to the plugin API? I'd like to work on a plugin that would filter out certain performers from the Appears With pane and update the number badge on the tab. See #5444 for info. |
might be better in a standalone issue |
How so? I only need the components exposed, the rest I can do myself. If I need to raise it separately though, I'm happy to. |
Could I also request the React-Select library be exposed to the |
As far as I can see, the Scene page is not in the Plugin API right now right? I would love to move QuickEdits to a more native plugin, but for that I will need the ability to inject a custom tab on the left side of the scene page. To avoid conflicts between tabs, I would also need for this tab to use the same data as the Edit tab, so changes in one tab don't overwrite changes made in the other. So either I re-create the Edit tab with the plugin, or somehow I can access the scene data it uses ? |
Per WP's suggestion, this is an issue for plugin developers to request improvements to the UI plugin API. This single issue would be used to keep requests in one place.
My current requests (completed):
Edit: Updated for cleanliness and to mark as completed.
The text was updated successfully, but these errors were encountered: