vis.js

We have been very busy fixing a lot of the open Github issues over the last week. We have also received multiple pull requests that could be added quickly! Special thanks to our community members contributing this release: @klmdb, @pavlos256, @T-rav, @brendon1982. Since this is a release with new features, we push the version number up to 3.9.0. Next up: big refactoring and version 4.0.0!

Changelog:

Network

• Reverted change in image class, fixed bug #552
• Improved the fontFill offset between different browsers. #365
• Fixed dashed lines on firefox on Unix systems
• Altered the Manipulation Mixin to be succesfully destroyed from memory when calling destroy();
• Improved drawing of arrowheads on smooth curves. #349
• Caught case where click originated on external DOM element and drag progressed to vis.
• Added label stroke support to Nodes, Edges & Groups as per-object or global settings. Thank you @klmdb!
• Reverted patch that made nodes return to 'default' setting if no group was assigned to fix issue #561. The correct way to 'remove' a group from a node is to assign it a different one.
• Made the node/edge selected by the popup system the same as selected by the click-to-select system. Thank you @pavlos256!
• Improved edit edge control nodes positions, altered style a little.
• Fixed issue #564 by resetting state to initial when no callback is performed in the return function.
• Added condition to Repulsion similar to BarnesHut to ensure nodes do not overlap.
• Added labelAlignment option to edges. Thanks @T-rav!
• Close active sessions in dataManipulation when calling setData().

Timeline

• Added byUser flag to options of the rangechange and rangechanged event.

I initially wanted to do a small recap of vis.js so far but it became larger (and more off topic) than I expected. To understand some of the motivations for our roadmap, take a look at the post below this one first.

So now for our plans for 2015! We have added a lot of features over the last year, and we have to be careful that vis does not die of option-obesity. To mediate this we thought of a few solutions. Firstly, we will make the docs collapsible using a similar system to Jos′s great online JSON editor. This is naturally a temporary fix but the docs are one of the most important ways to get information. We think we ourselves may be the most frequent visitor of those pages so it's a good start!

Secondly, the actual changes, we plan to reorganize some of the option structure. This will unfortunately (but by definition) be a breaking change from our old versions. The new structure will be clearer and more intuitive. The work our current users will have to do to update will be minimal. If you're using the options we reorganize, you'll have to update your options. Breaking releases are always a shame, but we feel it is necessary.

The third step we want to take is to go over the code of each module and modularize everything much more. This will make the code easier to maintain as we move away from very large .js files, as well as make it easier to expand on.

Once everything is modularized, we want to change the API to allow users to plug their own parts of vis together. As an example: You start a network module, plug in the type of node module, edge module, physics module and optionally navigation module (etc.) and you're good to go! All of these modules will be individually configured. This means the huge list of options will be segmented into smaller, more manageable parts. Additionally, the docs will become smaller and clearer.

Of course, we do not want to abandon all our plug-and-play functionality! We will also start to supply more preconfigured constructors (i.e. a vis.BarChart that will give you a preconfigured graph2d module). Apart from these constructors we will continue to publish examples which will include code snippets that you can use in your own project.

Once this has been completed, we expect there will be more options that accept functions as arguments which gives you more control over vis. Finally, because everything (well, more than now) would be split up into modules, it becomes easier for the community to create additional modules, further improving vis!

The things I have listed here are the ideas that we have now. This is subject to change. We also cannot provide a timeline for this because we work on vis whenever we have time. No deadlines, no constrains, just when we have time.

To wrap up, there are a few things I did not mention here but I'd like to add to the post anyway.

• We want to improve the fusion of graph2d and the timeline, with the ideal that a graph2d can be used like a group in timeline now.
• Examples will be split in simple option/configuration examples and larger, feature demonstration/exploration examples.
• Graph2d will be expanded.
• We will move to hammer.js 2.0.
• We will add features from the list when we can
• We hope to keep up the cation with our community!

Let's make 2015 as good as last year!

In April 2013, the initial commit was made for vis.js by Jos because the old CHAP LINKS library was becoming too large to expand and maintain. Vis.js was a clean, new start using all the knowledge gathered from the CHAP library with the ideal that the new infrastructure would be more stable, faster and easier to maintain.

In January 2014, I joined the project and started to expand the Network module, which was called Graph back then. I have been working alongside Jos since then we have poured a lot of hours into vis.

On the 16th of April 2014, exactly a year after the initial commit, a twitterbot with a lot of followers notified the world that we were featured on hackernews! This was the boost we needed to really reach a large community. We saw the amount of visitors and Github stars increase greatly over the months that followed.

The 14th of October, we have altered the license of vis.js to MIT or APACHE 2.0. This allowed Tiddlywiki to add vis.js to their keychain. From what we hear, their developers really enjoy working with vis and we look forward to hearing how their community uses our software!

Now, we have a great community that helps out in issues, fixes our typos in the docs, notifies us of bugs and sometimes fixes them for us. We have received pull requests with new features and improvements and it has been fantastic!

This post started out as the roadmap for vis in 2015, but the review was longer than I initially expected thereby deserving its own post.

Have fun using vis!

The old website served us well, but now that we arrived in 2015... it is really time for an upgrade! We hope the new website is more informative, modern and a good promotion for vis.js! It also allows us to keep the community updated through this blog and to show off great projects that make use of vis.js in our showcase.

If you have made something and would like it featured, please make an issue on Github with your project and how you'd like to be credited.

The new website is in beta so if anyone spots a typo or other mistake, please let us know on our Github page.

There is no forum on this website. We prefer to keep all the communication with the community through Github. We believe this is the best solution so everyone only has to check the Github issues when there is a problem or suggestion.

A big change introduced with our new website, is the feature request page. There are a lot of issues on Github that suggest features but we do not always have time to implement these ourselves. On the other hand, there have been issues where people tell us they want to contribute but are now sure where to start. To mediate this (and to make a clear overview for ourselves) we listed everything here.

Once a feature is added to the list, it is not the end of the line. At each new release, we'll look at the list and see which features we may want to pick up for the next one. Discussions on these features can still continue on the referenced Github issues. When we have added a feature to this list, we will close the Github issue that requested it to keep our open issues more of a bug-todo list. The main motivation for this is because we have noticed that old bugs (on pages after 2) would be overlooked from time to time.

This feature page is an experiment. If it turns out that the community does not like us closing issues with open feature requests or if it does not have the impact we'd like it to have, we'll revert back to the old model.

We thank you all for using vis! Last year has seen a great increase in our user base and it is a great motivating factor knowing that our work is used by others!

Here's to a great 2015!

We're proud to present a new version of the vis.js library: 3.8.0! This release has a lot of new features and bugfixes, nearly all of which were suggested and/or discovered by our community on Github. A lot of the issues on Github have been handled in this release and it is likely to be the last release before 4.0.0. The 4.0.0 release will break compatibility with old code (only options will be revisited on the API side) but more on that in the roadmap post.

Changelog:

Network

• Fixed flipping of hierarchical network on update when using RL and DU.
• Added zoomExtentOnStabilize option to network.
• Improved destroy function, added them to the examples.
• Nodes now have bounding boxes that are used for zoomExtent.
• Made physics more stable (albeit a little slower).
• Added a check so only one 'activator' overlay is created on clickToUse.
• Made global color options for edges overrule the inheritColors.
• Improved cleaning up of the physics configuration on destroy and in options.
• Made nodes who lost their group revert back to default color.
• Changed group behaviour, groups now extend the options, not replace. This allows partial defines of color.
• Fixed bug where box shaped nodes did not use hover color.
• Fixed Locales docs.
• When hovering over a node that does not have a title, the title of one of the connected edges that HAS a title is no longer shown.
• Fixed error in repulsion physics model.
• Improved physics handling for smoother network simulation.
• Fixed infinite loop when an image can not be found and no brokenImage is provided.
• Added getBoundingBox method.
• Community fix for SVG images in IE11, thanks @dponch!
• Fixed repeating stabilized event when the network is already stabilized.
• Added circularImages, thanks for the contribution @brendon1982!

Graph2d

• Fixed round-off errors of zero on the y-axis.
• added show major/minor lines options to dataAxis.
• Fixed adapting to width and height changes.
• Added a check so only one 'activator' overlay is created on clickToUse.
• DataAxis width option now draws correctly.

Timeline

• Implemented support for styling of the vertical grid.
• Support for custom date formatting of the labels on the time axis.
• added show major/minor lines options to timeline.
• Added a check so only one 'activator' overlay is created on clickToUse.

Graph3d

• Fixed mouse coordinates for tooltips.