+1

rename dependencies (without renaming package files)

Andy Soukup 5 years ago • updated 5 years ago 2

What is it?

currently you have the ability to add a file name prefix/postfix to all package files. I am proposing that we have the ability to add a file name prefix/postfix to ONLY the dependencies. This would be identical to the way that NI allows you to rename the dependencies in packed libraries.


Why is this needed?

When migrating your code into packages, you're presented with this series of events:

  1. I have X.vi. It is some piece of re-usable code that hasn't yet made it into a VIP.
  2. I build package A.vip and it has dependency X.vi included in the package
  3. I have application Application.vi that has dependencies A.vip and X.vi 
  4. Now, when i open Application.vi, I am unsure which X.vi will be used?!
Now, as a consequence of me applying configuration management, I have now completely lost configuration management if X.vi! (darn!). Usually, you are able to migrate X.vi into a package fairly quickly, but if you're working with a large library of reusable code (mine is 2300 VIs), this becomes an issue. 


With this change implemented, the series of events changes to:

  1. I build package A.vip and it has dependency X.vi included in the package as A_X.vi (assuming you add "A_" prefix to dependencies)
  2. I have application Application.vi that has dependencies A.vip and X.vi 
  3. Now, when i open Application.vi, the application uses X.vi and A.vip used A_X.vi

for a full discussion of this issue, see this thread http://forums.jki.net/topic/2103-rename-vi-dependencies/page__gopid__5165

I think the definition of a dependency in the context of VIPM needs to be defined. Would this be VIs that:

  • Live outside of the source folder
  • Live beneath LabVIEW
  • Live in other installed packages
  • All of the above

I would define dependencies as files that satisfy all of the following:

  • outside the source folder
  • not beneath labview
  • not in other installed packages
basically, i'm looking to rename all extra files included in the VIP that did not originate from the source folder.
This change should be completely transparent and backward compatible. Unless people are using these files that are not included in the palette.