Packaging your Reuse Libraries
We're happy that you love the idea of packaging
your library of reusable VIs into modular VI Packages and taking
advantage of the powerful yet easy-to-use features of VIPM.
You're probably wondering what's the best way to get started.
So, we've outlined our thoughts on the process, below.
By following these simple steps, you'll spend more time working on creating (re)useful VIs and finishing your LabVIEW projects instead of wasting time reinventing the wheel and searching for VIs.
See the Building your First Package exercise for a detailed tutorial.
These steps are just a rough outline of the possibilities for creating your own internal reuse library. Feel free to post any questions or ideas in the VIPM Discussion Forums.
Up: VI Package Guide
If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please consider posting them to the VIPM Discussion Forums. We're looking forward to your feedback.
By following these simple steps, you'll spend more time working on creating (re)useful VIs and finishing your LabVIEW projects instead of wasting time reinventing the wheel and searching for VIs.
Step 1: Organize Reusable VIs in your past and current projects.
a) Organize the reusable VIs into category folders that will become "VI Packages".
b) Give each category folder a name like "Array", "File", "String", etc.
b) Give each category folder a name like "Array", "File", "String", etc.
Step 2: Build VI Packages from each of your reusable VI folders using VIPM
It's easy to build a package.a) Select a reusable VI category folder (e.g., "Array", "File", "String", etc.) as your VI Package Source Folder.
b) Customize how your VIs will look in the palettes using the WYSIWYG (what you see is what you get) palette editor.
c) Add descriptive information about your package, such as author, company, package homepage URL, etc.
d) Build your package.
e) Repeat for each reusable VI category folder.
b) Customize how your VIs will look in the palettes using the WYSIWYG (what you see is what you get) palette editor.
c) Add descriptive information about your package, such as author, company, package homepage URL, etc.
d) Build your package.
e) Repeat for each reusable VI category folder.
See the Building your First Package exercise for a detailed tutorial.
Step 3: Install your VI Packages into the LabVIEW palettes and use them in projects
a) Use VIPM to install your VI Packages into the LabVIEW palettes.
b) Use your VIs in LabVIEW projects.
b) Use your VIs in LabVIEW projects.
Step 4 (optional): Create a VI Package Configuration for each LabVIEW project
If you're using VI Packages in your projects, you can ensure that you've always got the right packages installed when youa) Scan your LabVIEW project using VIPM to create a VI Package Configuration file and add it to your project folder.
b) Save your VI Package Configuration (*.vipc) file in your project folder (and check it into source code control).
c) Apply your VI Package Configuration when you start working on a project to ensure that all your reusable VI Packages that are needed by your project are found in the palettes.
b) Save your VI Package Configuration (*.vipc) file in your project folder (and check it into source code control).
c) Apply your VI Package Configuration when you start working on a project to ensure that all your reusable VI Packages that are needed by your project are found in the palettes.
These steps are just a rough outline of the possibilities for creating your own internal reuse library. Feel free to post any questions or ideas in the VIPM Discussion Forums.
Up: VI Package Guide
If you have any feedback or questions (including ideas for other topics you'd like to learn more about), please consider posting them to the VIPM Discussion Forums. We're looking forward to your feedback.