Your comments
Question on this. Would you just want VIPM to read the file and use the contents unformatted? If you set some text as Bold in the RTF file, would you want it bold in the license display. The latter is more difficult, but not impossible.
If your code calls VIs in dependent packages, then you can use the scan for dependencies feature. This would automatically populate the package list for the required dependencies. In this case there is no need to find the packages manually. However, I agree that the manual addition process can be improved.
One correction I'd like to make is that you can have subVIs in custom actions if the VIs you are calling ship with the LabVIEW version you are targeting. You could make a dynamic call to a subVI from the custom action that is installed at the target location which can contain SubVIs. Then you can delete the dynamic VI and subVIs. Another option is to create a LabVIEW executable that does the work you describe and then call that exe from a custom action VI.
I suggest that you create a separate idea request for the ability to modify ini files during package install\uninstall. Similer to modifying registry entries.
It would be great to implement this without the need to have an additional dependency package like the old OpenG had.
One possible solution is to modify the existing NI mnu files as new palette items get installed. The main issue with this approach would be that if you update LabVIEW to a patch release such as LabVIEW SP1, all of the customizations that VIPM made would get overwritten by the LabVIEW installer.
Thanks for the feedback. We are planning on adding more tutorials in our knowledge base to help with this. We'll also consider improvements to the UI to make it more intuitive in the next release.
Just wanted to let you know that you can now do this if you use the new VIPM 2012 API. You can create some LV code that can do this for you.
I'm not sure I understand what you are requesting. There are only a few tasks that you can perform on the repository. So a wizard would not have that many options. Could you elaborate a little on what you mean? Is there one task in specific that you are having trouble with?
Also, I don't follow how the Package Builder interface applies to the repository manager.
Customer support service by UserEcho
Thanks for the feedback. This is a great idea. Probably similar to this idea, but I think LabVIEW projects are better to use than libraries or possibly allow both.
http://ideas.jki.net/topic/55613-allow-libraries-as-build-source-instead-of-folders/