> On 2/25/07, David Huynh <[EMAIL PROTECTED]> wrote: > > Gerrit Griebel wrote: > > Hello, > > > > I'd like to group different events into one track: > > > > 1248 01.01.2006-01.01.2007 > > 1248 01.01.2007-17.01.2007 > > 399 01.01.2005-17.01.2006 > > 399 01.01.2006-01.07.2006 > > 879 15.01.2006-01.01.2007 > > > > |---1248-------|--| > > |---399--------|-------| > > |-879--------| > > > If you want fine control on the layout of events, then for now, put them > into different event sources and feed each event source to a different > band. > > I've actually run into the same issue with my 'conference' example. There > are 2 conference tracks so I want to group the series of events associated > with a track. The tricky problem with creating a second band is that it > interacts with the 'summary band' in that you either have to create 2 > summaries as is done in the religion mashup or load 2 sets of events into > the summary. Unfortunately, loading 2 sets of events into summary ends up > laying out the summary differently than the overview. You also have 2 > sets of labels that have to be suppressed. Maybe there should be a > 'composite-band' class that can take sub-bands to group the events and > handle unified labeling and styles.
I should have noted that the data is collected by a database query. There may may be 50-100 tracks and each may consist of a few events. So it's not really feasible to create so many event sources. Ordering should be solely defined by the database query. So this would actually require two new features: (1) a way to disable automatic layout and (2) a way to group events into tracks in timeline xml. Gerrit _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
