[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Misc. comments

From: Pascal J. Bourguignon
Subject: Re: Misc. comments
Date: Mon, 15 Jan 2001 02:52:07 +0100 (CET)

From: Alexander Malmberg <address@hidden> wrote:
> - I work quite a lot with 3d-rendering and modelling, so I often use
> ridiculously high resolutions. Thus, the GUI really must be resolution
> independent (resolution as in dpi). How is this supposed to be handled
> in GNUstep? Is the backend supposed to rescale everything transparently
> (so dimensions given in a program are really 1/72's of an inch, not
> pixels), or are the widgets supposed to take font sizes into account
> when calculating their sizes?

This is a  problem related to the subjacent  drawing architecture, and
to the way the pictures/icons are defined and drawn.

On NeXTSTEP,  with a display of 96  dpi, some scaling was  done by DPS
when a  window was specified  to contain 72dps picture.  Actually, DPS
being so good  at isolate the device resolution  from the application,
it was really easy for application to add zooming functions.

However,  the small  pictures such  as scroll  bar buttons,  or window
title buttons were defined as  bitmaps, and would not be zoomed nicely
when changing the resolution.

This  is a  problem that  will become  even more  important  as 200dpi
screens begin to appear.

NSImage is able  to handle pictures defined in  several ways. We could
store  thes small pictures  and icons,  in NSImages  with a  couple of
bitmap  representation  with different  resolutions,  and a  vectorial
representation of  higher resolutions. The  problem is to  define them
and store them in our resource files.

Also, with the  current scheme where it's the  window manager who does
the drawing of  the window adornments, part of  the problem belongs to
the window  manager too. With WindowMaker,  we can change  the size of
the icons in  WPrefs.app. However, it seems that  it's not possible to
change the  font/fontsize used for window titles  and WindowMaker menu
(at least, I can't find it in WPrefs).

Right now,  the application can  quite easily "zoom" the  GUI elements
inside its windows. It would be better if it was handled by the AppKit
for all the applications, by default.

__Pascal Bourguignon__    PGP Key ID:      0xEF5E9966                     (o_
mailto:address@hidden    PGP fingerprint: 00 F5 7B DB CA 51 8A AD 04 5B  //\
http://informatimago.free.fr/index         6C DE 32 60 16 8E EF 5E 99 66  V_/

() Join the ASCII ribbon campaign against html email and Microsoft attachments.
/\ Software patents are endangering the computer industry all around the world.
   Join the LPF:     http://lpf.ai.mit.edu/      http://petition.eurolinux.org/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]