From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Lucas <lucas75(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Layout Suggestion |
Date: | 2008-08-10 06:44:26 |
Message-ID: | 489E8E4A.2090108@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Lucas a écrit :
> [...]
> My suggestion is to have a tree view that suport search filters.
Yeah, I would like to have this too. Not sure how we should do it. I
think we should only filter object names. I also think we should be able
to target database, schema, and objects.
If I type "%foo%", I'll get every object named %foo% (and also databases
and schemas that can help me go to these objects, even if their names
aren't %foo%. %.%.%foo% would be a synonym of it.
If I type foo.s%.%bar%, I should get every %bar% object on every s%
schema on the foo database.
But what would mean foo%.%bar%? Ony the objects contained in %bar%
schemas of the foo% databases?
> Like the options dialog from eclipse.
> And to edit functions without opening a new window or make the edit
> windows not modal-like.
This is something that could be interesting. Problem is that it will
need a complete review of the UI, much much more than what I'm currently
doing. I don't think we'll go that way.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-08-10 10:20:42 | Re: Support for integrated tsearch configuration |
Previous Message | Lucas | 2008-08-07 02:36:34 | Layout Suggestion |