Skip to content
jducoeur edited this page Jul 2, 2013 · 2 revisions

Use Case: Timeline

Aaron suggests that it would really rock to be able to use Timeline.js as a UI; that makes sense.

I believe this would be a Mixin -- it's a feature of a Space or App, not the entire thing. You add the Timeline Mixin, and specify a bunch of things: the Model(s) that are feeding the Timeline, the Date properties to drive it, the fields for the texts and images and the like, and so on. Fill in your data, and you automagically get to view it as a Timeline by going to the right page within your space.

Analysis

This is probably a good earlyish test of Mixins. It doesn't sound too hard to implement, and provides excellent bang for the buck.

Timeline.js apparently has a JSON interface, which is presumably how we should work with it. Be smart about this, and use it as an excuse to expose a more general Querki JSON interface. (Which is likely extremely useful in its own right, and likely pretty easy.) The Timeline documentation can be found here -- it looks fairly easy for us to implement.

There are probably some security defaults to think about here. Typically, the Timeline is going to want to be Public-Read, but the underlying data isn't. Do we want the Mixin to offer to set the security defaults? Is this even remotely a good idea, that Mixins could do that? Think about it.

Clone this wiki locally