Re: Function editor - Mailing list pgadmin-support

From Dave Page
Subject Re: Function editor
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4306ABA@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Function editor  ("Tony Caduto" <tony.caduto@amsoftwaredesign.com>)
Responses Re: Function editor
List pgadmin-support

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of
> Andreas Pflug
> Sent: 11 October 2004 15:27
> To: Tony Caduto
> Cc: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Function editor
>
> Right. That's why maximize isn't cleanly supportable. I'm
> strictly against redesigning pgadmin property dialogs as
> frames, and thus flooding the taskbar.

Yeah, definitely with you on that one.

Back in the old pga2 days, we used to use a control developed by the
quietest member of the devteam (Mark) for all the multiline edit boxes.
It had a handy feature in that it had it's own maximise button which
would maximise it to fill it's parent frame. This was actually quite
elegant and worked rather well. Before pgAdmin 3 was started, we had
toyed with the idea of making the textbox detachable (this is roughly
the point at which Andreas' head will probably explode :-) ) into a
mini-editor.

Now, if we added such a control to pga3, we could immediately make all
the dialogues back into 'real' dialogues. All we would need to do is
figure out how the detachable editor should behave (modally speaking for
example) with respect to it's parent dialogue and the rest of the app
for it to be able to work in a fashion that's acceptable and liked by
all.

Thoughts (preferrable constructive)?

Regards, Dave.


pgadmin-support by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Function editor
Next
From: Andreas Pflug
Date:
Subject: Re: Cannot connect to postgresql 7.4.2