Log in if you already have an account. If you would like to become an editor for the wiki, request an account.
Difference between revisions of "LabVIEW"
(Tweak external links.) |
|||
| Line 9: | Line 9: | ||
==In the Team== | ==In the Team== | ||
| − | From [[2009]] to [[ | + | From [[2009]] to [[2013]], the team used LabVIEW as their programming language. The reasons behind this were that LabVIEW had amazing debugging capabilities that blew the other options ([[Java]] and [[C++]]) out of the water. For this reason and this reason only [[Tanner Smith]] made the decision to try out LabVIEW and the team has used it until the [[2014|2014 season]]. |
== External Links == | == External Links == | ||
Revision as of 23:01, 18 August 2013
LabVIEW is a visual programming language. In the 2009 FIRST FRC season it was introduced along with the National Instruments cRIO.
Features
LabVIEW features a uncommon graphical programming language. Instead of writing lines of code, programmers now drag blocks of Virtual Instruments "code". Features of LabVIEW include:
- Ease of use for new programmers
- Advanced, real-time debugging capabilities
One feature that LabVIEW lacks is the ability to mesh well with Version Control Systems such as Git or SVN.
In the Team
From 2009 to 2013, the team used LabVIEW as their programming language. The reasons behind this were that LabVIEW had amazing debugging capabilities that blew the other options (Java and C++) out of the water. For this reason and this reason only Tanner Smith made the decision to try out LabVIEW and the team has used it until the 2014 season.