Jump to content
News about the LabVIEW Wiki! Read more... ×

Search the Community

Showing results for tags 'project templates'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 1 result

  1. For a lot of my LabVIEW projects, I have been developing scripting tools to help team members get to a good starting point for their code or to remove human error when following templates. After seeing Becky Linton's presentation at NI Week in 2016 (link), I was inspired to use Project Templates to make it a little easier for the developers to get to. I have been able to get it to work to varying degrees at this point, but I have a question on how to handle project-specific dependencies. If I have a team working on a larger development project that has shared core code and we have it in a repository, everyone on the team usually puts the cloned source on a different location on disk. If my scripting tools have a dependency on code in that repository (class ancestor is biggest), then its location would move from development machine to development machine. Therefore, if I put my tools into the LabVIEW\ProjectTemplates directory, those dependencies would need to re-map for every user and that defeats the benefit to having it be a part of the Getting Started window - at that point it is easier just to point them to the scripting wizards that are pulled with the rest of the code from the repository. Does anyone have a good suggestion for how to accomplish a good structure with project-specific dependencies? Or am I trying to fit a square peg into a round hole for this type of application?
×

Important Information

By using this site, you agree to our Terms of Use.