Brainstorming in public here, especially if someone wants to take a shot at this before I get to it :).
> Hi, I have the branch tristil on github. I haven't done anything yet > except update webrat so that the spec tests can run. I'm planning to hack on > the following features: > * an "other users" controller > > What is the purpose? If you want to see other users, you can extend > UsersController. Or do you want to see other persons stuff? > You're right. I'll use the users controller. What if I put nested routes for actions, projects and contexts under users? What I'm thinking is that /users should show the other users and perhaps a sampling of public actions, then you can click through to the user and the actions, projects, etc. The purpose is to be able to discover other people's stuff. Basically, the use case I have in mind is something like chores, that you could "take off" someone. In general, though, the best way to collaborate will be to 1) create a public/shareable project and then add another person to the project. In this case the actions in the project will be shared by default and completable by anyone. So I guess there will be added shared_status, created_by, assigned_to and completed_by fields. > * ability to make a whole project or individual todos "public" to other > users > > Should be either an extra state or a separate switch. I think the latter is > best, so it does not interfere with > > hidden-state of todos or projects. > I agree. > * ability to see the visible todos/projects in the other users controller > > Why not extending the current project controller and either enhance the > current views or create a new view? > See above. > * ability to "delegate" to another user > > * workflow that allows the other user to "accept" or "push back" (with a > message) the task > I think you need to think about the screenflow for these features. How do > you show a user that a todo was delegated to him. > > Perhaps you can combine this with the enhancement request for a way to see > todos that have come from the tickler and/or the backend_api. > Yeah, I was thinking as part of a messaging system: "User X wants to push an action to you. Accept?" It stays at the top of the page until you accept or decline. Then on each action there is a right-arrow (maybe a pushing hand) for delegation. > Well, we're going to RSpec, but it progress has been slow lately. We do > need the selenium tests, since they have not been converted to specs (any > volunteers?). I'm working with unit and functional tests (but I'm no > TDD-guru) > I'll probably work on these first. > rather use the more complete set of tests. Is anyone coding using an > autotest setup and which set are you using? > > I run them manually. > Thanks for the info. Btw, the recurring actions feature is totally awesome and useful for me. -- -J. Method
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
