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

Activation at startup discussion #139

Open
Carreau opened this issue Mar 23, 2022 · 1 comment
Open

Activation at startup discussion #139

Carreau opened this issue Mar 23, 2022 · 1 comment

Comments

@Carreau
Copy link
Collaborator

Carreau commented Mar 23, 2022

From today's discussion,

we likely want a activate at startup event, except if a plugin requests that instead of enabling it by default, we should on next start ask "this plugin want to activate on startup, this can have consequences on the speed of napari stability and startup, to allow them to do so, go to preferences > plugins > allow blahblah blah".

We could also have a blessed list hardcoded but let's see later for how to do that.
Either PR against napari, or crypto key ?

@nclack
Copy link
Collaborator

nclack commented Mar 25, 2022

Here's the notes from the discussion

I really like the opt-in on startup.

I would love to gracefully handle a situation where:

  1. A user enables 50 plugins at startup
  2. One or more of them crashes/hangs during activate

A bulk reset, some ability to remember which one(s) caused issues, etc. would be nice.

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