I’m trying to get a feel for what’s possible architecture wise with perspective graphics. I’m working on my first Ignition project (Hurrah!) after working in the DCS world for a few years. The DCS HMI I worked with really enabled what I would call an Object Oriented Programming (OOP). I could build a class of elements, say a PCV icon with a bar graph, tag name, etc, out of other class based elements. The symbol for simultation active was a class based element that was used all over the place. If I updated that simulation icon in the class I updated all my graphics. Needless to say that’s super useful IMHO.
As I’m learning my way around Perspective I’m trying to figure out if something like that is possible, and I don’t see how I would do it. Short of learning to build my own components, which based on the Git Repo doesn’t look easy. Am I missing something, or will I just have to learn to do without my precious classes?
Most of us will make our own symbols and other objects with a view, then use the drop config system to make them drag and drop from the UDT that we build them against. Long story short, you can make reusable elements that take a UDT path and parameters to customise it, and then every time you use it as an embedded view, it's an instance of the template view. On top of this, the entire style system is built on CSS which is fully class based, and universally accessible throughout perspective.
Take care though not to nest views too deeply (Max 3 levels) as it will affect page load times and can also cause params to randomly not to load in the deeper levels (this is a bug)