On 7/10/07, Quentin Mathé <[EMAIL PROTECTED]> wrote:
> Le 8 juil. 07 à 02:11, Yen-Ju Chen a écrit :
>
[snip]
>
> > DictionaryReader was recently changed to use toolbar for search field.
> > But search field in toolbar cannot become the first responder.
> > Therefore, users have to click on the search field every time they
> > want to search,
> > instead of having cursor automatically in the search field when window
> > get focus.
> > So I probably will change it back later (not using toolbar).
>
> I will fix this bug related to toolbar and I also really need to find
> time to merge customization support (I have to merge it from -toolbar
> branch in GNUstep -trunk). I would prefer to keep toolbar since it
> helps to standardize UI and gives really nice features. In the
> meantime, I'm perfectly fine with current solution. Do you know if
> this responder bug also appears with basic text field?

  Regarding to toolbar, here is a short discussion with Guenther:

On 7/9/07, Guenther Noack <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I just couldn't wait any longer and had to download the Etoile SVN again
> to have a look at your changes on DictionaryReader. I am really quite
> pleased with it. Why did you turn off the toolbar and use buttons
> instead? I thought using toolbars was something like 'in the Etoile UI
> guidelines'? I also believe it's more likely to see toolbar items grey
> out when disabled than buttons. (I always wonder why GNUstep doesn't do
> this yet anyway.)
>

 The main reason is that I want to have the search field become
 first responder of window automatically every time the window
 got focused so that user don't need to click on the search field often.
 It seems hard to do with toolbar.

 Another thing is that toolbar is for convenience and is optional.
 If there is no toolbar, users can still have the menu and other UI
to do the same thing.
 For DictionaryReader, it is not the case.
 Users solely depends on that search field for main function.
 Therefore, to me, it is not suiltable to be a toolbar.
 Another example you can think is the web browser.
 In general, the so-called "toolbar" for input URL is not an optional UI,
 but an essential UI.
 In that case, Safari does not provide a way to hide such "toolbar".
 Firefox does, but it is probably never used.

 I am open-mind about using toolbar.
 But in this case, I think it is better to keep the main UI always on window,
 while toolbar is designed to be customized and hidden if needed.

 Yen-Ju

> Best regards,
> Guenther
>
>

>
> Cheers,
> Quentin.
>
>
> _______________________________________________
> Etoile-dev mailing list
> [email protected]
> https://mail.gna.org/listinfo/etoile-dev
>

_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev

Reply via email to