The Example Program Gatekeepers will be using the Example Programs Style Guidelines and Example Programs VI Analyzer Test Suite when reviewing example program submissions. The Style Guidelines can be thought of as the minimum requirements, but if you think that a particular requirement isn’t suited for your example just explain that in your submission comments.
The VI Analyzer test suite only covers a few of the Style Guidelines requirements so we added a few optional tests to help you find other issues that you might want to fix. The spell check is pretty useful! Please refer to the attached instructions and download the zip file when you're ready to get started.
Example Programs Style Guidelines
These guidelines were created to promote consistency, understanding, and good coding practices for LabVIEW Examples submitted to the NI Community. What follows is a small subset of the guidelines that are used internally for the shipping examples across the LabVIEW platform. The items in blue are tested in the Community Example VI Analyzer tests.
Example code should be clean, easy to read, and well commented. Examples should also be as minimal as possible, only requiring driver software and hardware if the example cannot be written without it. For example, if the main purpose of your example is to illustrate analyzing data after it has been acquired, consider using a constant or file-based sample instead of actually requiring the user to have certain hardware and drivers to supply data for your example.
Icon and Connector Pane