[Daniel Bathgate]

I would agree with the sentiments already expressed in this thread. As the only programer on a rookie team last year, it was relatively easy to get going with C moving from a Java background. Learning a completely new paradigm in the six weeks would have been nearly impossible. My only experience with LabView was from the camera setup, and I found it quite confusing.

Another thought, what kind of source management system (if that would even be the correct terminology for a graphical environment) works with LabView? Now that our team has grown and we will have multiple programmers (who were recruited for knowing C), we are considering keeping all of the source in a Subversion repository. Would this or something similar be possible using Labview?

Although I don't know enough about LabView to form a valid opinion on its use, I agree that we would need ample time before the build season to prepare for such an extreme change. Last year I attended a WWRF workshop in November or December that help bring me up to speed for programing the robot in C - workshops such as these would be vital for the use of LabView. I also generally favor simpler low level solutions and would be extremely hesitant about moving away from good old C.