Hi, We've been experimenting with Timeline as an interface for an electronic text edition of drafts and notebooks used by literary authors. In principle, we think it could be the basis for a very promising visualisation of search results on a time-based document collection.
However, a demo application with a data file containing over 3200 events proved fairly slow already (probably too slow for researchers to comfortably work with the timeline). Rather than its size (over 3 Mb), the Javascript-driven drawing of the sheer amount of events seems to be the bottleneck (deleting all events' text didn't improve performance). Since these sample data consist of only one fourth of the intended amount of data of the total edition, my question is: what would be the most sensible way to have Timeline deal with huge data collections? Is there a way to 'cut off' drawing of events to just the current visible 'time window'? Kind regards, Ron _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
