Difference between angularjs-nvd3 directives vs angular -nvd3

I need some kind of hint or something else. I use BI tools with new technologies, and I'm really interested in them, even participating in one of these projects. However, I would like to know the a priori pros and cons

References

https://github.com/angularjs-nvd3-directives/angularjs-nvd3-directives

https://github.com/krispo/angular-nvd3

thanks

+7
javascript angularjs-directive angularjs-nvd3-directives
source share
3 answers

I came across the same question, and I thought that I would share my thoughts. I will go from https://github.com/krispo/angular-nvd3 . To date, the most recent push on github was 15 days ago. Another choice was not carried over to 8 months. In addition, angular -nvd3 has great examples and additional documentation. As Vincent said, they both use nvd3 as an engine, so you are likely to get the same amount of performance. But for ease of use, I will give recently updated and many examples.

+4
source share

I studied the same two. Both seem promising and affordable.

My preferences: Angular -nvD3 - more control;

The mechanism for constructing diagrams is the same (nvd3).

angular -nvD3:

  • full range of diagrams - same as nvd3
  • Just a shell around nvd3
  • you will do most of your work in java (off-screen)
  • In the interface that works with a single nvd3 directive, and in the backend, you configure complex “options” and “data”.

nvD3-directvies:

  • wider but smaller range of charts (check websites)
  • More declarative: the range of nvd3 directives (one for each diagram); options are declared as attributes
  • more natural for binding to individual model variables

I can update this answer when I find out more.

+3
source share

With angular-nvd3 directives, since many configuration parameters are attributes, this can be a bit slower, since angular will keep track of any changes in any of the directive's attributes. Another argument is that the directives file is larger (un-minified 115kb).

I prefer "angular -nvd3" because json options can be created as a service and are configured and accessible much faster. Also, working in angular-highcharts is the best way to have a chart directive. It is also smaller (u-nminified 29.1kb)

+1
source share

All Articles