List and discuss the name for the plugin design

[unkcpz]

Thanks to the great work contributed by @superstar54, the plugin design allows new property developers can focus on the functionality and widgets needed for the property itself without knowledge of how other part of QeApp works.
It decouples the settings of parameters of different calculations by introducing the "Panel" as the base widget class which has some common functionality to interact with other parts of the code.
There are some terminology and methods used but not intuitively straightforward to know what is for, such as "identifier", "get_panel_value" etc.
@superstar54, can you make a list of these names and we can have a discussion with @giovannipizzi? Once we make the stable release at the end of this month, it become a new API for developers and will be hard to change after.

[unkcpz]

During @superstar54's group meeting, we agreed that we release this v23.10.0 with current names for APIs, and when there are more developers trying plugin design, we discuss and fix the API in the next version.

[unkcpz]

Pining @AndresOrtegaGuerrero @PNOGillespie @mikibonacci who start implement the plugins, do you find some class names are not clear or bring ambiguity? If those are all fine, we can close this PR.

[mikibonacci]

Hi @unkcpz, I do not have in mind examples, so for me everything is fine

[PNOGillespie]

Hi @unkcpz, the one thing that occurs to me is that set_panel_value() in Setting wasn't entirely clear at first, which did cause a brief problem for the XAS PR because I wasn't aware that the method was intended for loading panel settings from a previous calculation.

On the one hand, the documentation for the plugin system states:

set_panel_value to tell the app how to reload the panel values from the previous calculation.

On the other hand, the docstring for set_panel_value() itself states:

"""Set a dictionary with the input parameters for the plugin."""

My suggestion is just to make sure the docstrings and documentation agree with each other, so that it's clear in both places what each part is meant to do. Changing the name of set_panel_value() might also make it clearer, but I don't know what would work here because the intended behaviour seems too specific to create a clear name for.

Other than that however, the rest of the system was clear enough for me to work with.

[unkcpz]

Thanks @mikibonacci @PNOGillespie for the feedback.

@superstar54 Can you keep track on this issue and make sure the advice from @PNOGillespie above is happened on the v24.04.0?