Drawing on the experiences of a world-class LabVIEW development organization, The LabVIEW Style Book is the definitive guide to best practices in LabVIEW development. Leading LabVIEW development manager Peter A. Blume presents practical guidelines or “rules” for optimizing every facet of your ease of use, efficiency, readability, simplicity, performance, maintainability, and robustness. Blume explains each style rule thoroughly, presenting realistic examples and illustrations. He even presents “nonconforming” examples that show what not to do—and why not . While the illustrations in the print book are in black and white, you can download full-color versions from the publisher web site for free. Coverage includes This book will be indispensable to anyone who wants to develop or maintain quality LabVIEW developers, managers, and end users alike. Additionally, it will also be valuable to those preparing for NI’s Certified LabVIEW Developer or Certified LabVIEW Architect exams, which contain significant content on development style. Foreword by Darren Nattinger Preface Acknowledgments About the Author Chapter 1 The Significance of Style Chapter 2 Prepare for Good Style Chapter 3 Front Panel Style Chapter 4 Block Diagram Chapter 5 Icon and Connector Chapter 6 Data Structures Chapter 7 Error Handling Chapter 8 Design Patterns Chapter 9 Documentation Chapter 10 Code Reviews Appendix A Glossary Appendix B Style Rules Summary Index
Yeah, I guess it's OK if you're just looking to copy the visual look and feel of a Bloomy Controls product but, please, DO NOT take this book as gospel. While I totally agree that there should be great care given to the front panel and block diagram designs, especially, if you're working on a large project with multiple coders, some of the rules are just weird and may lead to more headaches than they spare. For example - sometimes for readability it may be necessary to add an extra bend to the wire. If these guys are focusing on how many bends their wires have, watch out! It may give you an OCD. It's also not a very good book to learn programming techniques from since it focuses only on the presentation and not on how to perform tasks like datalogging.