[Geany] "Replace All" button order

[spir]

Le Fri, 16 Jan 2009 17:04:36 +0000,
Nick Treleaven <nick.treleaven at btinternet.com> a écrit :

> On Sun, 11 Jan 2009 18:50:36 +0100
> Enrico Tröger <enrico.troeger at uvena.de> wrote:
> 
> > >	[In Selection]  [In Session]  [In Document]
> > >
> > >"Selection" and "Document" are self-explanatory; "Session" replaces
> > >text in all currently-open files.
> > >
> > >Why are the buttons in this order? Intuitively, I would expect them to
> > >be ordered in terms of increasing scope: selection, document, session.
> > >I don't see why the current order would be preferable---I've never
> > >even used the "In Session" button in actual work.
> 
> I did it like that because the Gnome HIG says the most commonly-used
> button should be on the right, and I assumed it was the document
> button. Then it seemed logical to put the session button near the
> document button.
> 
> Anyway, the selection button can also be used often, so we could change
> the order to:
> 
> [Session] [Document] [Selection]
> 
> This also makes sense in making the function with the biggest impact
> away from the commonly used position.
> 
> > Good catch.
> > I agree it should be in the order selection, document and then session.
> > I don't remember when these buttons were added. In case I did so, I
> > probably just didn' think about and just added them.
> > In case of it was Nick, maybe he had a reason.
> 
> Regards,
> Nick

Some notes about the replace feature/interface:

-1- I think the arrow should go and these replace choices be visible from start -- does this serve
any purpose?

-2- Which choice is the most common or useful one can probably be discussed for nights... so I
propose the fasttest/default one to be the most secure one, i.e. "in selection" or "in
scope" (-->).

-3- I would add a "replace all in current scope" function that I dream of for years already ;-)
where 'scope' means closest nesting func, class, or whatever.

-4-This button and "in selection" should be invalid (greyed) whenever there is no 'scope' (module toplevel, meaning "in scope" = "in doc") or there is no selection.

-5- I would also add a "in project" choice to allow lexical evolution at project level. This would
walk together with file/doc/module registering in project. (The latter would also allow
straightforward project stage freezing/recording e.g into myProj-0.10-01_02_2009.tar).

-6- I'd love an '\i' code working in both the search & replace fields, that would mean 'indent' &
match the user specified value for one level of indentation in preferences (that is n spaces or
one tab).

-7- ?

denis

------
la vida e estranya