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

npe2 TODOs #5874

Open
12 tasks
kne42 opened this issue May 26, 2023 · 4 comments
Open
12 tasks

npe2 TODOs #5874

kne42 opened this issue May 26, 2023 · 4 comments
Labels

Comments

@kne42
Copy link
Member

kne42 commented May 26, 2023

Background

This is an effort to document what work needs to be done to round out existing work for npe2 menu and keybinding contributions.

Checklist

Dependencies

  • menus
    • custom action / wrapper that allows one to take the output of a function and do something with it
    • file menu
      • open sample menu needs to be able to take the output of the action to populate the viewer [see custom action]
    • plugins menu
      • widgets menus need to be able to take the output of the action to create the widget [see custom action]
      • NAP 6 needs live demo to gather consensus, requires [custom action] for demo
    • window menu
      • testing errors: pytest fixture problem where init_qactions are persisting across tests
    • for npe1 deprecation, the menu contributions don't need to be completed, just the internal app-model menu migrations
  • keybindings
    • NAP needs to be created and consensus gathered to determine how we will handle keybindings on the backend
    • a design for the new GUI for setting shortcuts may be needed

API Changes

Once these changes have been made, npe1 will need to be deprecated and eventually removed. The action manager will also be removed. Existing APIs for keybindings will be changed as documented in the to-be-created keybinding NAP.

@kne42 kne42 added the Epic label May 26, 2023
@lucyleeow
Copy link
Contributor

lucyleeow commented May 29, 2023

Just a question, is #4860 still relevant or would this succeed it?

@kne42
Copy link
Member Author

kne42 commented May 30, 2023

This is meant as a successor in the sense that it's more up-to-date on current blockers, dependencies, and tasks. I think #4860 still has some relevancy for documentation as this issue is for technical work.

@lucyleeow
Copy link
Contributor

Makes sense, thanks!

@aganders3
Copy link
Contributor

Thanks for collecting this in one place! There's one small typo - the Window Menu app-model PR is #4977 (OP links #4997).

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

No branches or pull requests

3 participants