Thanks Larry, I think David did this for me in good Christmas spirit!
It was the Oregon Treaty entry. I'll rework it and see if I can make
it appear.

Thanks for the tips on the presentation. I need to just turn it on
live and let people know by email that its working and then they log
on and check it out. The perils of distributed projects with Christmas
deadlines. Now that it is working, people will be impressed with the
API timeline! Thanks.

Email me at [email protected] and I'll send you a copy of the
offending XML with the entry.

One small thing I noticed was at 1807 "Emmigration into the Flathead".
It displays following the duration bar and overlaps into the next
entry. I've tried to reduce the text to "Flathead" in thinking that it
was an issue of my reducing the text in the timeline div and the API
thinking that the text was longer. That did not work. It's a small
visual error, that I was going to ask about later.

Thanks for everyone's help and thanks for working on this API. It's
visually well done and the synchronizing of the bands is very cool.
Our Metis Timeline will be very educational for the sub-culture that
we research (mixed aboriginal/european sub-culture) in mostly Canada,
Northwestern USA.

Merry Christmas from Canada!

On Dec 24, 10:19 am, Larry Kluger <[email protected]> wrote:
> Hi James,
>
> I believe that the problem is in your xml file: one (or more) of the events 
> after 1831 is a problem.
>
> Suggested fix:
> Change your xml file.
> First delete all events after 1831. Run your html file and everything 
> (hopefully) will work perfectly.
>
> Then start adding back in the events. Add them gack half (of the remainder) 
> at a time: add half of the events that are after 1831. If everything still 
> works then you know the problem is in the last part of the xml file (the last 
> 25% or so of the file). If the file stops working, then you know that the 
> problem is somewhere in the set of events that you had just added back in.
>
> Use the technique to narrow down to the one or more events that are causing 
> the problem.
>
> I'd like to know what the actual event is that is causing the problem: I may 
> be able to make the Timeline more forgiving of the problem in the future.
> (Just having it crash is a bit boring.)
>
> In the worst, case: some tips about the demo:
> 1) YOU should control the computer
> 2) Just demo the parts of the Timeline that already work. It is already quite 
> impressive compared to nothing. Tell people that it is still in beta, that it 
> isn;t ready yet for wider use.
>
> Good luck!
>
> Regards,
>
> Larry
>
> ________________________________
> From: jameslove <[email protected]>
> To: SIMILE Widgets <[email protected]>
> Sent: Wednesday, December 24, 2008 12:48:30 PM
> Subject: Presenting today Need Quick Help: console' is undefined error
>
> Hi All,
> We've just got our British Columbia Metis (canadian aboriginal group)
> timeline completed with lots of data. I've got to show it today. Any
> thoughts on why suddenly getting this error in the API?  I've turned
> on only one band, since I thought that might be the issue.
>
> What happens is that when you slide the band towards the 1820's
> suddenly you get the error and the data disappears.  If you slide the
> band slower, it occurs further into the 1820's or 30's. If you close
> the error, the data suddenly reappears somewhere in the 1870's and you
> can slowly pan back until in the offending time period, the error
> occurs again.
>
> Line: 3794
> Error: 'console' is undefined
>
> http://www.bcmetis.ca/metis_timeline.php
>
> http://www.bcmetis.ca/metis_timeline.xml
>
> Thanks,
> James Love
> Associate Researcher
> University of British Columbia - OK campus
--~--~---------~--~----~------------~-------~--~----~
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