[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Caching local time zone
From:       David Jarvie <lists () astrojar ! org ! uk>
Date:       2006-09-21 23:05:52
Message-ID: a7a1c4e5f486197706630bd8f4a4e9ad () webmail ! plus ! net
[Download RAW message or body]

On Thursday 21 September 2006 22:53, Shaheed wrote:
> > > I'd first suggest rethinking the design. Say, a kded module (with the
> > > right kded startup phase, see kdebase/ksmserver/README) that does
> > > whatever initial checks needed, saves the current timezone to some config
> > > file and KTimeZone uses only that.
> > 
> > What should happen during startup if an application requests time zone
> > information before the kded module has run?
> 
> How about an environment variable? If that made sense, it might be possible to 
> combine that with this idea for per-user TZ settings in KDE: 
> 
> http://lists.kde.org/?l=kde-pim&m=112379368522252&w=2

Your proposal for per-user TZ settings sounds a good idea to me. But when an \
application asks for the local time zone, it is  likely to be in the context of \
wanting to convert a date/time value to or from that zone. So even if the zone \
identity is  readily available, it will still need all the KSystemTimeZones \
initialisation to run at that point. So the question remains as  to what should \
happen if the request is made before the kded module runs.

--
David Jarvie.
KAlarm author & maintainer.
http://www.astrojar.org.uk/linux/kalarm.html


[prev in list] [next in list] [prev in thread] [next in thread]