TimelineJS3 comes with a lot of new features. Not all of them have been implemented in the module yet. If you would like for a field or an option to be added to the module's 8.x-3.x and 7.x-3.x branch, you can request it here. The primary reason why I haven't already included these fields and options in the module is simple: the settings form is pretty long as it is. If there's no interest in a particular field or option, then I don't want to make things more confusing for site builders. This issue is where you can inform us that you DO have interest in them.

Unimplemented Fields

  • slide: autolink
  • date: millisecond

I know there's a thread already open for adding a thumbnail field, but I think I'll close that since it's for the 1.x branch. The only field in the list that wouldn't be easy to implement is the millisecond field. The others are already included as object properties in the new PHP library. They just need to have the integration written, which thanks to the library is mostly copying, pasting, and editing text.

Unimplemented options

  • default_bg_color
  • initial_zoom
  • zoom_sequence
  • optimal_tick_width
  • base_class
  • marker_height_min
  • marker_width_min
  • marker_padding
  • menubar_height
  • use_bc (this option may not have been implemented properly in TimelineJS)
  • duration
  • ease
  • dragging
  • trackResize
  • slide_padding_lr
  • slide_default_fade
  • ga_property_id
  • track_events

That's not a comprehensive list. There were a few options that either didn't seem to be relevant or their functions weren't obvious from their names and they weren't documented. Some of these options would be very useful for sites to have and I don't mind adding them. Again, I decided to hold off until someone requests them.

Comments

dcam created an issue. See original summary.

dcam’s picture

dcam CreditAttribution: dcam commented
Issue summary: View changes

FYI, this thread is for either the 8.x-3.x or the 7.x-3.x branches. Any new feature will be added to both.

mariagwyn’s picture

mariagwyn CreditAttribution: mariagwyn commented

For what it is worth, I vote for all the things. Mostly b/c at some point, I will probably want some option I don't have now. Also, ideally, it would be great to have settings PER VIEW rather than global. I am slowly building out a site that I hope to contain a variety of timelines and may want different functionality per timeline. If that is just pie in the sky, no problem.

mariagwyn’s picture

mariagwyn CreditAttribution: mariagwyn commented

So, since "all the things" might be a bit much, here is my current priority list:

  • background: color
  • timenav_position
  • All timenav_height related settings
  • use_bc
dcam’s picture

dcam CreditAttribution: dcam commented

@mariagwyn
Thanks for letting me know. For the record, the thumbnail field is also going to be a target for beta2. As I got into playing with the different media types more I realized that I needed to do something other than copying the media value into the thumbnail value. While it doesn't seem to do any harm, having blockquotes in the thumbnail value probably isn't the best behavior.

mariagwyn’s picture

mariagwyn CreditAttribution: mariagwyn commented

Can you take advantage of various image styles in the thumbnail?

dcam’s picture

dcam CreditAttribution: dcam commented

No reason you wouldn't be able to use styles that I know of. I'll set it up just like the media and background image handling.

  • dcam committed 54a1111 on 7.x-3.x 
    Issue #2752241: Added the background color field mapping option.
  • dcam committed 985c9b8 on 7.x-3.x
    Issue #2752241: Added the media thumbnail field mapping option.

  • dcam committed 7e7735d on 8.x-3.x 
    Issue #2752241: Added the media thumbnail field mapping option.
  • dcam committed e18520c on 8.x-3.x
    Issue #2752241: Added the background color field mapping option.
mariagwyn’s picture

mariagwyn CreditAttribution: mariagwyn commented

In case you want some positive affirmation (sorry it took so long to come back and test):

Background color: works. I haven't tested the thumb.

dcam’s picture

dcam CreditAttribution: dcam commented

Cool, thank you again for testing. I'm hoping to finish adding the other options sometime tonight. That way I can finally get beta3 released.

dcam’s picture

dcam CreditAttribution: dcam commented
Issue summary: View changes

I spent a few hours working on the use_bc option yesterday, but didn't get anywhere. There are two problems:

1. I don't think it's compatible with the way that the integration library currently works. The timeline will display dates in the same format as they are output from Views. This gives site builders the flexibility to use date formats other than the one that TimelineJS displays them in by default. Unfortunately, I think that will prevent TimelineJS from manipulating dates the way it has to in order to display "BC/BCE" instead of a negative year value.

2. The MUCH bigger problem is that the use_bc option doesn't seem to do anything at all! When I overrode the problem in #1 to get TimelineJS's date format, the option didn't seem to do anything. In fact, when I search the TimelineJS library that option doesn't get used anywhere at all. So I think they failed to implement it anywhere. It's not clear from the tiny bit of documentation exactly what it's supposed to do anyway, possibly because it does nothing!

  • dcam committed 9691628 on 8.x-3.x 
    Issue #2752241: Added the timenav position and various height options.

  • dcam committed 0a43689 on 7.x-3.x 
    Issue #2752241: Added the timenav position and various height options.
dcam’s picture

dcam CreditAttribution: dcam commented
Issue summary: View changes

The timeline navigation position and height options have been added.

dcam’s picture

dcam CreditAttribution: dcam commented

I opened a GitHub issue about the use_bc option and a documentation issue with the timenav_height_* settings, https://github.com/NUKnightLab/TimelineJS3/issues/393.

dcam’s picture

dcam CreditAttribution: dcam commented

If someone requests that the zoom settings be implemented, see the related child issue. The reporter tested adding them and says that they may be bugged.

RAWDESK’s picture

RAWDESK CreditAttribution: RAWDESK for Colruyt Group Services commented

Subscribing #17 for the initial zoom setting, which was requested by my client but not yet implemented.

dcam’s picture

dcam CreditAttribution: dcam commented

Does your client also need the zoom_sequence? The initial_zoom does nothing without it. Also, the scale_factor is an initial zoom that doesn't require the sequence. So if they don't need the sequence, which according to reports is bugged, then just use the scale_factor.

RAWDESK’s picture

RAWDESK CreditAttribution: RAWDESK for Colruyt Group Services commented

Hi, the scale factor has no effect. Tried both 1 and 7 scale on a timeline with 3 events spread over 3 years and it initially zoomed identical
First event is visible, starting on the timeline somewhere in the middle but not indicating the 2 other events.
The zoom- button was twice clickable, then showed all 3 events.

dcam’s picture

dcam CreditAttribution: dcam commented

The scale_factor does work. Smaller numbers show a greater span of time (zooms out). From your description of what you're experiencing, it sounds like you need a fractional scale factor. I can add 0.5 and 0.25 scale as options for you.

dcam’s picture

dcam CreditAttribution: dcam commented

I've added the fraction options to the 7.x-3.x-dev and 8.x-3.x-dev branches.

RAWDESK’s picture

RAWDESK CreditAttribution: RAWDESK for Colruyt Group Services commented

Hi, thanks for your efforts!
Could you provide me the necessary patch, so we can apply it here also ?

dcam’s picture

dcam CreditAttribution: dcam commented

@RAWDESK - It's available for download on the module landing page.