I couldn't find this info anywhere. I know that D3.js v4 has a lot of v3 bugs fixed and the new modular approach is great, but I've got an existing application that has 4 (relatively complex) charts and I can't estimate how many working hours it would take to migrate from v3 to v4. Furthermore, now I'm working on a new map chart and it seems that v3 has already a good map support (then using D3.js v4 wouldn't be mandatory).
When asked about updating v3 examples to v4, Mike Bostock wrote:
Yep, I’m going to update my examples in-place. Consider it my
heavy-handed encouragement to upgrade to 4.0. (For one thing, there
are lot of 3.x bugs fixed in 4.0, and I have limited resources to
provide free support to old versions.)
However, the last v3 release (v3.5.17) on GitHub is recent, 4 May 2016. Therefore I still don't know exactly how long the v3 support will last.
Does anyone have this answer? Or, Mike, do you even have any idea of it?
D3.js v3 is no more supported. Mike answered me on Twitter:
I am not fixing bugs or developing new features in v3; my development efforts are solely focused on v4+.
From Mike Bostock on Twitter:
I am not fixing bugs or developing new features in v3; my development
efforts are solely focused on v4+.
Related
I'm searching for guidance on Bot Builder v3 SDK to v4 SDK migration.
Any conversion guide you can advise?
According to the product github a migration from V3 to V4 (documentation and samples) guide may be available by Feb.
Shall I wait for that?
Has anyone hear about any tool that will be doing the migration automatically?
Thx
Yes, there is a migration path planned where you'll be able to recompile with some level of source compatibility and that will then run on top of the V4 runtime... a bridge if you will. Ultimately to take full advantage of V4 features you need to really start fresh. I'm not aware of any tooling in the works that would help migrate from V3 style dialog code to V4, only the binary bridge and documentation.
I have developed bot application using Microsoft bot framework V4 preview(4.0.1 Preview)
Now i want to migrate to new stable version (4.0.8)
Can anyone tell me what are the breaking changes and how to fix those..
The downvotes are probably because this is a very broad question, as the framework went through some pretty significant changes from Preview to Stable. For example, if I'm not mistaken, what you call DialogContainer is probably ComponentDialog now. No one's going to be able to say what the breaking changes are, because they broke in different places for different bots, depending on the the bot's code. If you attempt to upgrade to 4.0.8 and run into errors, you can post those errors and get better assistance in solving each one.
I started to build a web application for HR Management and thought of applying Material Design concepts for interface. When I searched I found there are many frameworks for it such as
Angular Material
Materialize
Polymer
I want to select one of these material design frameworks for my project. There are couple of concerns I have about these frameworks.
What is the stability and the future maintainability of framework
How easy to customize the framework according to our new requirements and components
Do others use the framework
Which has most of the features
By considering above concerns can some one advice me what to use as the Material Design framework?
I will share my finding based on different criteria
Browser Compatibility
I) Materialize supports in all 3 browsers.
II) Polymer does not support in IE and safari
III) Angular Material its not mentioned clearly on the documentation.
Stability
I) Materialize Still under development but because it's just js and css
you will be able to keep up with it.
II) Polymer Still under development. Next versions can be entirely
different.
III) Angular Material Still under development. Next versions can be
entirely different.
Material look and feel
I) Materialize not pure material design.
II) Polymer pure material design.
III) Angular Material pure material design.
Features
I) Materialize feature less compared to other two.
II) Polymer feature rich.
III) Angular Material feature rich.
Future
I) Materialize not clear.
II) Polymer very clear because of google doing it.
III) Angular Material very clear because of google doing it.
Overall It's hard to say which is best. If not for the lack of support in IE (HR domain lots of people still use IE) my choice will be Polymer.If someone knows about Angular Material's browser compatibility please comment.
I will answer based on the concerns you have.
I don't know much about materialize, but by looking at their websites, I think I can relate it with other libraries.
I feel Polymer is much more stable than the other the other two as it is production ready with version 1.0. While the other two are still under development and their 1st version isn't even out yet.
Polymer and angular-material both are projects by google, so future maintainability will be proper. I am not so hopeful about materialize.
I have worked more on angular-material and it is much more customizable than the other two.
I don't have the statistics.
Angular-Material and polymer have much more features than materialize. Angular-material is based purely on material-design and has more material-design components than the other two. While polymer is composed of different API's (example:google API's) which can be implemented in your application very easily.
I would like to conclude by saying that if you want to use pure material-design then you should go for angular-material.
Newb here learning rails... any advice/comparison of community engine v. social stream? I'll be writing a dating site, so especially if either lends themselves to that development I'd appreciate the advice.
I have tried CommunityEngine in the old days. Currently to use it with rails3, you will have to use a specific branch mainly updated by the community to make it stable. i'm not sure if that rails3 branch is production ready yet.
I don't know community engine, but have been looking at social stream and it looks very well put together.
We upgraded social stream to a mobile platform by exposing api end points - it took a couple of months. We built separate controllers for each call rather than modifying the core classes. The platform is now flexible enough to cater for any use case and we can hook in to updates on the trunk. It's really well thought architecture and has had iterations of refactoring. (I think the webviews / javascript is a bit of a mess though)
I suggest you have a look at this - it took my tech lead a couple of weeks to be comfortable with this.
https://github.com/ging/social_stream/wiki/Social-Stream-Base-database-schema
WRT communityengine - I abandoned this over 4 years ago.
https://github.com/jdp-global/communityengine/commit/31f9b267706157a63bfc103a290bd6e3d874066a
Any platform you choose needs to have a focus on APIs / web services.
I was wondering, how often does DHTMLX offer a new version and how hard do you find it to upgrade your applications to the new version. This is namely a critical part in my research, but I cant seem to find any problems with updates. This question is just to make sure that my findings are correct.
Please suffice with: version number, DHTMLX component.
I work for DHTMLX. During the past 3 years we released one major update per year. Currently we're preparing the next version which we hope will be available in beta till the end of April 2012. We try to make the new releases backwards compatible and provide the upgrade path to the latest release (like here).
I've used many controls from the dhtmlxsuite in our app for the past 5 yrs. They are pretty good at making things backwards compatible, but not always. When going from v3 to v4 just a few months ago, there was quite a lot I had to do get my code back up and running. Also there dropped a few features that were supported in v3, this is not so good in my opinion. But overall, I really like the dhtmlx controls, they are an integral part of our product which now is used all over the world by thousands of users (http://www.ecosys.net/ecosys-epc/).