04-21-2020 08:53 AM
Hello everybody
we already used the toolkit for some exciting ideas, thanks again to Q for providing the toolkit! You saved us a lot of work and helped us to made modular and propper code.
We are now asking ourselves how we can best share the different QControls in our team. The idea was to compile each QControl as PPL and then distribute them all together as a VI package. This way the QControls Facade can also be registered in the controls palette and the New/Close methods in the funtion palette. The wish is that the controls can not be changed anymore.
Are there already other people who share controls as a collection? How do you do that?
Regards
Matthias
04-23-2020 07:15 PM
On my team, we do package our shared QControls in PPLs for reuse purposes. However, I haven't gone so far as to make packages for them.
Another example, though, is the QControls that come with the QControl Toolkit. They are the ones you can access in the palettes and there are examples in the example finder.
So, I have done both of what you suggest, just not together. There should be no technical limitations for putting QControls in PPLs and distributing them via a package manager (i.e. VIPM). This will keep the underlying code in the QControl from being changed. However, it won't stop a user from using a different facade. You could package the facade you want with it, (that's why I included the Facade Folder), and add it to the controls palette. It might take some training for your users, but that would be easier than replicating that UI functionality all over the place.
Chief LabVIEW Architect, Testeract | Owner, Q Software Innovations, LLC (QSI)
Director, GCentral | Admin, LabVIEW Wiki | Creator, The QControl Toolkit
Certified LabVIEW Architect | LabVIEW Champion | NI Alliance Partner