| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Kozusznik Michal <kozusznik(dot)michal(at)ifortuna(dot)cz> |
| Cc: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: backup improvements |
| Date: | 2013-02-23 18:59:42 |
| Message-ID: | 1361645982.15634.94.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Sat, 2013-02-23 at 18:48 +0000, Kozusznik Michal wrote:
> Unfortunately it proves that way you have chosen doesn't match best practices for creating UI.
That's probably not the only one bad choice in UI on pgAdmin :)
> Besides, it makes impossible to execute backup once again with the same or slightly changed backup settings (what I already prooved).
Yeah, I understand that. Changing the button behaviour will get against
some other users wishes, and so won't happen. Having the dialog remember
the old values is something I would like to see coming though.
> Also I didn't ask form hide anything. I'm asking to leave it without changes. Instead of changing meanin of backup button, just pop up some modal requester with the information. 2 birds with one rock.
>
Well, the "hide a button" came from your comment: "curious the Cancel
button remains".
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Gill | 2013-02-23 23:31:42 | pgAdmin crashing in Windows |
| Previous Message | Guillaume Lelarge | 2013-02-23 18:54:05 | Re: Editable resultset |