Unclear feature coverage and migration process of new Web UI plugin system

[Enet4]

I have taken a look at the new Web UI plugin system. It does seem great, but I have these three concerns:

1. Can we include some of the example plugins in the current demo, so that we can see them in practice?
2. Can you confirm that these types of plugins still exist functionality-wise in the new system, even if with a different name?
   • menu: creates a new entry in the sidebar, so as to provide an arbitrary page
   • result-option: adds an element in the Advanced Options section of each search result on screen
   • result-batch: adds an element at the bottom of the search results which enable batch processing of results
   • settings: extends the plugin settings page with an arbitrary div for custom settings
3. What do we have to do in order to migrate web UI plugins for Dicoogle 3 so that they can be used in dicoogle-next? At some point we will need to have a migration guide in the learning pack, but having the information somewhere would be fine for now.

[luis-godinho]

Hi. Thanks for the feedback.

1. I will add the examples to the demo, so these can be tested.
2. I believe that the only type of plugin that does not currently exist from that list is the result-batch option. I will try to implement it as soon as possible.
3. I will add to the documentation the migration steps to go from the current to the dicoogle-next plugin implementation.