CLosing apps

[Matthew Woehlke]

Maciej Pilichowski wrote:
> On Friday 24 April 2009 18:41:37 Matthew Woehlke wrote:
>> Hmm. Well, if there are nested containers you end up at the deepest
>> container. I don't think we talked about context-menu keys yet, but
>> that obviously means there needs to be one to bounce from the
>> current context menu to the parent context menu.
> 
> Do you mean that context menu of child app should contain extra entry 
> like "parent container" + submenu with all actions related to parent 
> container?

That would be one way. In fact that's probably better than what I was 
thinking, since that menu could also have a submenu for the grandparent, 
and so on as needed.

> I don't think that providing an option for user for customizing policy 
> would affect any part of new UI (I mean in a bad way). Remember 
> pretty long thread not so long ago about closing apps. With this UI 
> approach there would be no discussion at all -- "don't like the 
> defaults, no problem, just switch the option".

Yes, I remember; that's basically the exact question we're trying to 
deal with :-).

>> What about a policy that close doc will close the application also
>> if there are sibling instances of that app? I think I would be okay
>> implementing it that way. It would be similar to your proposal
>> except you would be using close doc instead of close app, but the
>> not-last ones would "really" close app.
> 
> If you think of policy I am not for it, but I don't have anything 
> against it. If you think about hardcoded policy I am against it :-) 

Nah, my intent was it should be configurable :-).

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
What sort of trite mind
Didst produced this signature
 From random input