On Friday, January 27, 2012 18:36:05 Thiago Macieira wrote: > On Friday, 27 de January de 2012 16.03.51, Stephen Kelly wrote: > > On Friday, January 27, 2012 13:30:35 Thiago Macieira wrote: > > > Correct. What do we need extending them with? The only virtuals you > > > left in > > > the API were stream (which I didn't get) and utcOffset, which > > > doesn't seem to need to be a virtual. > > > > Different timezones (and countries) have daylight savings time at > > different times of the year (or different days from year to year). > > Different implementations of utcOffset would take account of that. So > > there's a dependence on both the timezone and the datetime object. > > > > What do you propose? > > I see. You're proposing a public class for the time zone *engine* (and that > should be the class name). I don't think that's necessary, though.
Yes, you could say that. > There are likely only two engines: Olson and Windows. And one of them is > platform-specific. > > > > > And therefore the olson db and > > > > windows registry timezone information code would need to be in > > > > QtCore?> > > > > See Lorn's email. I don't know why we'd need to keep them in QtCore. > > > > Lorn's email said he used the windows and olsondb info. If not in > > QtCore, > > where would they go? > > The DBs themselves or the engine? The engines should be in QtCore. And you want to import olson into src/3rdparty? > > Is there any system outside of Windows that doesn't have the Olson DB? I don't know. <snip> > We don't want to store just the offset if we know more. Timezones often > change around during the year... Yes. Thanks, -- Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
