areski
commented
11 years ago Yes keeping our code up to date should definitely be in the plans.
This is an open project so you are welcome to fork and also send patches / pull request. https://help.github.com/articles/using-pull-requests so join us and help us make this better :)
I don't think django-nvd3 needs to be updated much but python-nvd3 will require some work to use v3.
On Tue, Aug 20, 2013 at 3:02 PM, Stefano Crosta notifications@github.comwrote:
NVD3 major development branch, including usage of the new D3.V3, has been recently merged in master with a beta status.
Any plan to move to the new version? I'm not yet sure myself what are the compatibilities issues, but before making a fork and trying out I wanted to know if you are already working on it (this is a shared issue with python-nvd3 I guess)
— Reply to this email directly or view it on GitHubhttps://github.com/areski/django-nvd3/issues/10 .
Kind regards, /Areski
Arezqui Belaid, areski@gmail.com Founder at Star2Billing (www.star2billing.com)
Tel: +34650784355 Twitter: http://twitter.com/areskib LinkedIn: http://www.linkedin.com/in/areski
stefanocrosta
NVD3 major development branch, including usage of the new D3.V3, has been recently merged in master with a beta status.
Any plan to move to the new version? I'm not yet sure myself what are the compatibilities issues, but before making a fork and trying out I wanted to know if you are already working on it (this is a shared issue with python-nvd3 I guess)