Excerpts from Marcus Williams's message of Fri Jan 11 09:20:58 -0800 2008: > This patch adds a multi key combination to expand the thread index > view to all available threads. Note that this could return _a lot_ of > threads, which is why I've used a double keypress '!!' as a guard to > accidental usage. Its useful in conjunction with the tag all and apply > to all commands though.
This does make me a little nervous. Is the use case always that you want to apply a command to all threads for a given search? If so, I wonder if it would be better to explicitly model that, without the intermediate process of loading all the threads. If we're going to have a potentially long-running activity like this available from the UI, then I'd prefer to do it in a manner that gives the user an indication of how long until completion, the ability to abort, etc. How does gmail handle this type of thing? Or is everything so fast with gmail that it doesn't matter? -- William <[EMAIL PROTECTED]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
