🚀 go-pugleaf

> A (serious) criticism of MacProject:
> MacProject is not capable of preventing assignment of a resource to
> multiple projects concurrently.  This is surprising, particularly as
> MacProject recognizes two different reimbursal strategies: so called
> multiple and single. ....
> If this program did indeed permit mutual exclusion (can anyone thing
> of a reasonable single-use resource for which one does not want
> mutual exclusion?) it would admit many more applications.  ...
> <sak>     ::= stuart | kurtz

I think this is a flaw also, but I'd prefer to have resources tagged
as "exclusive" or not, and be able to get a resource-loading report [
although the existing resource report does give a quick idea here].
I think that many of the people I've worked with are "reasonable single-use
resource for which one does not want mutual exclusion".  I find that many
normal activities are most simply modeled by using the elapsed time,
knowing that one will only work on that activity on a part-time basis.
[Ideally, one might be able to enter both elapsed & fraction worked,
like some other systems, but that might complexify it more than its worth].

Actually, what I miss most is a convenient ability to hierarchically
compose charts, i.e., so each person can keep more detailed charts,
but get overall dates and times included in master charts.  However,
I still find MacProject to be a good thing: the downfall of many
powerful project management systems has been the difficulty of getting
people to use them.  Even with its occasional irritations, MacProject
has not seemed to have this problem.
-- 
-john mashey
UUCP: 	{decvax,ucbvax,ihnp4}!decwrl!glacier!mips!mash
ARPA:	mips!mash@SU-Glacier.ARPA
DDD:  	415-960-1200
USPS: 	MIPS, 1330 Charleston Rd, Mtn View, CA 94043