 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Programming / Mac Programming / September 2007moving code around
I frequently copy my source code to and from my mac-formatted disks to disks formatted with NTFS... in earlier days I heard that you can loose 'resource forks' if you do this sort of thing... but now we have OS X..... is this something I still need to worry about? TIA > I frequently copy my source code to and from my mac-formatted disks to > disks formatted with NTFS... [quoted text clipped - 5 lines] > > is this something I still need to worry about? Resource forks generally only apply to applications. The idea is that the app and all its required files (icons, gui translations etc.) are all bundled together. I think that you should seriously consider a networked source control system (svn, Perforce, cvs etc.). A bientot Paul  SignaturePaul Floyd http://paulf.free.fr > I frequently copy my source code to and from my mac-formatted disks to > disks formatted with NTFS... Rather than move code back and forth between machines, set up a source code management (revision control) system and keep independent work areas on each of the machines. That will ensure that your checkouts are all correct. I usually recommend Subversion because it works well and it's free, though we're in a bit of a renaissance of SCM systems these days so there is a very wide variety of options you can choose from. Anyone who thinks "I don't need SCM, I'm a one-person shop" or "I don't need SCM, my projects are small" is terribly wrong. You may be able to get by without SCM but you're really just making things harder for yourself by trying to do so. -- Chris > > I frequently copy my source code to and from my mac-formatted disks to > > disks formatted with NTFS... [quoted text clipped - 14 lines] > > -- Chris I second this. At home, I check in to my personal SCM multiple times per work session, and I make frequent use of Xcode's "compare" command (on its contextual menu when a text file is frontmost) that compares the current state of the file with its most recent checked-in version. (The compare button on the SCM panel of the "Get Info" window of the file lets you compare with any previous checked-in version.) If you are copying source from machine to machine, you NEED SCM. You are doing the very act that SCMs were invented to help with (well, one of them.) > I second this. At home, I check in to my personal SCM multiple times per > work session, and I make frequent use of Xcode's "compare" command (on > its contextual menu when a text file is frontmost) that compares the > current state of the file with its most recent checked-in version. (The > compare button on the SCM panel of the "Get Info" window of the file > lets you compare with any previous checked-in version.) Thirded. SCM is like a backpack: it means you're carrying even *more* stuff (since you have to learn and use the SCM system) but it makes everything else so much easier to carry. In the long run it will save you a vast amount of time, even if you only ever work alone on a single computer. For anyone reading this who does not yet use SCM, I heartily recommend that you stop what you're doing and go obtain and learn svn, right now. You'll thank me for it later. SignatureMichael Ash Rogue Amoeba Software |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.