 |
|
|
| Customer Review: |
|
1: P. Blume and LabVIEW Rock!!!!!!!!
P. Blume nailed it!!!!! I am a heavy user of LabView (aka "the View") and this guy absolutely nailed it. This may as well be entitled "the Joy of LabVIEW". I have learned more new positions and ways to get the best out of my partner (LabVIEW) than ever before. Let's just say after reading this masterpiece a cig and a drink were in order.
Kudos to P. Blume and the team at Bloomy Controls.
|
2: Informative Book
I read the first couple chapters and was impressed with the quality of information. I then gave it to a programmer I am supervising for a project. I had him read it and told him to adhere to the standards of the book. After a couple weeks the code he is turning out is much improved. The flow is better, the code is documented and there is actual error control being used. It will be much easier to maintain the project as time goes on. The point of the book is to write better labview diagrams so I think it works quite well in that regards.
|
3: Don't Waste your Money
As the Title suggests "The Labview Style Book" only focuses on Style and provides no useful information outside the scope of the title.
|
4: Worth buying or reading
For just a decade I've been dealing LabVIEW based system.
During the career, for almost all years I was stick to
narrowly inmatured programming style. So then unfortunately
sometimes I harmed my own career.
If I'd met this book earlier I were taking on the management
of a certain LabVIEW project. It's certainly a very regrettable
truth, but just becoming certified recently I'll go along
another career.
This is very helpful book, including GUI style and BD style.
It is important you should first have review in the data
structure and location of each objects in the diagram.
Various examples will guide you to the real world of LabVIEW.
Like to say thanks to the author.
|
5: Good - needs editing
I get the feeling the other reviews are written by the author and his friends. Some are just a little too glowing.
This book is good but, needs editing because it is very long winded; using twice as many words than necessary to get the point across (the author is always stressing efficiency). Many of the "rules" are subjective and should be called suggestions. For example, the author has a rule disabling "Show dots at wire junctions". I like the dots. The VI's are not included with the book. Some are available from the authors company site but, only after registration.
I recommend the book but, be prepared to spend the time required for reading.
|
|
|
