-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Better plugin installation interface (plugin directory) #74
Comments
I can hit the API for https://datasette.io/content/plugins ( https://datasette.io/content/plugins.json ) to get the data. Would it be useful to filter that down to just the plugins that are known to work well with Datasette Desktop though? I'm inclined not to do that. If a plugin doesn't work well with Datasette Desktop that's a bug in the plugin that should be fixed. Even the ones you wouldn't expect to be useful ( |
Could you use something like italics to show extensions that don't work in the app? |
New menu item: + {
+ label: "Install Plugins…",
+ click() {
+ let newWindow = new BrowserWindow(windowOpts());
+ newWindow.loadFile("plugins.html");
+ configureWindow(newWindow);
+ },
+ }, |
Here's a fun idea: what if the list of plugins you could install was a very lightly customized Datasette table? Would get search and faceting for free, and help people further understand what the tool can be used for. Could be pre-populated in the Or just an in-memory |
Uninstall work will happen in #72. |
Each plugin should also show which version you have installed, what the latest version is and provide the option to upgrade. The install status facet can have an extra value for upgradable. |
An "upgrade all" button would be good too. |
For the next release I'm going to implement "upgrade" but I won't fix "uninstall" - because uninstall requires a complex additional layer of persistence to avoid re-installing default plugins, see #101. |
I'm dropping the "compatible with Datasette Desktop" feature for the moment. |
I'm going to ship what I've got as a new |
I punted on this in #5 - see also this suggestion from @psychemedia in #67 (comment)
The text was updated successfully, but these errors were encountered: