Re: Handling a project environment

[Derek Rendall <derek@csarc.otago.ac.nz>]

Hi,

Do not try to merge separate web apps - it will cause more problems than
it's worth. Sub projects are not the answer either. I would suggest
someone spending half a day or so creating the project and a (rough)
first page (that will link to other items, or however the site is going
to be laid out). Then put this into source control software. Each person
can then (independently) check out and work on a copy of the
application. They then check in their changes when they are working. 

If you do not have source control software then I would suggest CVS -
it's free, and available under OpenStep/Unix and NT (look for WinCVS).
Apparently Perforce is quite good too. We use this approach very
successfully in WebObject project teams of 2-5 people. The only tricks
with CVS is that EOModeler and Interface Builder need some extensions to
handle CVS directories well - I can supply code for that if you want.

"Sri Sankaran (TPA)" wrote:
> 
> Product:  WebObjects 4.0
> Platform: Windows NT
> 
> We are planning work on a project that will involve a team of 4 developers.
> Each will be building several screens and together these will constitute the
> application.
> 
> What is the recommended method of handling a WebObjects project with several
> team members each contributing toward the same application?  Does each
> person on the team start with an independent project and then have them
> somehow merged?  It seems like sub-project option is geared more towards
> projects that have sub-applications, in other words each builds its own exe.
> 
> Any pointers will be greatly appreciated.
> 
> Sri
> 
> ----------------------------------
> Srivaths Sankaran
> mailto:sri.sankaran@dcicorp.com
> (813)971-3707 x292.

-- 
Derek Rendall
Senior Software Engineer
Black Albatross
University of Otago
P.O. Box 56
Dunedin
New Zealand
ph +64 3 4795468
fax +64 3 4799033
http://www.albatross.co.nz