DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
AudioVideoDisco

Distribute DQMH Template Metadata as code

Status: Declined

Hi @AudioVideoDisco,

We are sorry to decline your idea.

We think that your problem can be fixed by using VI packages to distribute your templates. Developers would create modules based on templates installed with the .vip instead of templates based on copies of sources.

 

That said, we appreciate your time you took the time to share your thoughts here.

Please keep those ideas coming!

 

Distribute DQMH Template Metadata alongside the template (i.e. not in [LabVIEW Data]/DQMH Module Templates). With the goal to enable template XML metadata to be distributed and versioned as code.

This would solve the problem where each developer has a slightly different template configuration and needs to go through the "Create DQMH Module Template" process when setting up a new system etc.

 

Example workflow:

  1. Clone new project containing it's own set of custom DQMH templates
  2. Add new DQMH Module
    AudioVideoDisco_1-1676587419411.png
  3. Specify path to template (template location includes all relevant metadata alongside in the same folder).
    AudioVideoDisco_3-1676587813117.png

     


     

 

 

1 Comment
Olivier-JOURDAN
Active Participant
Status changed to: Declined

Hi @AudioVideoDisco,

We are sorry to decline your idea.

We think that your problem can be fixed by using VI packages to distribute your templates. Developers would create modules based on templates installed with the .vip instead of templates based on copies of sources.

 

That said, we appreciate your time you took the time to share your thoughts here.

Please keep those ideas coming!

 


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!