[RFC] Search box

Mads Kiilerich mads at kiilerich.com
Mon Apr 27 09:14:17 EDT 2015

On 04/27/2015 09:31 AM, Thomas De Schampheleire wrote:
> On Sun, Apr 26, 2015 at 10:23 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
>> On 04/26/2015 09:17 PM, Thomas De Schampheleire wrote:
>>> Redirecting to a search 'page' in order to be able to enter search terms
>>> is not very user-friendly and makes searching harder than it should be.
>> Yes, it would be weird if that search page only contained one input field. I
>> do however not see how a click to a new page with an input field is any
>> harder than a click that reveals an input field.
> One case is where the search terms you want to enter are derived from
> the content you are currently looking at, for example a particular
> commit. Having to move away from that page to get to the search page
> means you will either have to remember, or copy/paste (but this is
> only possible if the search terms you need are already adjacent on the
> existing page, which is not always true).

Sure. But if the globally available options depends on the content, it 
should make it very clear in what way that happens.

Note also how for example 
https://bitbucket.org/conservancy/kallithea/commits/all and 
https://bitbucket.org/conservancy/kallithea/issues?status=new&status=open have 
two search fields. It is hard to merge them to one while keeping it as 
simple and easy to use as it might look like it is. Having two fields 
might not be bad. (In their case I would have moved "Find a repository" 
to the Repositories menu.)


More information about the kallithea-general mailing list