Every programmer out there develops a programming style of their own. This style usually evolves over time, and eventually reaches a point where without outside influence, it stops evolving.
Many ASI VARs have developed their own style when it comes to using Function Groups. These styles reflect what that particular VAR wants to get out of using FGP's. ASI Controls endeavors to provide a library of FGP's to the VAR base as practical learning examples. These FGP's can then be deployed in the field, pending modification to meet the actual sequences needed.
One need in all this is a common style to the examples, and a defined method to deploying them. Without it, it will impossible for the VAR base to successfully use these library examples consistently. Without further ado, here is our recommended programming style for FGPs, broken out into six rules.
In order to be able to reuse Function Groups between controllers, it will be necessary to be as modular as possible. This means the Function Group should perform only one function to the end result of the controller's sequences.
Multiple Function Groups should not contain the same Object instance. The proper way to deal with this is the use of Published Points, which allow points to be shared between FGP's.
Certain Function Groups should exist in every controller, no matter what the end configuration will look like. These FGP's should contain all of the Objects which will cause on overwrite condition when imported.
Visual Expert handles the list of Function Groups by alphabetizing them. To keep similiar FGP's together in the list, use a prefix.
Always use notation in your Function Groups. Put a large note in the upper left corner to describe the FGP. Use small notes liberally in your FGP to document the sequence.
Keep the Object symbols lined up, and in an orderly fashion. Do not have connection lines cutting across symbols. Do not make your FGP's larger than what will fit on the screen without scrolling. If you have that many Objects instances on your screen, you probably need to break that FGP up into smaller pieces.