On 20.07.2011 22:45, Guillaume Lelarge wrote:
On Wed, 2011-07-20 at 21:41 +0200, Erwin Brandstetter wrote:
On 20.07.2011 20:26, Guillaume Lelarge wrote:
On Wed, 2011-07-20 at 19:05 +0100, Dave Page wrote:
On Wed, Jul 20, 2011 at 6:05 PM, Erwin Brandstetter
wrote:
Aloha!
A lot of work has
On Wed, 2011-07-20 at 21:41 +0200, Erwin Brandstetter wrote:
> On 20.07.2011 20:26, Guillaume Lelarge wrote:
> > On Wed, 2011-07-20 at 19:05 +0100, Dave Page wrote:
> >> On Wed, Jul 20, 2011 at 6:05 PM, Erwin Brandstetter
> >> wrote:
> >>> Aloha!
> >>>
> >>> A lot of work has been put into when a
On 20.07.2011 20:26, Guillaume Lelarge wrote:
On Wed, 2011-07-20 at 19:05 +0100, Dave Page wrote:
On Wed, Jul 20, 2011 at 6:05 PM, Erwin Brandstetter
wrote:
Aloha!
A lot of work has been put into when and where to refresh the browser
window.
From my experience it is often a _good_ thing, t
On Wed, 2011-07-20 at 19:05 +0100, Dave Page wrote:
> On Wed, Jul 20, 2011 at 6:05 PM, Erwin Brandstetter
> wrote:
> > Aloha!
> >
> > A lot of work has been put into when and where to refresh the browser
> > window.
> >
> > From my experience it is often a _good_ thing, that changes via SQL are no
On Wed, Jul 20, 2011 at 6:05 PM, Erwin Brandstetter
wrote:
> Aloha!
>
> A lot of work has been put into when and where to refresh the browser
> window.
>
> From my experience it is often a _good_ thing, that changes via SQL are not
> reflected in the browser window immediately. Serves me well as a
Aloha!
A lot of work has been put into when and where to refresh the browser window.
From my experience it is often a _good_ thing, that changes via SQL are not reflected in the browser window immediately. Serves me well as a poor
man's undo-tool.
On the other hand, one tends to forget about re
