[Biococoa-dev] Subversion proposal

[Charles Parnot]

Koen, thanks for that email. What you say is exactly true, and we  
should in fact decide if we want to create a separate project for  
Alex's code, this is the real bottom line. And I was arguing we  
should, but the option of having it available as a download is good  
enough for me.

To answer your question: yes, you would need to check out 2 separate  
projects when working on the trunk and on a branch (btw, there is  
only one trunk, not several "trunks", but several branches; think of  
a tree ;-) ...). And it is actually not very hard to manage. You just  
want to make sure you know which version of the project is open when  
you work on the code! Xcode can get a bit confused with the builds,  
so you may have to do some clean-up.
But this probably does not have to happen here anyway.

charles


> Hi,
>
> Since everything is tagged in svn, I guess it doesn't really matter  
> in what organization the files are entered into svn. Also in svn it  
> is very easy to change/rename directories.
>
> What I am more concerned with is how everything works with Xcode.  
> Which files are included into the project, only the latest? How are  
> trunks handled when using Xcode? Can I switch between trunks,  
> without exiting my Xcode project? Do we now make keep a separate  
> project for the example apps? Currently they all are in the same  
> project. But I understand from you guys input that the new demo  
> from Alex is a separate project.
>
> Another svn comment: I believe that svn doesn't like paths with a  
> space in it, so be aware where you put BioCocoa on your HD.
>
> cheers,
>
> - Koen.
>
> ps Peter, do you still need the zipped project in your mailbox?

--
Xgrid-at-Stanford
Help science move fast forward:
http://cmgm.stanford.edu/~cparnot/xgrid-stanford

Charles Parnot
charles.parnot at gmail.com