KDE Core/QtMerge/QTimeZone: Difference between revisions
(→ICU) |
|||
| Line 13: | Line 13: | ||
ICU does have a nasty API for most things, but that's what Qt is for :-) | ICU does have a nasty API for most things, but that's what Qt is for :-) | ||
===KDateTime vs QDateTime=== | === Qt Proposals === | ||
Steve has made a proposal based on Python. | |||
* http://lists.qt-project.org/pipermail/development/2012-January/001628.html | |||
* http://codereview.qt-project.org/#change,14405 | |||
* http://icu-project.org/apiref/icu4c/classTimeZone.html | |||
Lorn Potter has previously proposed patches based on Meego: | |||
* https://bugreports.qt-project.org/browse/QTBUG-71 | |||
=== KDateTime vs QDateTime === | |||
KDateTime obtains the current system time zone from KSystemTimeZones::local(), which in turn requires the ktimezoned daemon to update it with any changes to the current system time zone. This would prevent KDateTime from being moved into Qt without modification to this mechanism. Additionally, Qt would need to support Mac OSX and any other operating systems - currently, KSystemTimeZones is only supported on Linux and Windows. Note that all the KTimeZone classes would need to be moved to Qt also in order for KDateTime to work. | KDateTime obtains the current system time zone from KSystemTimeZones::local(), which in turn requires the ktimezoned daemon to update it with any changes to the current system time zone. This would prevent KDateTime from being moved into Qt without modification to this mechanism. Additionally, Qt would need to support Mac OSX and any other operating systems - currently, KSystemTimeZones is only supported on Linux and Windows. Note that all the KTimeZone classes would need to be moved to Qt also in order for KDateTime to work. | ||
Revision as of 10:36, 12 February 2012
QTimeZone
ICU
Qt5 locale will move to depending on ICU for localisation backend. ICU implements timezone support so any solution must well with this. ICU ships a version of Olsen which can be outdated and different form the system,by guarantees canonical tz names. It also provides translations to Windows tz names in ICU 4.4 and later.
References:
- http://userguide.icu-project.org/datetime/timezone
- http://userguide.icu-project.org/datetime/timezone/examples
- http://icu-project.org/apiref/icu4c/classTimeZone.html
ICU does have a nasty API for most things, but that's what Qt is for :-)
Qt Proposals
Steve has made a proposal based on Python.
- http://lists.qt-project.org/pipermail/development/2012-January/001628.html
- http://codereview.qt-project.org/#change,14405
- http://icu-project.org/apiref/icu4c/classTimeZone.html
Lorn Potter has previously proposed patches based on Meego:
KDateTime vs QDateTime
KDateTime obtains the current system time zone from KSystemTimeZones::local(), which in turn requires the ktimezoned daemon to update it with any changes to the current system time zone. This would prevent KDateTime from being moved into Qt without modification to this mechanism. Additionally, Qt would need to support Mac OSX and any other operating systems - currently, KSystemTimeZones is only supported on Linux and Windows. Note that all the KTimeZone classes would need to be moved to Qt also in order for KDateTime to work.
If KDateTime were merged into QDateTime, it would probably require source incompatible changes to create a nice API for the combined class.
A better way of merging KDateTime into Qt4 would be to add a new class alongside QDateTime. QDateTime would be kept as a simple class without any time spec (source incompatible change), alongside the merged KDateTime to be used when any time spec was needed. It wouldn't be a good idea to keep QDateTime unchanged in this scenario, since the current QDateTime's time spec property wouldn't play along very nicely with the new KDateTime class's more sophisticated time spec property - having both would lead to unnecessary confusion.