|
|
|
 The numbers that I gave were purely theoretical and should not be considered realistic - Karibou [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating: 
|
Display Modes |
|
|
|
| The numbers that I gave were purely theoretical and should not be considered realistic - Karibou [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#8
24-12-2009, 19:16
|
|||
|
|||
|
Re: C and LabView version control with Git
Yep, teams will be getting at least the SCC features of the pro version. The most beneficial feature of that is an integrated check-out and check-in locking. The VI files do contain some time stamps and even pointers in them, so they are not meant to be diffed outside of the LV editor. The LV editor does a graph comparison of the source and displays the objects and describes the differences. As of 8.6, I don't think merge is there or is a good implementation.
As for distributed development, Engineering firms usually seem to have ten or fewer programmers working on the same project in LV. Bigger than that and you need to isolate them into subgroups a bit. Even with that, and you need some coordination. Cowboys are a pain in the neck on any project, but can really cause issues on a LV project -- one of the tradeoffs of a graphical language. Greg McKaskle 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 2009 Control System LabVIEW Tips and Pitfalls | Travis Hoffman | NI LabVIEW | 3 | 22-12-2008 11:25 |
| LabVIEW Training and new control system demonstration 10/17-10/19 in Frazier Park, CA | Joe Ross | NI LabVIEW | 0 | 25-09-2008 13:25 |
| First problems with FTC and Labview | PhilBot | National Instruments LabVIEW and Data Acquisition | 0 | 10-09-2008 20:21 |
| Labview and communication with peripheral device help | jaijaidin | LabView and Data Acquisition | 3 | 26-01-2007 19:17 |
| version control and linux | shtylman | Programming | 2 | 01-05-2006 17:44 |
Threaded Mode