firmware: remember installed plugins, hint at user to install them #1663
Comments
|
Very cool. Even cooler if more people had the time to work on this... :) |
|
As a stopgap, can we just list the installed plugins in the config so they are easy to see & reinstall? |
|
Not without creating a mapping of config sections and plugins that needs to be in core and synced almost every release. Big process. :) |
|
It's probably simpler to register installed plugins in the config.xml by name. If there are testers, I can try to fix it for 18.7 ? |
|
No, more simple than that. just a list of non-core plugins that are installed in an xml field. the web UI seems to know already... |
|
It asks the package database, yes. But it would be better to fix the real problem first instead of trying to create a "sync" mechanism that writes all currently known plugins to the config. If we have a install/deinstall trigger that is much easier to implement and avoids "over-syncing" and a separate code spot for it. |
While this works, even for retrospective reinstall, the real issue is to get to know all the other plugins that are installed but not yet known like an image-preinstalled os-dyndns. Second step is how to present the plugins that may be missing in a sensible way or clickable "install all missing plugins".
|
Code is in there, but GUI parts need more work. |
Something like plist can be done? Just a standard flat file with current/previously successful installed plugin name. Then just call the |
|
The store is already there, the question is how to use it in the GUI, present reinstall buttons, clear, discard orphaned packages but only when the mirror is up to date because otherwise all plugins look "orphaned". I'm happy for all help but I am going to be picky here to ensure the feature is as good as it can be when we have it. I don't like to go back and rewrite this again. Sorry in advance. :) |
|
you got a rough design for that? can show me where it should be done? i would like to help with this under your guidance. |
When we install "os-debug" it will deinstall "os-debug-devel" so we should update our logic.
When we install "os-debug" it will deinstall "os-debug-devel" so we should update our logic. (cherry picked from commit b1702d0)
|
@fichtner how about this? |
… a button when there are missing plugins. for #1663
|
this is certainly the right direction, but we also need a dismiss button that syncs the current plugin names into the config and we can only install the ones that are really there (do we silently dismiss them or dismiss explicitly?) also when you change the mirror url and open packages again the missing ones should also be listed if people do offline installs :) |
|
There you go, accept captures currently installed plugins, which looks like the most obvious choice here. In time we might need to think about a larger overhaul, the volt template file is growing a bit too much for my taste, but certainly not this year :) |
|
some more changes done to streamline it a bit and also display missing plugins that are no longer available (while not making them marked as orphaned)
The last bit is moving the action buttons to the dedicated blue upper section and make the page show the actual progress of the reinstall. :) |
|
@fichtner looks good, thanks! |
(when a config.xml was exported / imported)
The text was updated successfully, but these errors were encountered: