[Chandler-dev] Proposal for a startup-options dialog

[Bryan Stearns]

Heikki Toivonen wrote:

>Alec Flett wrote:
>  
>
>>+1 - Bryan's solution is an excellent one to a frustrating problem. It's
>>not meant to be discoverable, its not meant to be accessible (though it
>>is, meta keys are perfectly accessible)
>>    
>>
>
>The reason I suspect it might not be accessible is because you either
>need to hold down one key while clicking another, or first click
>something then quickly hold down another. Both of these can be
>problematic for people with certain disabilities.
>  
>
The point is to get rid of the hurdles we place in front of all users 
whose repositories get hosed: they all currently need to run a command 
line, or find a platform-specific folder in a weird location that isn't 
even visible to most Windows users.

It turns out that it takes almost a second after launch (and longer on 
Mac ;-) to get to the point where the ctrl key state is tested, but it 
seems harmless on Mac & Windows (haven't tried Linux, but I expect it's 
the same) to hold down ctrl before starting the launch. If that's a 
physical hardship for some users, those users could go find the command 
line (that is, the same hurdle we're forcing on them them now) and use 
--ask to get the box (this new command-line option wasn't in my 
proposal, but is supported in the patch that I've attached to bug 
5904).  (The benefit to doing this is that the file that gets created 
not only has their repository, but also their chandler.log, twisted.log, 
and version.py - this mechanism gets us more information than before, 
and in a consistent format, with less user effort.)

>
>But I am confused about your statement that refresh-ui is not functional
>at the moment... Bryan's proposal included that option in the dialog,
>did it not? So either asking the user to do it or doing it automatically
>isn't that big a difference in code.
>
One more time, with feeling: the point of the dialog is to keep users 
from having to figure out how to run Chandler from the command line or 
find their profile directory. So yes, there's intentionally no 
difference in code between asking the user to specify --refreshui on the 
command line versus clicking a radio button in the dialog; this is 
because all the dialog does is set the command-line option flag.

The existing --refreshui command line option is indeed not completely 
functional right now, and John has a separate bug about this.

...Bryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060517/69729a93/attachment.html