Hi,
I learned LVOOP in a way that doesn't satisfy me anymore and I would like to improve my designs.
One of my personnal project is a MenuBurger class using picture and dynamic launching VI.
This one, I would like to share with the community one day but there some probleme rely on the design...
This is a very simple explanation using UML about how it's works :
(I want it to be compatible for earliers LabVIEW version so it's ok to not use the Interfaces that ship with LabVIEW 2020)
The idea is to have an MenuBurger API that manage interactions between the user and the menu (A picture control) and call a Button API (Image to be display in the picture).
To be extendable and modular for an end user, we can derive an existing button class to customize it (Adding some decoration, color gradient, etc...) by overriding the create method.
And I would like that be dynamic using factory pattern :
For my own use, I know the rules for using it so it's ok but I'm not satisfy of this design to share it with the community.
Using dependancy inversion and passing the object just move the probleme. I still have to manage different configuration.
Have a big configuration cluster to handle all case is not admissible, this is not easely maintainable and extendable and this more confusing for a developper...
Is it an abstraction problem ? But I like the idea to have a button base class that handle the common functionalities...
I don't know what to do to make this tool good enough to be shared.
I'll be glad to have any advice !
Loïc
