Article View: comp.sys.next.programmer
Article #530Re: NeXT project management software
From: Lyle Parkyn
Date: Tue, 11 Aug 1992 07:02
Date: Tue, 11 Aug 1992 07:02
43 lines
2719 bytes
2719 bytes
In article <167588INNjnn@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art Isbell) writes: > > My request for info about NeXT project management software resulted in few > responses, probably because there's not much out there. > > RCS is distributed with NeXTSTEP, but the last time I looked (2.1), it was a > very old version. RCS is file-based, so is not very suitable for the complex > 3.0 development directory structure. > > CVS extends RCS to the directory level and adds binary file version control > capabilities. 3.0 InterfaceBuilder and ProjectBuilder don't work well with the > CVS administrative directories placed in each directory under CVS control. > I've written make targets that seem to take care of these problems, but this > isn't a foolproof solution. NeXT probably won't address this problem in 3.0. > > No one at NeXT has commented on what is used by NeXT. > > Meanwhile, back to CVS for now. Wonder what it would take to add a NeXTSTEP > front-end to this puppy?.... Art I agree with you on this. NeXT project management is fine for self-contained projects for a very small number of people. Get more involved or try maintaining separate libraries used across multiple projects and it looks like things will get messy, with lots of potential for screw-ups. I like to develop a class in its' own directory with a test application. The developed and tested class would then be put into a library which is used by the main project. This works well using CVS and hand-carved makes. Ideally, I'd like use Project Manager to setup sub-apps (testers) and put together the libraries. I've asked a couple of NeXT tech people about this and it's not possible in 2 or 3.0. I've never taken the time to try making appropriate preambles/postamble makes. It would be nice if the project management software could be CVS aware. Then those that want to use it could and those that don't won't have to. Really makes you curious about how others are handling large projects, including NeXT. (Bet they don't even use ProjectManager) -- ===== ldp@pkyn.questor.wimsey.bc.ca (Mail and/or NeXTMail ) Lyle Parkyn - Reveal Development Service
Technical Details
Message-ID:
<1992Aug11.070213.9062@pkyn.questor.wimsey.bc.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!van-bc!pkyn.questor.wimsey.bc.ca!ldpReferences:
<167588INNjnn@darkstar.UCSC.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!van-bc!pkyn.questor.wimsey.bc.ca!ldp From: ldp@pkyn.questor.wimsey.bc.ca (Lyle Parkyn) Newsgroups: comp.sys.next.programmer Subject: Re: NeXT project management software Message-ID: <1992Aug11.070213.9062@pkyn.questor.wimsey.bc.ca> Date: Tue, 11 Aug 1992 07:02:13 GMT References: <167588INNjnn@darkstar.UCSC.EDU> Sender: ldp@pkyn.questor.wimsey.bc.ca Reply-To: ldp@pkyn.questor.wimsey.bc.ca (Lyle Parkyn) Organization: V-NUS (Vancouver NeXT Users Society) Lines: 43