David:
I think we are, indeed, zeroing in on this request. Thank you. The
syntax you propose looks good. If we think of the base collection as a
parent class (the plan of record) and the related classes as a child class (
i.e. the set of milestones, the set of research efforts, etc) then it is
important to me to reference data within either the parent or the child when
constructing a bar containing the instances of a particular child. For
example, the date(s) probably come from the child, but the marker (color)
may, in some cases come from the parent and in some cases from the child.
Now, I keep an id reference to the parent in the child so I can probably do
this but I want to make sure that I can. I also want to be able to
construct the caption (the text associated with the bar or milestone). For
example I may want to concatinate the label of the parent and the child to
produce a caption for the child.
I have worked a bit with your mock up approach and it, indeed, provides a
partial solution. I have figured out how to get all 3 child cases on to 3
bars. What I can't figure out how to referece is the parent - the union is
of the all of the milestones, but doesn't contain the PORs so I can't refer
to them. I do understand, though, that this is a mockup. I think the unions
are also stressing the system a bit since the timeline comes up just fine
when originally loaded, but if I select a facet it blows up with a "Caught
exception: undefined .. Details: 'console' is undefined." Probably a bit of
a performance stress too, but again, I understand it is a mockup.
Thanks again, and please let me know if I can provide any more
information.
Charles
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
