On Mar 18, 2015, at 10:33 AM, Richard Hipp <d...@sqlite.org> wrote: > > Currently, of there is a line from the 289th entry up to > the 41st entry of the graph, that is a single entry in a table. But > with separate canvas, apparently that line now requires entries in 249 > different canvas definition tables? Either that, or somehow 249 > different canvas renderings need to somehow find out about that one > single entry in the global table.
I didn’t respond to this immediately because I wanted to think a bit about it first, so please excuse the second reply. I think the solution is for the Fossil web server to ship a JSON representation of its internal data structure as part of the web page. Then the JS canvas drawing code can iterate over that data structure when drawing its sub-graphs. Think MVC: you’re shipping the timeline model down to the client along with a copy of the view code that turns that model into pixels. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
