I had seen that page but somehow didn't think it was working as I'd
expected. I've now updated my site and hopefully it's working (I've had 1
report saying it does 2 saying it doesn't but I think that was a
misunderstanding).
Thanks for your help

John

On Mon, Jun 15, 2009 at 8:16 AM, John McKerrell <[email protected]> wrote:

> Hi David
> Thanks for the links, I'll take a look. You should be able to experience
> the timeline by browsing one of the links I gave in my original email. You
> should be able to do that without logging in (if it does ask you to log in,
> please let me know!) Unfortunately, yes, to add your own data you need to
> log in.
>
> John
>
>
> On Fri, Jun 12, 2009 at 5:21 AM, David Huynh <[email protected]> wrote:
>
>>
>> John McKerrell wrote:
>> > Hi
>> >
>> > Just thought you might be interested to see an implementation of the
>> > Simile Timeline that I've recently done on my site http://mapme.at/
>> >
>> > The site allows you to store a location history through various
>> > methods, including integrations with Yahoo! Fire Eagle and Google
>> > Latitude. Previously we had a very simple drop-down allowing you to
>> > show history for any of the last 30 days for a user. With Simile
>> > Timeline we've been able to much improve this. The bottom band shows a
>> > summary of your history for the last 30 days, highlighting the days
>> > that you've had activity. The top band shows individual journeys and
>> > periods of inactivity. As you drag the timeline around more data is
>> > loaded. Here's a few examples, the first shows my location which I've
>> > restricted the accuracy of, the following two show timelines for users
>> > that show full accuracy:
>> >
>> > http://mapme.at/where/john
>> > http://mapme.at/where/thebox
>> > http://mapme.at/where/royaliris#/200905202037/6
>> >
>> > (the time interval to show in the top band is detected automatically
>> > depending on how active the user is, it probably still needs some
>> > tweaking)
>> >
>> > It's been an interesting widget to work with but I'm really happy with
>> > the result. I think there's still more that I can do with it but I'd
>> > be interested to hear your feedback and if you think there's things I
>> > could do better. One thing that I'm not sure about is timezones (and I
>> > think other people have had issues with that too). I'm creating JS
>> > date objects that appear to be correct, the source string is, for
>> > example, "2009/06/03 20:11:15 +0000". This creates a JS date object
>> > that returns, on my computer (in the UK), "Wed Jun 03 2009 21:11:15
>> > GMT+0100 (BST)". The timeline is showing the dates as GMT though. I
>> > did find one web page that suggested Simile Timeline would use the
>> > browser's timezone by default. I also noticed the timeZone option for
>> > band, I tried ((new Date()).getTimezoneOffset()/60) but that seemed to
>> > shift another hour in the wrong direction. Should I simply negate that
>> > or is there something else I should be doing?
>> >
>> > Anyway, great widget, thanks to all involved in putting it together.
>> > Hope you find my integration interesting.
>> John,
>>
>> That looks interesting! It'd be nice to get to experience its value-add
>> without having to sign up / sign in first.
>>
>> Regarding the time zone issue, there is a little test here
>>
>>
>> http://trunk.simile-widgets.org/timeline/examples/test_timezones/test_timezones.html
>> that might shed some lights on how Timeline parses date/time ISO8601
>> strings. There are some relevant discussions here
>>
>>
>> http://groups.google.com/group/simile-widgets/search?group=simile-widgets&q=test_timezones
>>
>> Hope that helps!
>>
>> David
>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
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