Welcome to the VIPM Idea Exchange. Here's your chance to collaborate with JKI engineers and other users to influence the future of VI Package Manager. How can VIPM make your life easier or help you work smarter? Tell us!

To submit an idea:

  1. Type your idea in the box below. The Idea Exchange will show you similar ideas as you're typing.
  2. If someone else has already submitted a similar idea, vote that idea up and add a comment to the discussion.
  3. If they haven't, submit your idea as a new suggestion by clicking Next. Then provide a detailed description in the submission form. Add links, images, and video to make your suggestion clear and compelling!

To vote for an existing idea:

  1. Click the Vote balloon next to any idea to show your support. Better yet, also add a comment to the discussion.
  2. You will be prompted to create a new account if you don't have one, or login, if you do.

If you need technical support for VIPM or any of JKI's other products, click here.

Brandyn Adderley 5 years ago • updated by David_L 5 years ago 1

I would like the ability to categorize VI packages that are built.  If my company has 3 basic categories for a toolkit (1. use at own risk 2. Semi-tested 3. Certified). Then this category can be displayed when a user installs a package.  

Furthermore, once this information is gathered, you can then possibly search and install only Rock solid packages, for example

olivier-jourdan 6 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 5 years ago 2
As far as I've seen "custom action" VI cannot have SubVIs. It might be useful to allow that.
One of my use case is to create a package to "install" QuickDrop shortcut in LabVIEW.ini file. Source code could be too large for manage user interface dedicated. Workaround I've used is not satisfying.
I should understand that my use case is perhaps  a wrong usage of VIPM. 

Jonathon Green 6 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 5 years ago 3

I think it would be really cool if a dynamic palettes (I will call it that after the OpenG package name, but there maybe a better descriptor for it?) were a first class feature of VIPM. There would be nothing better than being able to open up a native LabVIEW palette and being able to select from your code - all conveniently in the one place just like the OpenG ogrsc_dynamicpalette package does for OpenG etc...

Aristos Queue 5 years ago 0
VIPM 2012 can create links that when users click on them in the browser will open VIPM and install the file... but only on Windows. For Mac and Linux users, there is no way to use a link, since there's no way to download the file and then open the package. The main VIPM menus need an equivalent to File >> Open File but for opening URLs. (Or fix the system so that links will open VIPM on these other platforms, but I get the impression that's hard to fix.)
Christopher Relf 5 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 5 years ago 3
i'd like to see a wizard added to the repo interface - i figure most people need help when they're setting up their first repository.  or, better yet, make the repo interface more like the package builder interface.
olivier-jourdan 5 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 5 years ago 3
It would be great to be able to install a package for each compatible version installed on a computer.
Bela Komoroczy 5 years ago 0
In the VI package buider in the 'Palettes' section you have the possibility to edit the icons.
It would be very useful if besides 'edit icon' and 'autogenerate icon' there would be an option to change the way the icon autogeneration happens.
For example in the LabVIEW icon editor, if you choose a template (which can be fully customised) which has a header, than the text entered in the icon editor is automatically placed under the header. Options like this, and also some other clever ways to cusomise the autogeneration of icons would make the customisation easier.
John Lokanis 5 years ago 0
When I am browsing the LabVIEW Tools Network, packages that I have already installed are not marked as INSTALLED.  So, I cannot be sure if I already downloaded something.  I would like to see thiswork like the Apple App Store, where it shows me what is installed and alsolets me know what is new and what is updated.
Christopher Relf 5 years ago • updated 5 years ago 0

So I have a lightbulb moment today: why do I have to switch from LabVIEW to VIPM to build packages? Why can't I right click on a package build definition in my project's "Build Specifications" and either edit the configuration or build it directly from there?

olivier-jourdan 6 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 5 years ago 1
[Related to this thread on JKI forum]

My use case is to create a package which install templates. These templates could have some identical VI in different directory.
VIPM, currently doesn't allow to build this type of package.  
Jonathon Green 5 years ago • updated 5 years ago 0
I would like control over specifying the name and location of internal dependencies. 

I envisage another entry in Destination (where if not configured, VIPM would just do what its doing at the moment).

This topic relates to this thread here.
Jonathon Green 5 years ago 0
This feature relates to VIPM Enterprise, but affects VIPM end users.

It would be handy if Deprecation was LabVIEW Version Specific, instead of global. 

This way a package would be shown in VIPM only for compatible versions of LabVIEW and hidden for non compatible versions.  
David_L 6 years ago • updated by Christopher Relf 5 years ago 3
To zip something up in a Zip file and send it to someone, it's as easy as going to the directory, right clicking files and choosing "Add to zip" or "Compress" depending on your software.  VIPM should add this option to the context menu so you can easily create a new build specification at this location.  
Greg Sands 6 years ago • updated by Jonathon Green 5 years ago 3
Currently, to see information on a package, it is necessary to double-click, which opens a modal window.  This makes it difficult to browse through a number of descriptions.  I suggest a preview pane (like in Windows Explorer) which either just shows the package description, or which shows all the contents of the package information window (including Install button etc).  Something like this hacked screen shot:
chrisreed 6 years ago • updated 6 years ago 5

My VIPM Package Table has so many entries now that I have to scroll up and down to view all the entries.  I was thinking that a Tree View of the packages would make it easier to view and organise.

For instance the OpenG Package would be the root folder and clicking on this folder would show all the individual packages ie. Array Library, Boolean Library etc..

Jubilee 6 years ago 0
Add 0-5 stars field to packages so users could rank the packages and even add comments, like in amazon, letting the community know how they use the package and how it helped them.
Jonathon Green 6 years ago • updated 6 years ago 2
It would be really cool if there was another option on the Insert pop-up for LabVIEW SubVI....  
I envision this would navigate directly to the <LabVIEW> or (maybe even better) the <vi.lib> symbolic directory.
Just something little to speed things up.

Jonathon Green 6 years ago • updated 6 years ago 0

Given the graphical paradigm of LabVIEW I think it would be sweet if I could click on an icon I see in the Insert >> LabVIEW Primitive... dialog to select it for the palette (rather than just text). 

Here is a quick edit (not complete) of what may be cool - to show all search hits with icons and text that could be scrolled through and double-clicked.

Jonathon Green 6 years ago 0

Just a small one... ...I think it would be sweet if the Insert >> LabVIEW Primitive... Dialog defaults to the previous search. 

It should have the text highlighted in focus so I can just type over it if I am doing a completely different search, but if I am in the middle of putting a bunch of like-primitives in the palette then there may already be there from the last keyword search.

Jonathon Green 6 years ago 0

This may be an edge case not worth the time but I thought I'd throw it out there. It would be nice if you didn't have to wait for the Palette Dialog to refresh if you have already opened it. A refresh button could force an update or it could refresh after each install (in the background could be nice). 

Jonathon Green 6 years ago 0
I would like the ability for VIPM to save a .png to disk of the palette. 
Of course I can do this with external utilities but, it would be quicker if it was native.
This will be used for documentation etc...

The VIPM palette is very similar to the LabVIEW one:

I don't mind any of the differences (VIPM logo etc...) being there.

Additionally, an option to select all (atomic action) subpalettes would be great, then just dump them everything to a folder.
Jonathon Green 6 years ago • updated 6 years ago 2
This one came up - installing the same palette in multiple locations. E.g. maintain forwards and backwards compatibility with a Top Level mnu, if that location changed. Also would benefit idea of Dynamic Palettes.  

The idea is that Palette to Installation Location relationship would be one to many.

Jonathon Green 6 years ago 0

Have been playing with the Custom Category and I really like it. 

One issue I foresee is the difficulty in updating all packages when there is a change of the Custom Category.

One way could be to allow the Custom Category to be synchronised to the currently installed Category palette with the press of a button:

Another way, possible better, would be to link to an external file. This way, you update the external file and the next time you load the VIPB it will update:

This file could be as simple as a 32x32.png file or maybe there could be an a GUI option that allows a new VIPM file type to be created.

I am just trying to think of the best of both worlds where your Top Level mnu package is not an external dependency and its really easy to update wrt changes.

Another idea is that it could be a separate package that is included as a sub-package (ties into Expose Sub Package idea. VIPM can upgrade to the latest if not already installed, but the user is only ever distributing/installing one package.
Jonathon Green 6 years ago 0
I thought it would be cool to know what fields are autopopulated but some small visual indicator. 
The only way we had to check was in the VIPB file. 
We had some issues where it was changing from PC to PC - mine to his and vice versa (based on previous 'favourite' entries?).
But I can see other use cases where it would be handy.