|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Source/Version Control
I'm not sure privacy would be a real issue. Your team's programmers and their mentor should be the only ones who know where the code is and as long as they don't go post the link somewhere online, I don't think it would be easy for the public to find your code on GitHub.
|
|
#2
|
|||
|
|||
|
Re: Source/Version Control
Quote:
Given how I'm not even sure how to set up a LabVIEW repository on GitHub in the first place, as well as the fact that you can get Perforce for free with ~20 users, I'm almost convinced I should just get into the morass of converting my desktop into an Apache server with Ubuntu Server and Perforce. I could use it to host our website too. Anyone else here have any advice for LabVIEW vs Java? The benefits I see of LabVIEW are ease of learning, ease of debugging, and data collection. The only benefit I can really see of Java would be support, but people here are probably more experienced with it than I am. |
|
#3
|
||||
|
||||
|
Re: Source/Version Control
Github can host any files, even executables. LabView should be no problem.
|
|
#4
|
|||||
|
|||||
|
Re: Source/Version Control
This year 364 used a BitBucket mercurial repository with TortoiseHg Workbench. You can commit, push, pull, and merge, but you obviously can't see changes without opening the code. Commit messages are really important since you can't see changes on the fly.
TortoiseHg: http://tortoisehg.bitbucket.org/ BitBucket: https://bitbucket.org/ Screenshot of TortoiseHg from our repository: http://i.imgur.com/QhCvkhm.png/ |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|