Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x
Subject: Re: Clock widget for different timezones
Message-ID: <1991Jun24.224923.2746@smsc.sony.com>
Date: 24 Jun 91 22:49:23 GMT
References: <9129@gollum.twg.com> <8488@auspex.auspex.com> <9151@gollum.twg.com> <8508@auspex.auspex.com>
Sender: dce@smsc.sony.com (David Elliott)
Organization: Sony Microsystems, San Jose, CA
Lines: 26


In article <8508@auspex.auspex.com>, guy@auspex.auspex.com (Guy Harris) writes:
|> >BTW.. I feel that the clock widget definitely *should* have
|> >a resource setting for which time zone to display.  After all
|> >the code doesn't always run on Unix so the TZ variable isn't
|> >always available.
|> 
|> So what would it do with that setting?  A resource giving just an offset
|> from GMT isn't sufficient for all purposes, for obvious reasons....

It seems to me that the point of this resource would be to force some
kind of system-independent behavior.  We could define a set of values
that would be "sufficient for all purposes".  Since we're out here in
Unix-land, we could define the syntax for TZ to be sufficient.  I doubt
that many non-Unix systems would find this to be insufficient for most
purposes.

I personally wouldn't mind seeing xchrono's Clock widget being made
the standard Athena Clock widget.  The location, AM/PM, and date
labels make it useful all alone.

--
...David Elliott
...dce@smsc.sony.com | ...!{uunet,mips}!sonyusa!dce
...(408)944-4073
..."Art is never fair" - paa