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

List:       kde-core-devel
Subject:    Re: Replacement for KDateTime
From:       John Layt <jlayt () kde ! org>
Date:       2015-08-04 23:38:40
Message-ID: CAM1DM6kLuRdSDgV+G0Q+OT=BCfg_WfOAJaxOzGWf0fB=+w+pPQ () mail ! gmail ! com
[Download RAW message or body]

On 2 August 2015 at 14:26, John Layt <john@layt.net> wrote:

> On 1 August 2015 at 19:47, Sandro Knau=C3=9F <bugs@sandroknauss.de> wrote=
:
>
> > * indivual timezone support, this is something that we need when parsin=
g
> ical
> > and have no known timezone information. I havn't looked into it, but I
> think
> > this can make it eventually into QDateTime.
>
> This is the real problem and the biggest stumbling block,and I'm sorry
> I haven't had the time to come up with a solution as promised.  I'll
> try sort it out in the next week or so. It was something I wanted in
> QTimeZone but it was far to complex to get in the first version., or
> indeed maybe ever. I need to see if there's a way we can derive our
> own support separate to Qt.
>

OK, I had a quick look at this and to do it in Qt and it wasn't actually
that hard. You can see the result at:

https://codereview.qt-project.org/#/c/122750/

This should support the full set of VTIMEZONE rules, have a look and let me
know if not.

I'm not sure if it will be ready for 5.6 feature freeze on Friday, or if
Thiago will approve of it, but clearly it's not going to be available when
KCalCore is released. I'm still thinking about work-arounds, but it's going
to be messy internally at the very least, and may not be do-able.

John.

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 2 August 2015 at \
14:26, John Layt <span dir="ltr">&lt;<a href="mailto:john@layt.net" \
target="_blank">john@layt.net</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 1 August 2015 at 19:47, Sandro Knauß \
&lt;<a href="mailto:bugs@sandroknauss.de">bugs@sandroknauss.de</a>&gt; wrote:<br> \
<br> &gt; * indivual timezone support, this is something that we need when parsing \
ical<br> &gt; and have no known timezone information. I havn&#39;t looked into it, \
but I think<br> &gt; this can make it eventually into QDateTime.<br>
<br>
</span>This is the real problem and the biggest stumbling block,and I&#39;m sorry<br>
I haven&#39;t had the time to come up with a solution as promised.   I&#39;ll<br>
try sort it out in the next week or so. It was something I wanted in<br>
QTimeZone but it was far to complex to get in the first version., or<br>
indeed maybe ever. I need to see if there&#39;s a way we can derive our<br>
own support separate to Qt.<br></blockquote><div><br></div><div>OK, I had a quick \
look at this and to do it in Qt and it wasn&#39;t actually that hard. You can see the \
result at:<br><br><a \
href="https://codereview.qt-project.org/#/c/122750/">https://codereview.qt-project.org/#/c/122750/</a><br><br></div><div>This \
should support the full set of VTIMEZONE rules, have a look and let me know if \
not.<br><br></div><div>I&#39;m not sure if it will be ready for 5.6 feature freeze on \
Friday, or if Thiago will approve of it, but clearly it&#39;s not going to be \
available when KCalCore is released. I&#39;m still thinking about work-arounds, but \
it&#39;s going to be messy internally at the very least, and may not be \
do-able.<br><br></div><div>John.<br><br></div></div></div></div>



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