The design I put together a long while back, but which I never got around to writing should have be simple to maintain. Basically split out the user auth part of the User model. Rename the model to List. A (new) User can then have "access" to multiple Lists - either full (meaning ability to add other users to the List, r/w or r/o) Tasks were not "owned" but by Lists.
A person/user can then view a list either in "single" list mode or overview mode - the overview being just a merged display. You can layer more on top of that, but this method is a simple first step. Plus can be done without major modifications. On Fri, Aug 28, 2009 at 6:43 PM, Reinier Balt <[email protected]> wrote: > My problem with this feature is maintenance. This will be very intrusive > code (all over the map) and much harder to bugfix than single-user > scenarios. I would like to see good tests to support it… >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
