Hi Jon, Thanks, your post is very helpful--I had not seen usage or explanation of all four date attributes previously. I'd like to add your Timeline to the examples in the source. -- Let me know if you wouldn't want that.
I agree with you about not removing any capabilities. I'm more trying to understand how to make use of the capabilities that are there. Regarding display of just a terminus ante quem: As a workaround, you can do that now, as you describe, by use of the new tapeImage and tapeRepeat attributes I added. Just create an image which starts on the left side as white and becomes darkest on the right side. Width depends on how far back in time you want the tape to extend to. Only issue that I can think of is that the label will be in the past, not at the terminus ante quem. But updating the original-painter.js file to shift the label to the right side of the tape for terminus ante quem events wouldn't be hard. Thanks again for a helpful post, Larry On Sep 19, 2:12 pm, Jon Crump <[EMAIL PROTECTED]> wrote: > On Wed, 17 Sep 2008, LarryK wrote: > > I vaguely remember reading a post that one of the features of 2.0 was > > that latestStart and earliestEnd were no longer needed? Maybe the idea > > is that instead of switching from using start to latestStart for an > > imprecise event, you can now continue to use start, but set isDuration > > to true. > > > But if that is the case, maybe it'd be clearer to rename isDuration to > > isImprecise (better isFuzzy)? > > (Of course, such a change would be implemented by adding the new > > attribute, the old attribute should always be available for backwards > > compatibility with older data sets.) > > > ==>> Is the above the current design idea? If so, we should change the > > docs to mark latestStart and earliestEnd as obsolete. > > I'm not exactly sure what's being suggested, but let me register my > opinion here in the strongest possible terms that latestStart and > earliestEnd are not obsolete. When David was originally planning the > development of timeline I offered the desideratum that timeline should be > able to represent dates and spans with terminusPostQuem and > terminusAnteQuem properties. David wisely chose latestStart and > earliestEnd instead, in order to implement a representation like this: > > http://home.myuw.net/jjcrump/Timelines/itinerary/earliest_latest.html > > in medieval or ancient history especially (but also true for any age) the > date of an event or some evidence may be uncertain, but can be narrowed > down to a date after which it MAY have occured (terminus post quem), a > date before which it MAY have occured (terminus ante quem), a date after > which it MUST have occured and and before which it MUST have occured. That > timeline offers this flexibility is one of its most attractive features. > > The second two examples are meant to show that a point date can > represented as 'fuzzy', ie, may have occured any time within the span > shown; as opposed to an event that spans a duration of time. > > One of the things I'd like to see in future development is the capacity to > represent terminus ante quem by itself. This might look something like > this: a point date with a tape that fades off into nothing in the past. > the length of that tape could be established by means of some kind of > fuzzy metric indicating degrees of uncertainty, ie 'at some time before > this date'. (days, months, years?, or perhaps a percentage of span of time > currently displayed). > > just my 2 cents, > Jon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
