Comments below ... :) Jeffrey Harris wrote: think it depends on whether you're trying to introduce users to the
Chandler data model, or whether you're trying to describe a task the user might actually want to do without knowing anything about Chandler. "Add to task list" is a goal everyone will understand, "Make this a task item" doesn't suggest a workflow as strongly, but it does explain what's going on under the hood more accurately.
Actually, that was an attempt to cater to people not familar with Chandler, not to give people more of a peek under the hood. :)
If I were not familiar with Chandler, and see something that says "Add to task list," I would assume that means that there's an actual Task List somewhere in the Web UI where I can go to look at the things I've checked this checkbox for -- and that's something we're apparently not implementing yet.
I can see the benefit of unifying the language with Chandler, but I'm also thinking there's some value in making the prompts in what is ostensibly a separate app reflect what the app actually does (or in this case, doesn't do :)).
Matthew _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
