Re: [pgadmin-hackers] About our GSoC projects

2010-08-17 Thread Guillaume Lelarge
Le 17/08/2010 16:08, Magnus Hagander a écrit : > On Tue, Aug 17, 2010 at 12:15 PM, Guillaume Lelarge > wrote: So, my basic question is: how do we handle this? I know Luis is interested to continue to work on his project. I don't know for Adeel. Anyway, perhaps a good way to do

Re: [pgadmin-hackers] [pgAdmin III] #220: Show/hide columns in frmStatus's reports

2010-08-17 Thread pgAdmin Trac
#220: Show/hide columns in frmStatus's reports --+- Reporter: gleu | Owner: gleu Type: feature | Status: closed Priority: minor| Milestone: 1.14 Component: pgadmin

Re: [pgadmin-hackers] Ticket 220: Show/hide columns in frmStatus reports

2010-08-17 Thread Guillaume Lelarge
Le 31/07/2010 19:23, Guillaume Lelarge a écrit : > Hi, > > This patch allows a user to select which columns are visible in each > pane (but not the log one). The user only needs to right click on the > list's header, and it will show him a popupmenu with all the columns' > names displayed as check

[pgadmin-hackers] pgAdmin III commit: Add support for showing/hiding specific columns in

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=05c0eba6bbac7c9f75d57821fbd6beaf2e1ba3bb Log Message --- Add support for showing/hiding specific columns in the server status window. Implements #220. Branch -- master Modified Files -- CHANGELOG

[pgadmin-hackers] pgAdmin III commit: Add a shortcut to trigger a properties' window. Pat

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=365e72d859c6f4c50294e4e011f544e6abdc1df8 Log Message --- Add a shortcut to trigger a properties' window. Patch from Steffen Kuhn. Branch -- master Modified Files -- CHANGELOG |2

[pgadmin-hackers] pgAdmin III commit: Disable the "output pad" menu when the user is on t

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=fb8ce19b4a1f3aebbc6d142a7d257d5dc7dffbe9 Log Message --- Disable the "output pad" menu when the user is on the GQB tab. Patch from Steffen Kuhn. Branch -- master Modified Files -- CHANGELOG

[pgadmin-hackers] pgAdmin III commit: Disable the "output pad" menu when the user is on t

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=54362ef968c872a52bac97f66dbff3c68b399f6f Log Message --- Disable the "output pad" menu when the user is on the GQB tab. Patch from Steffen Kuhn. Branch -- REL-1_12_0_PATCHES Modified Files -- CHANGE

Re: FW: [pgadmin-hackers] UI Addition Request. View Data > View BOTTOM 100 Rows

2010-08-17 Thread Guillaume Lelarge
Le 13/08/2010 02:07, Dave Page a écrit : > On Thu, Aug 12, 2010 at 11:08 PM, Matt Janssen wrote: >>> "Top" just means the first 100 returned by an unordered select query. >>> They're actually in a completely arbitrary order, as that's how >>> Postgres stores them, so "bottom" doesn't really make a

[pgadmin-hackers] Re: [pgAdmin III] #224: UI Addition Request. View Data > View BOTTOM 100 Rows

2010-08-17 Thread pgAdmin Trac
#224: UI Addition Request. View Data > View BOTTOM 100 Rows ---+ Reporter: Matt Janssen | Owner: Steffen Kuhn Type: feature | Status: closed Priority: minor | Milestone: 1.14

[pgadmin-hackers] pgAdmin III commit: Add a "View Last X lines" menu item. Suggestion fro

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=527e2972bfff8cb8f16db6155980760c6810496b Log Message --- Add a "View Last X lines" menu item. Suggestion from Matt Janssen. Patch from Steffen Kuhn. Implements #224. Branch -- master Modified Files

[pgadmin-hackers] [pgAdmin III] #224: UI Addition Request. View Data > View BOTTOM 100 Rows

2010-08-17 Thread pgAdmin Trac
#224: UI Addition Request. View Data > View BOTTOM 100 Rows --+- Reporter: Matt Janssen | Owner: Steffen Kuhn Type: feature | Status: new Priority: minor | Milestone:

[pgadmin-hackers] pgAdmin III commit: Update german translation, per Steffen Kuhn.

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=f1ecf845d4e5b15d128cb69b3808461e9d42cabc Log Message --- Update german translation, per Steffen Kuhn. Branch -- master Modified Files -- i18n/de_DE/pgadmin3.mo | Bin 192883 -> 192947 bytes i18n/de_D

[pgadmin-hackers] pgAdmin III commit: Update german translation, per Steffen Kuhn.

2010-08-17 Thread Guillaume Lelarge
Commit: http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=f63105ed148dbbcf57089ded432763e2442c3546 Log Message --- Update german translation, per Steffen Kuhn. Branch -- REL-1_12_0_PATCHES Modified Files -- i18n/de_DE/pgadmin3.mo | Bin 192883 -> 192947 byt

Re: [pgadmin-hackers] GSoC - Patch (Schema Difference Sync+ Visualization)

2010-08-17 Thread Dave Page
Hi Adeel, On Mon, Aug 16, 2010 at 10:13 PM, Guillaume Lelarge wrote: > No, it isn't "too much" strict. It's just more strict, more precise than > VC++. Yeah, just a bit :-). The main issue though, is that VC++ is setup to use precompiled headers which GCC isn't (I never got it to work properly).

Re: [pgadmin-hackers] About our GSoC projects

2010-08-17 Thread Magnus Hagander
On Tue, Aug 17, 2010 at 12:15 PM, Guillaume Lelarge wrote: >>> So, my basic question is: how do we handle this? >>> >>> I know Luis is interested to continue to work on his project. I don't >>> know for Adeel. Anyway, perhaps a good way to do this is to create two >>> dev branches on the pgadmin r

Re: [pgadmin-hackers] About our GSoC projects

2010-08-17 Thread Guillaume Lelarge
Le 17/08/2010 11:56, Dave Page a écrit : > On Mon, Aug 16, 2010 at 9:20 PM, Guillaume Lelarge > wrote: >> [...] >> I'm wondering how we should handle the GSoC projects now. They both give >> us their patches, and in both of them, they are quite some work to do. >> >> I didn't do a lot of work on A

Re: [pgadmin-hackers] About our GSoC projects

2010-08-17 Thread Dave Page
On Mon, Aug 16, 2010 at 9:20 PM, Guillaume Lelarge wrote: > Hi, > > I'm wondering how we should handle the GSoC projects now. They both give > us their patches, and in both of them, they are quite some work to do. > > I didn't do a lot of work on Adeel's one, but there is at least a lot of > work