On Sat, Mar 24, 2012 at 12:20 AM, Reinier Balt <[email protected]> wrote:
> > This is not an easy task (you are btw not the first to ask). The datamodel, > security model and functionality was all build around the concept of todos > belonging to one user. Changing this is a major effort I think. I made a mistake when I first wrote the multi-user part of the code. In hindsight I should as split the design into two parts - users and lists. Users would have rights access to lists - read, assign task, edit task, add project, add context or admin - but lists hold tasks, not users. Then it's just a matter of an overlay interface for merging the set of lists into a users UI. I think pretty much every semantic would be covered by a design like that. Unfortunately I never got time to rewrite the code, and Tracks is well past where I have the knowledge any more to hack something like that into the design. Nicholas
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
