From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Oh no!! |
Date: | 2003-07-15 09:36:50 |
Message-ID: | 3F13CB32.3060202@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 15 July 2003 09:33
>>To: Dave Page
>>Cc: pgadmin-hackers
>>Subject: Re: [pgadmin-hackers] Oh no!!
>>
>>
>>Dave Page wrote:
>>
>>
>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>>>Sent: 15 July 2003 08:07
>>>>To: pgadmin-hackers; Dave Page
>>>>Subject: Oh no!!
>>>>
>>>>
>>>>This message popping up every time a query finishes in query
>>>>window is
>>>>completely annoying. I hated it with pgadmin2, and it was one
>>>>reason for
>>>>me to write pgadmin3. And people in the same room working
>>>>with you will
>>>>soon hate it too, unless you remove your speaker or beep
>>>>device.... I removed it.
>>>>
>>>>
>>>>
>>>>
>>>Please put it back with an option to switch it off if you
>>>
>>>
>>dislike it so
>>
>>
>>>much. I hate running non-queries and not seeing that they have
>>>obviously completed.
>>>
>>>
>>>
>>Later we might add some animations (spinning thing in right
>>side of the
>>toolbar, and vacuum needs something too)
>>The idea behind the query window is that all input is in the
>>upper half,
>>and all output is in the lower. Messages are mostly duplicated now,
>>(message page and status line), and triplicated with that
>>msgwindow. I
>>just changed frmQuery so that in case no result set is returned the
>>message page is selected.
>>
>>
>
>Mmmpph. Still doesn't make it obvious to me that a long running query
>has completed. I'll try it out, but if I find it's no good then the
>message box goes in with an option to enable/disable it.
>
>
>
>>This is becoming quite an option grave.... Don't like that either. It
>>looks as if we couldn't decide what's working and what's not. Options
>>should merely be for dividing beginners from advanced users.
>>I'd really
>>like to stick to a consistent behaviour.
>>You might complain that the logging facility isn't sufficient
>>for you,
>>but that may not mean that the message window doesn't reflect what's
>>going on with the *current* query. Then we'd need an
>>additional logging
>>page. And the possibility to save it to disk. And a clear
>>option. And ...?
>>
>>
>
>And? That sounds good to me though the save to disk and clear options
>are unnecessary
>
Right, you may cut-and-paste to KWrite instead of saving and clear is
already implemented with Alt-F4 :-)
> (yes, I realise you were being sarcastic). We are trying
>to build feature rich software after all. Session logging is a useful
>feature that's been in both previous versions of pgAdmin. pgAdmin II
>even added a query recorder option to allow logs of sessions to be
>maintained in a useful format.
>
"History" might even be a better title for that page.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-07-15 09:53:35 | Re: Missing strings in pgadmin3.pot |
Previous Message | Brage Førland | 2003-07-15 08:54:38 | Missing strings in pgadmin3.pot |