-
Notifications
You must be signed in to change notification settings - Fork 34
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
Plugin Center #771
Comments
This is an excellent idea. I think we don't need to add much to improve a lot the user experience. The following would already be great:
We can already download files from an url, but we can't unzip on all platforms. A minimal library like Additional information on why loading a plugin has failed would also be great, but I don't know if there is a mechanism to retrieve this. |
On linux and macOS, the path will be changed. Currently, we are using |
For Linux, a subdirectory of |
If a plugin is implemented in C++/Rust/... which could be compiled to wasm, we should deliver the binary in wasm but not one for Unix, another for Windows. |
|
Users should open a gui from mogan, which lists all plugins available for mogan, all plugins installed at local storage, and status of these plugins. Then users select plugin to install, update, remove or modify its setting.
When a plugin is detected, mogan should let user decide whether to activate the plugin. After activating plugin, mogan should tell user information and errors encountered in plugin execution.
Design of this tool should be discussed:
We should build a service to host plugin archives.
Install to their user directory responding to each os. Different os has different standard:
%APPDATA%
$HOME/.local/share
if not defined)(Need Discussion) If a plugin is written in native language (c, rust, zig, .etc), binaries under different platform differs, thus proper package should be selected according to platform.
We could fetch and install update via Qt Installer FrameworkMogan is installed by apt on linux, or installed from portable version, thus QtIFW may be missing.(Need Discussion) Depends on module system
(Need Discussion)
(Need Discussion)
(Need Discussion)
No. It is hard to learn dynamic linking for plugin developers. Developing dynamic loading api is also cumbersome. Evermore there is several security issues when loading dlls. (Need Discussion)
The text was updated successfully, but these errors were encountered: