Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Control over Nav Rows #547

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Conversation

rpeleg1970
Copy link

Hi,

I've added control over the number of rows, size, and how they are ordered. This helps build cases where you need to break events into more than 3 full / 6 half sized rows - which is currently hard coded. Here is a short summary of the changes:

  1. Fixed recursive merging of config object, allows setting properties under config.nav and below
  2. Remove hard coded calculations of row size and count
  3. Added support for pre-ordered tagged rows via tags node in JSON
  4. Fixed handling of secondsas intervals - one of my use cases was a sequence that lasts only 2 minutes
  5. Added example files (and tested the existing ones still work)
  6. Updated README file

*** IMPORTANT *** - I did not create a minified build as the fab build command does not work for me - I also opened an issue #546 for that. If you merge this branch you will also need to create a build (or better yet help my issue and command me to do it ;)

Hope you find this useful
Ron

ronp@winter added 5 commits December 26, 2013 11:04
… a minute or two, like a sports event or a malware attack sequence
… a Thu Dec 26 11:46:19 IST 2013 section puts this event in an annotated swimlane. however the swimlanes are arranged according to first-come. Adding a tags list (optional) allows to control the vertical arrangments of these lanes
1. Fixed recursive merging of config object, allows setting properties under config.nav and below
2. Remove hard coded calculations of row size and count
3. Added support for pre-ordered rows via  node in JSON
+ JSON timeout was 3 seconds. In some cases it casued the timeline to get stuck on load. Increased to 10 secs.
+ Fixed hard-coded position of event-line-indicator (blue line on timeline ruler, indicates start->end life of event)
@titpetric
Copy link

+1 for merge

@voz
Copy link

voz commented Jun 14, 2014

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants