So then, on a default SuSE 8.2/KDE (with a full gnome install as well), and
running pgadmin3 under KDE:
Add the lines Raphael suggested (below) to the file `etc/X11/gtk2rc-keramik`,
then restart pgadmin3. This will adjust the font & font size pgadmin3 uses.
Note that only arial 7 works well. Other fonts and/or larger sizes cut off
controls. I also installed 100dpi fonts, and changed gnome's default to
render fonts at 120 dpi, as this minimized the differrence in rendering fonts
between the desktops.
The other problem, namely fonts and/or controls on the forms being cropped is
due to the xml-based *.xrc files that pgadmin uses to create the
dialogs/forms. The problem is they are designed to be static. This is fine
if they are only used for one language and one font size combination.
This is likely, IMHO, the reason why the pgadmin3 team made distinct forms for
every language supported by pgadmin3. However, this only solves half the
problem. If you need or want to use a font/fontsize that renders larger than
arial 7-8 does, then text and controls will be clipped. For example, arial
10 makes pgadmin3 completely unusable on my setup.
IMHO, these xrc files should be using "sizers" to ensure suitable form
rendering at various fonts/font sizes (and maybe among various languages as
well). The general rule of thumb, gleaned from the wxWindows website and
other wxWindows developers' sites is that one sizer should be used for each
control. Doing this should solve this problem. One consequence of doing
this would be to increase the size of the xrc files by about 3-4 times. This
may be an issue on slower systems or systems with poor xml parsers.
I will be redesigning these forms to use sizers, starting with frmOptions,
which I will submit to pgadmin-hackers to get feedback on whether the
developers want to pursue this with the remaining forms and add them to the
distribution.
Thanks for all of your help, and congrats to the developers and testers on
reaching v1.0!
Regards,
Mark
On Friday 19 September 2003 08:13, [EMAIL PROTECTED] wrote:
> Hi Mark,
>
> Here is the result of the thread Andreas was talking about:
>
> Try to put something like this in your ~/.gtkrc-2.0 file and tell us if it
> solves the problem.
>
> <-cut here--->
> style "defaultfont"
> {
> font_name = "Arial 8"
> }
> widget_class "*" style "defaultfont"
> <-cut here--->
>
> You can find the entire thread on wx-users list:
> http://lists.wxwindows.org/cgi-bin/ezmlm-cgi?8:mss:44237:200309:jgdnbjmpiag
>pccbpjnpb
>
> Regards,
> Raphaël
> Message d'origine
>
> >Date: Fri, 19 Sep 2003 11:48:03 +0200
> >De: Andreas Pflug <[EMAIL PROTECTED]>
> >A: "Mark A. Taff" <[EMAIL PROTECTED]>
> >Copie à: [EMAIL PROTECTED]
> >Sujet: Re: [pgadmin-support] pgAdmin III Bugs/Feature Requests
> >
> >Mark A. Taff wrote:
> >>On Thursday 14 August 2003 01:28, Andreas Pflug wrote:
> >>All,
> >>I have finally been able to compile wxGTK w/o errors (I had to install
> >> some more devel rpm's and become intimate with pkg-config). I also
> >> compiled pgAdmin3 from cvs source just now. Per Andreas' suggestion, I
> >> am indeed linking against wxGTK 2.5. However, I am still having the
> >> same display issues, to wit:
> >>
> >>Label fonts are too large, being cut off by other controls
> >>Some controls likewise are cut off by the window edges
> >
> >There's obviously a bad default font configured on your system. We had a
> >thread about how to fix this, unfortunately we didn't put this into the
> >FAQ immediately.
> >
> >>I also noticed a problem with CSS that may be relevent. Konquerer
> >> applies CSS properly, displaying the documentation in traditionall
> >> Postgres blue, etc. However the builtin help browser does not seem to
> >> apply the CSS. IMHO this is the cause for the gigantic fonts in the help
> >> browser.
> >>
> >>Could a CSS/XML issue be the root of my problem? Any ideas?
> >
> >The help browser doesn't support CSS, but that's not the reason for the
> >bad display. We implicitely use the system's font.
> >
> >Regards,
> >Andreas
> >
> >
> >
> >---(end of broadcast)---
> >TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to [EMAIL PROTECTED] so that your
> > message can get through to the mailing list cleanly
>
> ---(end of broadcast)---
> TIP 7: don't forget to increase your free space map settings
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
