On Thu, Jun 16, 2011 at 9:04 PM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
> On Thu, 2011-06-16 at 20:54 +0100, Dave Page wrote:
>> On Thu, Jun 16, 2011 at 8:48 PM, Guillaume Lelarge
>> <guillaume@lelarge.info> wrote:
>> > On Wed, 2011-06-15 at 23:48 +0200, Jasmin Dizdarevic wrote:
>> >> Yeah, I know. All of the dialogs have a "binding" to some pgObject,
>> >> because all of them modifies something.
>> >
>> > No, see dlgFindAndReplace.
>>
>> Yeah, back in the early days there was some confusion about what was a
>> form (window) and what was a dialog - I don't want to add to that now.
>>
>> In pgAdmin virtually all of our dialogues are actually more like
>> regular windows because they are sizeable. That's a conscious
>> decision, made for reasons of usability and consistency. With that in
>> mind, I consider forms to be the "main" application windows, eg.
>> frmMain, frmQuery, frmDebugger, frmStatus and so on. Everything else
>> is a dialogue - a popup to perform a quick task eg. vacuum, backup or
>> search/replace, to adjust program options (frmOptions is one of the
>> mistakes!), or to define/display properties of a database object.
>>
>
> One of the things I want to do for 1.16 is a new options dialog. We
> already discussed its design. I wonder if we should also change it to a
> dlgOptions file. Is it OK for you?
Absolutely :-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company