GNOME Bugzilla – Bug 632024
Be able to start contact search using menu
Last modified: 2010-11-08 14:47:56 UTC
We all like minimalist design and the coolness of having a search bar magically appear as you type into the contact list, however, this goes against common usability principles. Namely, the current search bar is not discoverable by anyone but geeks (or people who have cats walking onto their keyboards while the contact list is in focus). So, my suggestion is to show the search bar by default (I presume we can afford those 10 pixels), or, if you don't want that, you could have an action to bring it up in the menus at the very least. However, if you "only" put it in the menus, users might (or probably, "will") not be aware of its existence. From experience, mom and pop don't go looking into menus.
Vertical space is a precious ressource, so I don't think always displaying the bar is a good idea. But indeed, we could add a "Search" entry in the "Edit" menu (like in Epiphany).
Fixed in repo: git://vminko.org/empathy branch: fix-632024
Created attachment 172465 [details] [review] proposed fix In case I did something wrong with git...
Review of attachment 172465 [details] [review]: Your commit message isn't very informative. I'd prefer something like "Add an entry in the Edit menu to search for contacts (#632024). ::: empathy-2.32.0.1/src/empathy-main-window.c @@ +958,3 @@ + + g_signal_emit_by_name (priv->individual_view, + "start-interactive-search"); Firing a signal on another object is not very clear. I'd prefer if you add API on the individual view. @@ +960,3 @@ + "start-interactive-search"); +} + There is a trailing space here; please remove it. git diff and git show you show you trailing spaces in red. ::: empathy-2.32.0.1/src/empathy-main-window.ui @@ +169,3 @@ + <object class="GtkAction" id="view_search_contacts"> + <property name="name">view_search_contacts</property> + <property name="label" translatable="yes">Find in Contact _List</property> That's a bit long. "Find Contact" ?
>I'd prefer something like "Add an entry in the Edit menu to search for contacts (#632024). I added the new item in the View menu, because I think it's more suitable for this item. Isn't it? >Firing a signal on another object is not very clear. I'd prefer if you add API on the individual view. >There is a trailing space here; Fixed in fix-632024-v2 >That's a bit long. "Find Contact" ? I believe that this long name is justified in this case, because we should explicitly distinguish this feature from the 'search contacts in the net' (which does not seem to be supported by empathy, but is quite common). Moreover, it's no longer than 'Previous Conversations", for example. If you don't agree - I will change it.
(In reply to comment #5) > >I'd prefer something like "Add an entry in the Edit menu to search for contacts (#632024). > > I added the new item in the View menu, because I think it's more suitable for > this item. Isn't it? Humm; I'd still be tempted to say it belongs to Edit: that's more coherent with other app such as Epiphany and "View" is usually used to display persistent options, while here it's more an action. > >That's a bit long. "Find Contact" ? > > I believe that this long name is justified in this case, because we should > explicitly distinguish this feature from the 'search contacts in the net' > (which does not seem to be supported by empathy, but is quite common). > Moreover, it's no longer than 'Previous Conversations", for example. If you > don't agree - I will change it. Fair enough.
>I'd still be tempted to say it belongs to Edit Fixed in the same branch (fix-632024-v2).
Sorry for nit picking, but "Preferences" is usually the latest item of the Edit menu in all GNOME apps. I'd put it after personnal info (and before the separator).
Sorry I should have noticed that. Fixed in the same branch (fix-632024-v2).
I accidentally merged an older version of your branch and moved it myself. Thanks a lot! This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.