Re: [Usability] How should an editor behave when it comes to search and replace?

[Martyn Russell <mr gnome org>]

On Tue, 2005-01-04 at 23:33 +0000, Alan Horkan wrote:
> On Tue, 4 Jan 2005, Martyn Russell wrote:
> > Personally, I have always hated the way a search or search & replace
> > type dialog worked since it always needs to be moved because it is above
> > something you are reading on a web page or in a document.
> 
> Smart programs move the window if it is in the way or they scroll enough
> so that the word isn't obscured.

That annoys me too because I expect the window to be in a certain
position and if it keeps moving it makes me look at it and away from the
information I want, not to mention if I am clicking on Next several
times it means I can't just click the mouse button but I have to move
the mouse first.  

> > The new search mechanism that Firefox uses from version 1.0 (I think)
> > where a small entry box and some options appear at the bottom of the
> > window is a great idea.
> 
> I noticed this, eventually (not sure which Mozilla related product it was
> though).  A searchbox for the current context appears just above the
> status bar.  Unfortunately I was expecting a pop-up dialog and it wasn't
> obvious that anything had actually happened so it took a while for me to
> discover what was giong on.

It isn't a big change, and after a few seconds, you notice it and go on
as you were.  I think for that small amount of time you spend learning a
new method to do something, you gain a lot more with the improved
usability.

> > Plus the whole idea about having colours when
> > the text doesn't match and optionally highlighting every instance in a
> > document is just brilliant in my opinion.
> 
> In a really large document highlighting every match could be a little bit
> time consuming and at the very least is more effort to code than 'Find
> Next'.  

It is an option.  It would need to be for the reason you mention. ;)

-- 
Regards,
Martyn