Anyone has compared SIMILE Widgets Timeline with https://github.com/VeriteCo/Timeline?
I'd like to know the pros and cons between them. Which JS codes are better designed?

Comments

xamanu’s picture

Title: Is https://github.com/VeriteCo/Timeline a better choice? » Support for Timeline JS libs
Status: Active » Postponed

There are other interesting libs out there (#1192830: Support Timeglider libraries). The approach would be first to have a #1192828: plugable library support and then we could start using different libs.

shenzhuxi’s picture

I spent the weekend to check the module and different JS timeline tools, and found that VeriteCo/Timeline support both HTML and JSON. That can reduce the codes greatly.
It's definitely the better choice than SIMILE Widgets Timeline.

bjalford’s picture

Has anyone been able to get VeriteCo/Timeline working with Timeline module?

boabjohn’s picture

Ready to add some modest bounty on this one for an output that includes:
1. integration with VeriteCo's timeline.js
2. a Views display type [timeline] so that data can be driven through Views

SteffenR’s picture

Hi i tried to port the timeline module to work with VeriteCo's timeline.js
@xamanu
Maybe we should follow your effort and integrate it by using a pluggable library.

I just uploaded the module to github - it's in an early "stage" - working with image-assets already (Screenshot)

For Full-Support of all media-assets (flickr, youtube, vimeo etc) we should think of an easy to use GUI. A normal text-field would work in these cases - anyone better ideas ?

Here you find and early verion of the module: https://github.com/steffenr/timelinejs-drupal

SteffenR

boabjohn’s picture

@SteffenR : my confusion...what are you seeing is the value of a GUI to handle remote media-assets directly in this module? What is the "simple text field" for in your vision? Pasting an embed code or permalink in?
My instinct is this: those assets should be "hooked" into the Drupal website using the full power of the remote service API, whatever that might happen to be.
Since these APIs are all different, and since there's already a very mature process in the Media module ecosystem, surely there's no need to spend time developing new GUI here?
Instead, think of the advantage of using this module to bridge between timeline.js and Views, and hooking CTools in the process...then we get an enormous boost off these very sophisticated and highly utilised Drupal contribs.
Does that make sense or were you on another path entirely?

SteffenR’s picture

You are right - we don't have to care about a GUI or sth. like that - the Media file selector would be a "best fit" ;)
In the JSON structure of timelinejs a media asset is provided this way:

"asset":
  {
    "media":"http://youtu.be/u4XpeU9erbg",
    "credit":"my credit line",
    "caption":"my caption"
}

TimelineJs handles the media pathes automatically (supplies a player etc.) and has build-in support for several media providers..
So we could definitly use already existing widgets to select media and provide the corresponding pathes for the media assets used by timelinejs..
My first approach was just to test the abilities how to integrate a media-field with timelinejs as a views-plugin.

juhaniemi’s picture

@SteffenR: I wrote a very similar TimelineJS Views display plugin module a few weeks ago, but didn't have time to publish it until today. Should join forces or something? :) We have slightly different architecture, but I think we're both kinda at the same development phase.

http://drupal.org/sandbox/juhaniemi/1795500

SteffenR’s picture

Great idea - i'll have a look on your sandbox tomorrow or on weekend. Maybe an approach using a ctools plugin would be more generic - but i have to digg deeper into writing own ctools plugins. As already mentioned in this issue this would be a better way to implement timelinejs also, cause lot of the code used in the module would be duplicated.
@juhaniemi: have you tried writing own ctools plugins already ?
What do you think of this approach ?

SteffenR