Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Developer Center > xcode and svn

xcode and svn
Thread Tools
Fresh-Faced Recruit
Join Date: Nov 2004
Status: Offline
Reply With Quote
Mar 4, 2007, 01:37 AM
 
Hi, developers,

I am new to xCode. Now I have a problem that has to do with svn and xcode, which goes like this:

I am building a java tool, which does some text processing on a large corpus (text files). All my corpus are on a remote host. I have been using SSH + Vim the whole time to hand-code everything. Now I really wanna use the wonderful xcode tool for development. But I don't wanna actually copying the corpus to my local machine. I'm thinking of setting up a SVN on the remote host. Then I could check out the code from the remote machine. But how do I deal with the corpus?

Can anyone give me some suggestions on what the best solution to this? Thanks.
     
Professional Poster
Join Date: Oct 1999
Location: :ИOITAↃO⅃
Status: Offline
Reply With Quote
Mar 4, 2007, 08:15 AM
 
I do this all the time. I'd do one of three things:
1. Download a subset of the corpus and do your development work with that.
2. Do like you really should and develop unit tests -- code against those locally, and then just sync up to run longer tests on the corpus.
3. Suck it up and download the corpus. It can be very useful to have a local copy to browse through -- I've found myself examining text corpora in ways I wouldn't bother to when the files seem "far away".
     
Fresh-Faced Recruit
Join Date: Nov 2004
Status: Offline
Reply With Quote
Mar 4, 2007, 10:31 AM
 
Originally Posted by Mithras View Post
I do this all the time. I'd do one of three things:
1. Download a subset of the corpus and do your development work with that.
2. Do like you really should and develop unit tests -- code against those locally, and then just sync up to run longer tests on the corpus.
3. Suck it up and download the corpus. It can be very useful to have a local copy to browse through -- I've found myself examining text corpora in ways I wouldn't bother to when the files seem "far away".
Mithras,

Thanks for the suggestion. I think I'll try the first option first. One problem with that might be about the path to the corpus. Some of my team will need to access and test my code on the corpus on the remote machine. Maybe I'll just pass that as a run time parameter.
     
Professional Poster
Join Date: Oct 1999
Location: :ИOITAↃO⅃
Status: Offline
Reply With Quote
Mar 4, 2007, 08:11 PM
 
Yeah, I usually do one of two things with corpus paths:
a) put the corpus in the same path on your local machine. Nothing stopping you from doing a quick
sudo mkdir -p /projects/corpora/text/foo/bar
or whatever on your Mac.

b) Have a FOO_DATA (or whatever) environment variable, which is set appropriately in your .bashrc (or an 'init.sh' script) on the local and remote machines.

Good luck!
     
Fresh-Faced Recruit
Join Date: Nov 2004
Status: Offline
Reply With Quote
Mar 4, 2007, 08:13 PM
 
Thanks a lot!!
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 02:47 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2