Re: [Nautilus-list] remembering different properties in differentdirectories?

[John Sullivan <sullivan spies com>]

on 10/17/01 7:08 AM, Calum Benson at calum benson sun com wrote:

> John Sullivan wrote:
> 
>> This doesn't seem to be a very strong argument for window manager control.
>> Putting a splash screen at a hardwired location is simply bad. Centering it
>> on the screen is always better. The application should be able to center the
>> splash screen. Why does the window manager need to get involved?
> 
> Well, it's better as long as your display isn't split across two
> physical screens, at which point you get a splash screen plastered over
> the join.  This sounds like a case where the window manager would know
> better?

Sure the window manager might know better, if the window manager were smart
about multiple screens. But if the application were smart about multiple
screens, the application would know better too

I agree that it's best for there to be one piece of code that handles
centering a window. This code can be the place that knows about measuring
the screen, keeping out of the way of panels, multiple screens, etc. There
are at least three places to put this code:

(1) In each application. Error-prone because there's no guarantee that each
application will do it right.

(2) In each window manager. Error-prone because there's no guarantee that
each window manager will do it right.

(3) In some built-in part of the system, perhaps a utility in gnome-libs or
something like that.

Each of these three approaches has its own costs and benefits. In the simple
splash-screen case, it seems clear to me that (3) is the least problematic.

John