Every good integrator I know does this internally, but I don't know of any publicly available libraries
We've got a large library of AOI/UDTs; some of them directly mirror PlantPAX functions (CmdSrc, Intlk, Perm, etc.) while most are our own creations, but most are paired with Ignition resources.
Hi @Brian_Stilson,
i've a start of a library with plc code and ignition faceplates.
It's near off be polish like it should but at least some folks use it in project or to start the development of their own library.
It would be nice. As much as we like to pile on FactoryTalk View and Panelviews, I will say that there is very little you can do to screw them up. More traditional HMIs like PVPlus, C-More, Weintek, etc. pretty much operate in a walled garden of sorts whereas anything the software lets you do, it's okay to do it, and you almost never run into performance issues. If you want to accomplish something, there is one well-documented, prescribed way to do it.
The other side of that coin is that the manufacturer had to think of that feature and purposely give you the ability to do it. Ignition (and really, SCADA in general because these issues exist in Aveva, iFix, etc.) is more wide open, and being so script-reliant to expand functionality means there is no possible way IA engineers can imagine every single scenario their software can be used. They're also using a lot of industry standard functionality like python/jython, css, etc. that they don't have 100% control over.
So I can understand why every single possible programming scenario isn't covered in the manual. It can't be. It's the same reason Rockwell doesn't tell you how to program absolutely everything. For every "here's how to do x," there's 1,000 other scenarios that will crop up they didn't cover. Learning how to program is easy. Learning how to program well takes time, and making lots of mistakes.