10-25-2012 10:55 AM
Are there any official naming convention for LabVIEW files, such as VI, proj, lvlib, etc? Thanks!
10-25-2012 11:17 AM
Hi,
well in the LabVIEW style guide, there are some guidelines (http://www.ni.com/pdf/manuals/321393d.pdf#labview_style_guide p6-2 for example "When naming VIs, VI libraries, and directories, avoid using characters that are not accepted by all file systems, such as slash (/), backslash (\), colon (:), and tilde (~). Most operating systems accept long descriptive names for files, up to 31 characters on Mac OS 9.x or earlier and 255 characters on other platforms.")... but I do not think there is any convention...
Aurelie
10-25-2012 11:30 AM - edited 10-25-2012 11:36 AM
@jyang72211 wrote:
Are there any official naming convention for LabVIEW files, such as VI, proj, lvlib, etc? Thanks!
Not official. But you would be well served by keeping to a Fully Qualified Naming convention similar to "Verb <Adverb> Noun.xxx in yyy.lvlib on zzz.lvproj"
eg " Write XML File.vi in Calibration.lvlib on MyTestSystem.lvproj"
Avoid overdecorating with outdated conventions! For example the same file might have once been "MTS_Cal_XMLFileWrite.vi"( in Calibration.lvlib on MyTestSystem.lvproj) Before FQNs were fully supported and text programmers brought bad habits into LabVIEW Development.
10-25-2012 11:50 AM
10-25-2012 12:08 PM - edited 10-25-2012 12:11 PM
Mike,
I'd argue against that convention and tell you to use libraries and projects.
"Connect.vi in Battery Charger.lvlib" is a lot more discriptive
10-25-2012 01:35 PM
I am a fan of the libraries as well.
Ben
10-25-2012 02:41 PM
I think library is great, but sometime, I am too lazy to add a new vi into the library, and my library become a mess.
10-25-2012 02:43 PM
I have seen people using ! to move their file up in the directory. The problem is everybody started doing the same thing.
10-25-2012 02:45 PM
What did you mean by "Avoid overdecorating with outdated conventions! For example the same file might have once been "MTS_Cal_XMLFileWrite.vi"( in Calibration.lvlib on MyTestSystem.lvproj) Before FQNs were fully supported and text programmers brought bad habits into LabVIEW Development."?
What bad habits are you referring to? Is using "_" a bad habit? If so, why?
10-25-2012 02:57 PM
This question is about a library that consists of reusable VIs with the structure below. Library is the main folder that consists of subfolders that store subVIs with different types of functionalities. Should I create one *.lvproj at the main folder level and one *.lvlib at each subfolder level (1 lvproj and 3 lvlib total)? Or should I create a *.lvproj and a *.lvlib inside such subfolder (3 lvproj and 3 lvlib total)? Or is there a better way?
Library main folder
- vis with function type 1 subfolder
- vis with function type 2 subfolder
- vis with function type 3 subfolder