Re: re: Mr. Project DB

Mikael Hallendal wrote:

>
> > As every task is owned by a person, only the owner can edit it. So no
> > collision can happen as described by you. The person can break a task
> > into subtasks and make more detailed plans from a big task it was
> > assigned as beeing responsible for it and it accepted beeing
> > responsible for it.
>
> Great, this is the kind of discussion that I would like at this point.
> This solution would solve the issues I raised, is this a solution that
> makes the software easy to work with at the same time?
>

You are talking about a multiuser system here - in P3 the ability to assign and
revoke prevledges to groups of activities is used to manage access by various
sub-contractors as part of the update cycle, since activities in this context are
basicly by agreement and used for invoicing only the administrator can create
them or delete them. I think perhaps gnue is headed in this direction but
MrProject so far has a sort of 'internal' flavour.  Maybe some kind of interface
could be envisioned. I wish also that someone who knows XML would look at the
gnue reportwriter - maybe some kind of integration would work there too.  I have
a wild dream about a non-centralized planning system but that is so far as far
featched as KS Robinsons' Martians rescuing the Earth with 'eco-economics'. The
plain fact is that the person with the money drives the project.