View Single Post
  #2   Spotlight this post!  
Unread 09-05-2008, 20:54
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Labview Revision Control

Quote:
Originally Posted by Joe Ross View Post
The only problem is that the document implies that you have to have a supported version control solution to take advantage of the graphical differencing. Most of the supported software costs thousands of dollars. The supported CVS client costs $27 per license, which adds up. Are there any cheaper ways to get graphical differencing?
The difference feature is part of LV, not part of the CVS or another repository tool. So, you can diff independent files, or revisions of the same file from within LV, and it is potentially independent of the CVS system.

Even with merge, you will want to use CVS a little differently. You will likely want to lock files to prevent multiple simultaneous edits. As you noted, it isn't quite as convenient to merge LV code graphs as it is to merge textual C files. The lock doesn't have to prevent simultaneous edits, but it means that both parties are aware of the upcoming merge, and aren't surprised by it.

Merge is in the works, by the way, and if you embrace subVIs and modular code, LV can scale to medium sized teams of SW engineers (10 or so). But the SCC tools and LV diff and merge features aren't mature enough to support large or huge teams easily, at least not yet.

Greg McKaskle
Reply With Quote