[Kstars-devel] [bug] KStars should use system time zone and DST data

[Daniel-Marian Baboiu]

I agree that time should be stored ad JD - maybe with additional fields
as UT (also DST independent), to avoid recalculating it every time we
need it. Time zone rules should indeed go outside kstars - all OS ans
desktop environments have tables of time zone rules for all areas, not
only for the local zone. For example, the clock applet in KDE can handle
multiple time zones at the same time. 

On Tue, 2012-01-10 at 23:48 +0400, Aleksey Khudyakov wrote:
> Hello everyone!
> 
> I've just submitted a bug about time handling in KStars. Does anyone 
> have comments? Bug description is pasted inlne
> 
> 
> 
> 
> Now KStars uses its own system for handling time zones and daylsight 
> saving time (DST) rules. This is wrong for several reasons:
> 
> 1. It's not correct. Time zones and DST change over time. KStars cannot 
> handle it.
> 
> 2. They'll become out of date when rules change. In fact they are out of 
> date already.
> 
> 3. It's very complex. We canot make it better than it's already done. 
> It's just a wasted effort.
> 
> In my opinion KStars should store time internally as julian date or 
> something similar. It's simple since it doesn't have to deal with abrupt 
> jumps in time when DST kicks in. It's just a number so it's easy to 
> manipulate time intervals. Transformation to/from YYYY:MM:DD HH:MM:SS is 
> required only  when  time is presented/being read  from user and could 
> be done on demand.
> 
> On downside it require overhaul of all time handling in kstars.
> 
> 
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel