Larry, thanks for your *hard work* on timeline...looking forward to testing this new feature out. Cheers!
On Thu, Oct 30, 2008 at 10:47 PM, LarryK <[EMAIL PROTECTED]> wrote: > > Turns out I spoke (and committed) a bit too soon. > > So if you're planning to use this capability, please wait...more sw on > the way. > > Thanks, > > Larry > > Details: > Turns out I was calculating the max tracks needed for the events shown > on the screen when the Timeline was initialized with the events. Need > to monitor the max tracks used when any of the bands' ethers are > moved. I'm working on an update. > > > On Oct 26, 3:57 pm, LarryK <[EMAIL PROTECTED]> wrote: > > Hi, > > > > If you're making a Timeline for a specific data set, it is no problem > > to figure out the size of the Timeline--just try different sizes to > > see what looks best. > > > > But if you want to automatically generate Timelines for data sets on > > the fly, figuring out the right size is more problematic. Too large > > and you have gobs of empty space. Too small and some events won't be > > visible. And the right size is dependent on the Timeline bands' > > resolution, plus how closely (in time), the events are in the data > > set. The necessary size also depends on the event labels since longer > > labels cause more overlaps which cause Timeline to use additional > > tracks to automatically avoid the overlaps. > > > > I worked on this today, and I think I have a good solution. The new > > autoWidth capability is optional and is NOT in use by default. Your > > additional tests, using your own data sets, band resolutions, etc, > > would be greatly appreciated. > > > > Currently you need to download the trunk version to try it. > > > > More details in the change file: > http://simile-widgets.googlecode.com/svn/timeline/trunk/CHANGES.txt > > > > I've added a new example to the source that demonstrates and tests the > > new feature: > http://simile-widgets.googlecode.com/svn/timeline/trunk/src/webapp/ex... > > > > Regards, > > > > Larry > > > > ps Details on the solution > > I did not add another pass through the event data. Instead, while the > > event data is being painted, I now keep track of the max number of > > tracks used at any one time (per band). When a client program calls > > timeline.autoSetWidths(), the max number of tracks, per band, is used > > to set the width of the bands. The new total (desired) width is then > > returned to the client. The client then enlarges the Timeline div and > > calls the layout method to make use of the new divs' new sizes. > > I modified all three event painters to track the max tracks needed. > > > > If the client wanted to resize the Timeline after changing the events > > being displayed (eg by filtering), it should hopefully work as > > expected. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
