Few comments from my side: * Agree with Thiago, that the class should be value based and called QTimeZone * I think such a class would be good to have in QtCore, but * I'd prefer if we don't have to ship the database. As noted it can change easily and a compiled in database would get out of sync. * ICU has timezone support as well. Something that could simplify our life? * Do we need to support both the Windows and Unix format, or could we get away with Unix only in a first version (if e.g. ICU provides the data)?
Cheers, Lars On 1/31/12 1:13 AM, "ext Stephen Kelly" <stephen.ke...@kdab.com> wrote: >On Tuesday, January 31, 2012 01:07:50 Thiago Macieira wrote: >> On Tuesday, 31 de January de 2012 00.51.17, Stephen Kelly wrote: >> > > The DBs themselves or the engine? The engines should be in QtCore. >> > >> > And you want to import olson into src/3rdparty? >> >> If we can avoid it, we should. That's what I'm waiting to hear from >>Lorn, >> about the Windows TZDB. > >Whatever you're waiting to hear from him, maybe he missed the request for >it. I did too for that matter. > >-- >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 >_______________________________________________ Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
