Обсуждение: some window sizes are not ok
Hello PgAdmin Team, I looked through the archive but didn't found something about that topic. Here is what I recognised: OS: Ubuntu Desktop: Gnome Task bar: default size (I just use one horizontal task bar on bottom). Screen size: 1024 x 600 (16:9) I used version 1.10.2 Language: German (no clue how to change it into English) Open pgadmin3 and click onto the left button (the power plug icon). A second window will be opened. The window is too big (high) - Unfortunately the buttons will disappear behind the task bar. File -> options -> general (hope the translation is correct) The "input" form will cover the text / description left next to the field. E.g. Path to bin directory ... only will be displayed as Path to bin dire and the the "input" form starts already. The warning at the bottom is cut too. There are two rows displayed correct but the third text row you just will see the top 3-5 pixel. Best Regards, Susanne -- Susanne Ebrecht Bielefeld
Hi Susanne, Le 04/01/2011 19:10, Susanne Ebrecht a écrit : > [...] > I looked through the archive but didn't found something about that topic. > > Here is what I recognised: > > OS: Ubuntu > Desktop: Gnome > Task bar: default size (I just use one horizontal task bar on bottom). > Screen size: 1024 x 600 (16:9) > You won't have a good experience with such a small display. IIRC, you need at least 1024x768. > I used version 1.10.2 > 1.12.2 is the last one :) > Language: German (no clue how to change it into English) > Menu File/Options, first Tab, "User language" combobox. > Open pgadmin3 and click onto the left button (the power plug icon). > A second window will be opened. > The window is too big (high) - Unfortunately the buttons will disappear > behind the task bar. > This should be fixed in 1.14, as we put some of the options in another tab. But it wasn't done for this. > File -> options -> general (hope the translation is correct) > The "input" form will cover the text / description left next to the field. > > E.g. Path to bin directory ... only will be displayed as Path to bin > dire and the the > "input" form starts already. > It shouldn't do such a thing. I'll look into this. Anyway, this dialog will be redesign for 1.14 (or at least, I hope so). > The warning at the bottom is cut too. > There are two rows displayed correct but the third text row you just > will see the > top 3-5 pixel. > Fixed in 1.12. Obviously, you should use the latest release :) -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
Hi, * Platform you're running on: win xp 32bit * Language: en * Distribution you used: binary * Version you tested: 1.12.2 In 1.10 and 1.12.1 the font of SQL query output contents depends on the Preferences font (set from Options -> Preferences -> Font), but in 1.12.1 it is now tied to Query Tool font (set from Options -> Query Tool -> Font) . Is it intentional or a bug? And maybe it makes sense to give user an option to change the Output grid content font separately from Preference and Query Tool fonts. But, my preference is to choose rather Preferences font instead of Query Tool editor font ;) Test case... Preferences font: Tahoma, 8 Query Tool font: Courier New, 9 Result: http://img23.imageshack.us/img23/7990/pgadmin1122font.png Thanks, -- Rainer
Le 05/01/2011 13:45, Rainer Kuhi a écrit : > Hi, > > * Platform you're running on: win xp 32bit > * Language: en > * Distribution you used: binary > * Version you tested: 1.12.2 > > In 1.10 and 1.12.1 the font of SQL query output contents depends on the > Preferences font (set from Options -> Preferences -> Font), but in 1.12.1 it > is now tied to Query Tool font (set from Options -> Query Tool -> Font) . > > Is it intentional or a bug? Intentional. We didn't actually set a font for the query output. We do now. > And maybe it makes sense to give user an option > to change the Output grid content font separately from Preference and Query > Tool fonts. But, my preference is to choose rather Preferences font instead > of Query Tool editor font ;) > I don't see why it would make more sense to have this other option. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
I could live with Courier New as the Editor and Output grid font, but I really need to see underscore symbols without dragging the cells taller. http://img23.imageshack.us/i/pgadmin1122font.png/ (notice missing underscores around "i") and using Tahoma for coding is not so funny ;) or what would you recommend? Thanks, -- Rainer -----Original Message----- From: pgadmin-support-owner@postgresql.org [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Guillaume Lelarge Sent: 5. jaanuar 2011. a. 19:16 To: Rainer Kuhi Cc: pgadmin-support@postgresql.org Subject: Re: [pgadmin-support] pgAdmin v1.12.2: SQL output grid font base Le 05/01/2011 13:45, Rainer Kuhi a écrit : > Hi, > > * Platform you're running on: win xp 32bit > * Language: en > * Distribution you used: binary > * Version you tested: 1.12.2 > > In 1.10 and 1.12.1 the font of SQL query output contents depends on the > Preferences font (set from Options -> Preferences -> Font), but in 1.12.1 it > is now tied to Query Tool font (set from Options -> Query Tool -> Font) . > > Is it intentional or a bug? Intentional. We didn't actually set a font for the query output. We do now. > And maybe it makes sense to give user an option > to change the Output grid content font separately from Preference and Query > Tool fonts. But, my preference is to choose rather Preferences font instead > of Query Tool editor font ;) > I don't see why it would make more sense to have this other option. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Hello Guillaume, On 05.01.2011 09:23, Guillaume Lelarge wrote: > >> Screen size: 1024 x 600 (16:9) >> > You won't have a good experience with such a small display. IIRC, you > need at least 1024x768. Let me point out something here: 600 is the size of eeepc and other notebooks. Before I wrote my email I made the mistake and asked on IRC. The result was that more ppl complained that it is a little bit annoying to use pgadmin on notebook. It seems to be a common use case that users just use notebook to administrate the server. One argument pro PostgreSQL is that the graphical administrator works also on notebooks at all. This is a great advantage that we have against another well known open source DBMS. And I just want to plead you to stay notebook compatible. Susanne -- Susanne Ebrecht Bielefeld
Le 07/01/2011 07:47, Susanne Ebrecht a écrit : > Hello Guillaume, > > On 05.01.2011 09:23, Guillaume Lelarge wrote: >> >>> Screen size: 1024 x 600 (16:9) >>> >> You won't have a good experience with such a small display. IIRC, you >> need at least 1024x768. > > Let me point out something here: > > 600 is the size of eeepc and other notebooks. > > Before I wrote my email I made the mistake and asked on IRC. > The result was that more ppl complained that it is a little bit > annoying to use pgadmin on notebook. > > It seems to be a common use case that users just use notebook > to administrate the server. > > One argument pro PostgreSQL is that the graphical administrator > works also on notebooks at all. > > This is a great advantage that we have against another well known > open source DBMS. > > And I just want to plead you to stay notebook compatible. > There is no way to *stay* notebook compatible because we've never been. Anyway, my laptop has a big resolution (1440x900), I don't own a netbook myself, and I don't intend to buy one just on the idea to write one patch. So, if you, or someone else, wants to work on this, sure, go ahead. I make no promise it'll ever be applied, but it'll be at least reviewed. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
Le 06/01/2011 15:05, Rainer Kuhi a écrit : > I could live with Courier New as the Editor and Output grid font, > but I really need to see underscore symbols without dragging the cells > taller. > http://img23.imageshack.us/i/pgadmin1122font.png/ (notice missing > underscores around "i") > > and using Tahoma for coding is not so funny ;) > > or what would you recommend? > > Thanks, > -- Rainer > > -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Guillaume Lelarge > Sent: 5. jaanuar 2011. a. 19:16 > To: Rainer Kuhi > Cc: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] pgAdmin v1.12.2: SQL output grid font base > > Le 05/01/2011 13:45, Rainer Kuhi a écrit : >> Hi, >> >> * Platform you're running on: win xp 32bit >> * Language: en >> * Distribution you used: binary >> * Version you tested: 1.12.2 >> >> In 1.10 and 1.12.1 the font of SQL query output contents depends on the >> Preferences font (set from Options -> Preferences -> Font), but in 1.12.1 > it >> is now tied to Query Tool font (set from Options -> Query Tool -> Font) . >> >> Is it intentional or a bug? > > Intentional. We didn't actually set a font for the query output. We do now. > >> And maybe it makes sense to give user an option >> to change the Output grid content font separately from Preference and > Query >> Tool fonts. But, my preference is to choose rather Preferences font > instead >> of Query Tool editor font ;) >> > > I don't see why it would make more sense to have this other option. > I actually have no idea which font would be usable for both the SQL editor and the results grid. We could have another option to set this widget's font. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com