I was wondering if using a standard MVC approach would benefit the design of a software project using Ignition?
The general idea would be to design all the windows needed but not configuring them nor the items used inside each window. Instead, a script (or many scripts, depending on the structure of the project) would be created, centralising the behaviour of all the components. This way, one person can create the windows and focuses on the “view” when another one focuses on the “controller” by creating scripts which will describe the behaviour of the items.
A benefit would be that we don’t need to find the item to change its behaviour (when we have a lot of windows), but just open the script file and change the code inside.
Would it be a good way to design software in Ignition? Is it even possible to do so? What about performances comparing to standard approach (see user manual)?
Thanks for your time !