jumping

[Andrew Abernathy]

On Sep 17, 2005, at 8:45 PM, Trevor Harmon wrote:

> On Sep 17, 2005, at 4:41 PM, Andrew Abernathy wrote:
>
>
>> Omni deciding to make changes in response to user feedback doesn't  
>> necessarily mean that we would change the _default_ behavior.
>>
>
> In that case, what did you mean when you talked about modifying the  
> current behavior based on user feedback?

It could _potentially_ mean that we would change the default  
behavior. Or it could mean that we provide a preference.

> I understand the impact on your documentation and localization  
> efforts, but I'm confused about the complexity issue. I can't  
> imagine a couple extra radio buttons generating so much confusion.

True, but a couple extra controls for this, a couple extra controls  
for that, pretty soon you're talking lots of controls.

> I would think most users expect to be able to customize  
> OmniOutliner's behavior to suit their needs, especially in its Pro  
> incarnation.

Certainly the barrier is lower for the pro edition. I'm not trying to  
leave the impression that I think flexibility is a bad thing - I  
don't believe one size fits all, and this isn't an app that is so  
tightly targeted that we don't need to accommodate a range of users  
and usage patterns. Indeed, we see the need for much more flexibility  
than currently exists (customized keybindings leaps to mind).

-andrew