|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
LuNaTeCs 2016 LabVIEW Code Release!
I know, I know, it's late. But here is team 316 the LuNaTeCs 2016 LabVIEW code release. For this year's code, since we had multiple programmers, we had to find some sort of version control. The best option that we found was dropbox. Since we could not use Github for LabVIEW code, this was the quickest and easiest option that we could find. It worked well until the end of the season, when the code was sustained less and some extra .ALIAS files were generated. These files are referencing some paths inside of the Dropbox, which obviously the downloader does not have access to. However, the end user should not need those files to open, use, or copy the code. If there are any issues with opening a file, please PM me or leave a comment on this form.
While I have your attention, the programming team is looking towards switching to Java for the 2017 season, any suggestions? Thank you all very much! |
|
#2
|
||||
|
||||
|
Re: LuNaTeCs 2016 LabVIEW Code Release!
If you have a very good mentor base in Java and not one in LabVIEW, then go ahead. If not, it's probably better to stick what you know with for now. IMO the benefits of switching to Java are more than outweighed by the downsides of having to learn to program the robot in a new language in the middle of the season. Programming a computer application in Java is very different from programming a robot. Wait till next off-season and let the programming team take time with as many old robots as possible to reprogram them in Java. Let them iron out the kinks of Java programming in the off-season, not in the middle of the build season when they need to be on their best game.
|
|
#3
|
||||
|
||||
|
Re: LuNaTeCs 2016 LabVIEW Code Release!
Thank you for the reply. We do not have any Java mentors and only one programmer, me. I have practiced with the FRC over the summer and have learned a lot. However, I was still planning on still doing LabView this season and dabbling in Java when I have the time. Thank you.
|
|
#4
|
||||
|
||||
|
Re: LuNaTeCs 2016 LabVIEW Code Release!
You can still use github for LabVIEW code, just not some of the built in site/git features. Using github for LabVIEW code would be a better option than dropbox.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|