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

Application manager: Decouple from napari #154

Open
3 tasks
jaimergp opened this issue Jun 18, 2024 · 1 comment
Open
3 tasks

Application manager: Decouple from napari #154

jaimergp opened this issue Jun 18, 2024 · 1 comment

Comments

@jaimergp
Copy link
Collaborator

Similar to napari/napari-plugin-manager#59, the application manager should not depend too much on napari. Instead, napari-application-manager should be a product that depends on the agnostic one and provides the features needed for our ecosystem.

To do:

  • Investigate coupling and propose design/API for decoupling
  • Implement the aforementioned design. At first, this can happen in the same repository with two independent projects.
  • Decide maintenance and release model.
@dalthviz
Copy link
Member

Giving a quick check to #34 #46 #63 and code over the main branch, I think there is not much coupling between the work here and napari. Seems like the design defined at #34 already takes into account that the implementation should be agnostic? Maybe one sort of coupling is the UI style which kind of follows napari style and icons and that the mock up UI already implemented was build using PyQt5/PySide2? 🤔

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

No branches or pull requests

2 participants