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

List:       kde-pim
Subject:    Re: [Kde-pim] KBlog library
From:       David Jarvie <lists () astrojar ! org ! uk>
Date:       2007-03-18 11:53:35
Message-ID: 200703181153.36473.lists () astrojar ! org ! uk
[Download RAW message or body]

On Sunday 18 March 2007 02:44:21 Christian Weilbach wrote:
> Am Mittwoch 13 September 2006 schrieb David Jarvie:
> > On Wednesday 13 September 2006  4:27, Allen Winter wrote:
> > > you are using QDateTimes.  Better change over to KDateTimes.
> > >   But we can probably address that later too.  We all have a lot of
> > > work changing over to KDateTime.
> >
> > There are not many date/time values in the kblog code, so it won't be a
> > big issue. But as Allen says, it would be better to future-proof your
> > code by using KDateTime rather than QDateTime for compatibility with
> > other parts of kdepimlibs and kdepim. I see that you are converting
> > date/time values to text for storage - you will need in that case to
> > allow for storing the time zone name alongside the date and time. The
> > time zone name is obtainable by KDateTime::timeZone()->name().
> >
> > A small note: QDateTime::currentDateTime() (and the equivalent KDateTime
> > methods) are static, so you don't need an instance to call it with.
>
> Why is KXmlRpcClient using QDateTime, by the way? Because KDateTime has no
> advantages and Xml-Rpc always uses UTC by default?

I don't know what KXmlRpcClient is about or what standards it has to adhere 
to, so I wasn't in a position to judge how to change it when I did the 
KDateTime conversion in kdepim. If you know what time zone it should use 
(perhaps UTC ??) then it would be a good idea to convert it to KDateTime.

-- 
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]