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

[Alan Horkan <horkana maths tcd ie>]

On Tue, 4 Jan 2005, Markus Bertheau wrote:

> Date: Tue, 04 Jan 2005 23:25:01 +0100
> From: Markus Bertheau <twanger bluetwanger de>
> To: Alan Horkan <horkana maths tcd ie>
> Cc: usability gnome org
> Subject: Re: [Usability] How should an editor behave when it comes to
>     search and replace?
>
> У Втр, 2005-01-04 у 21:51 +0000, Alan Horkan пише:
>
> > It is an interesting idea and although people keep suggesting it I'll feel
> > much better when there are a few more implmentations out there,
> > particularly when someone tries it with a much more complicated
> > application than a text editor.
>
> Why? If I want to know if continuous save works with a text editor, why
> not write such a text editor?

Sorry if I wasn't clear.

Writing any application with 'continuous save' is an interesting idea.
I'd be interestd to know what metric are you used to determine how often
to save, how do balance the need for reliability against responsiveness?
If i pull the plug out what is the most I data i might lose, a few
characters, a line of text?

Writing a text editor is a good start and I look forward to someone trying
out the idea with more complicated applications, as some compound
documents dont lend themselves to incremental saves and it will be harder
to get everything rigth but still remain responsive.

- Alan H.