On Thu, Jul 9, 2009 at 1:17 PM, Julie S<[email protected]> wrote: > Good argument. But if these are easy to turn off, then the user who only > needed them for one segment can easly turn them off and be done with it. > Let's look at the efficiency of both cases.
I like the idea of using O(n)-style efficiency measures for user activity! Don't forget about expectation though. Something that requires one or two actions each time a window is opened may be costly, but it isn't necessarily more costly than something that requires one or two actions only half the time when a window is opened, if the user can't readily anticipate which half it will be. If the action is a single keystroke, the cost of hesitation probably outweighs the cost of performing the action itself. I think this probably weighs in favour of global control and remembering state in the settings rather than the composition file. But as you say, it really all depends on how users actually use the feature(s). Chris ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
