LeahEdwards Posted October 23, 2022 Report Share Posted October 23, 2022 I stumbled upon these today in VI package builder under File > Save As Template , but I am struggling to find the documentation. Am I right in saying they allow you to set the Source Directory, Product Name and Company Name upon opening the .vipt file (including where they are used e.g. in automatic package filename), but pre-set other fields of the new .vipc? 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted October 23, 2022 Report Share Posted October 23, 2022 1 hour ago, LeahEdwards said: Am I right in saying they allow you to set the Source Directory, Product Name and Company Name upon opening the .vipt file (including where they are used e.g. in automatic package filename), but pre-set other fields of the new .vipc? Yes, that’s the general idea. Please let me know how it goes. BTW, we’re working on updated documentation here (and it’s far from complete) as there are a lot of new features in the works. https://docs.vipm.io/package-building/vi-packages-build-templates/ BTW: the documentation is in a public GitHub repository, so you can suggest edits by clicking on the little edit icon ✍️ -Jim 1 Quote Link to comment Share on other sites More sharing options...
LeahEdwards Posted October 23, 2022 Author Report Share Posted October 23, 2022 Thanks for clarifying @Jim Kring. The new documentation centre looks great, handy being able to edit too. Unfortunately I don't think I will be able to use VIPT files for what I need to do. I have a template LabVIEW project which has a VIPC, and I want to replace every instance of the word "TEMPLATE" in the VIPC when a new project is spun up. This includes places like the product description summary, product description and pallette names. I believe in the past I would have been able to edit the xml of the VIPC but it seems that it doesn't work on VIPM Free any more, and I can't guarantee the template users will have Pro. Am I missing something here? Quote Link to comment Share on other sites More sharing options...
LeahEdwards Posted October 23, 2022 Author Report Share Posted October 23, 2022 (edited) Scratch that, I've found it in the API! Missed it first time I looked. Edit: But I see now that it works for Community but not Free. Will this change for VIPM 2023+? Edited October 23, 2022 by LeahEdwards Realised I was using community license, not free Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted October 23, 2022 Report Share Posted October 23, 2022 @LeahEdwards Yes, in 2023Q1 you'll be able to use VIPM Community Free Edition to call the API and edit the vi package build spec. And, you should still definitely buy VIPM Pro... Quote Link to comment Share on other sites More sharing options...
LeahEdwards Posted October 23, 2022 Author Report Share Posted October 23, 2022 So this feature is not coming to Free? It seems to work in Community already. In that case, I'll add that to the list of reasons to buy Pro. 1 Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted October 23, 2022 Report Share Posted October 23, 2022 Sorry, I mistyped that. I meant to say, "in 2023Q1 you'll be able to use VIPM Community Free Edition to call the API..." Quote Link to comment Share on other sites More sharing options...
LeahEdwards Posted October 24, 2022 Author Report Share Posted October 24, 2022 No problem, thank you! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.