Mark,

Exhibit assumes ISO8601, so I'd recommend a full ISO8601 date/time, e.g.,
    2009-06-21T00:00:00Z
Note the Z at the end. If there's no Z, the parser assumes the browser's 
time zone, which obviously depends on the user's browser. (The timeline 
view by default, however, paints its date/time markers in UTC rather 
than in the user's browser's time zone).

David

mleden wrote:
> Thanks Larry for the reply.  Couple more clarifications below.
>
> My Timeline view is defined as follows:
> <!-- Timeline View -->
>                       <div
>                       ex:role="view"
>                       ex:label="Timeline Daily"
>                       ex:viewClass="Timeline"
>                       ex:topBandUnit="day"
>                       ex:bottomBandUnit="month"
>                       ex:topBandPixelsPerUnit="50"
>                       ex:bottomBandPixelsPerUnit="150"
>                       ex:start=".start"
>                       ex:end=".end"
>                       ex:colorKey=".group">
>                       </div>
>
> I don't see any references here or in any of the other Exhibit-related
> content that implies anything "timezone-related".  My assumption is
> that the widgets will assume UTC for the data while using browser
> locale for the Timeline glyphs that you mention.  Are those good
> assumptions?  That's how I arrived at the thought that there is a
> "timezone mismatch" between the data and the "representation".  Does
> that sound right to you?  So I'm expecting that there must be some way
> to offset one or the other to get them "in-sync".  One other detail
> that may or may not help is that I now realize that values in the
> format I mentioned earlier ("2009-06-21T00:00-08") render on the
> Timeline in IE 7.0 (but "misaligned") but *not* in FF 3.0 (nothing
> shows up).  To get them back to rendering (although "misaligned") on
> each browser, I am now formatting as "2009-06-21T00:00".
>
> Any other thoughts?
>
> Thanks again,
> -Mark
>
>
>
> On Mar 17, 10:48 am, Larry Kluger <[email protected]> wrote:
>   
>> Hmmm, two timezone issues in one day.
>>
>> Did you try using UTC tz in your data instead of -8?
>>
>> There are two different questions:
>> 1) What TZ is Exhibit/Timeline in. This determines "when" a date's mark is 
>> shown on the band.  Eg is "Start of Monday" at time 2009-06-21 00:00:00T00 
>> or 2009-06-21 00:00:00T-08
>> 2) What TZ is the data in once it is parsed by the Timeline library.
>>
>> Unless the two match, the data won't line up with the glyphs.
>>
>> Check that any settings for your Exhibit or Timeline use 0 as the tz. Eg in 
>> the create band parameters.
>>
>> Do all of your date/times come from the one data source?
>>
>> Hope this helped,
>>
>> Larry
>>
>> ________________________________
>> From: mleden <[email protected]>
>> To: SIMILE Widgets <[email protected]>
>> Sent: Tuesday, March 17, 2009 12:40:14 PM
>> Subject: Exhibit, timezones, and mySQL DATETIME
>>
>> Hi,
>>
>> I'm having some trouble understanding exactly what I need to do to
>> format date/time data to "represent itself correctly" using the local
>> timezone.
>>
>> Here's my setup:
>> 1. I have a mySQL instance that stores my data including two columns
>> defined as DATETIME
>> 2. I run a query to grab and format the data as a JSON file readable
>> by Exhibit
>> 3. I have a Timeline view that renders the JSON file including the two
>> columns defined as DATETIME
>>
>> Everything works fine EXCEPT that the values from the DATETIME columns
>> are not aligned with the begin and end ticks on the Timeline.  I
>> assume that this is to do with a "timezone mismatch".  I'm not doing
>> anything special with the DATETIME data during input in the database.
>> For example, the value of '2009-06-21 00:00:00' represents "the start"
>> of June 21st 2009.  From what I understand, without any further "data
>> transitions", Exhibit would assume this to be UTC.  Therefore, on
>> returning the value in the query noted earlier I have tried to
>> "transition the value" by using a mask with an offset (for Pacific
>> Time) on the mySQL DATETIME value to give me "2009-06-21T00:00-08" in
>> the JSON file.  However, this still renders "misaligned" in the
>> Timeline, as noted previously.
>>
>> Any thoughts on what I'm doing wrong?
>>
>> Appreciate any suggestions.
>>
>> -Mark
>>     
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to