Support of dhtmlxSuite 3.6 and Old Browsers Can Be Stopped [Poll]

| Comments (10)

We want to inform you that we are planning to stop supporting the old versions of our dhtmlxSuite library. It concerns the versions 3.6 and lower, and IE6, IE7.

Here are the reasons of this decision:

  • 90% of appeared problems in 3.6 are already fixed in 4.x.
  • Technologies are developing fast, so we’re unable to provide proper support of 3.6 for new browsers, new devices, etc.
  • Necessity to support old browsers (IE6, IE7) thwarts the progress. Our components may obtain more cool and modern features but they hardly can be supported with old IE browsers.

DHTMLX Suite

We highly recommend those who still use old versions to update their library to the latest version. You may use our detailed migration guide. Moreover, if you have difficulties with migrating of your old skins to the new ones, then you can use new features in our Online Skin Builder that will help you to solve the possible problems with changes in skins starting from the version 4.0.

Now we’d like to hear your opinion about this. You’re welcome to take part in the poll here. If you don’t want to update, please share your reasons for it in the comment section below or write us on sales[at]dhtmlx.com.

Comments

  1. Matthew Waygood August 14, 2015 at 4:20 pm

    Will the help sections be updated for 4.4? If so can you also include which individual files are required. dhtmlx.js and dhtmlx.css are pretty hefty files to download, separate files would help speed up our site, as we only load what is required.

    • Ivan (DHTMLX team) September 7, 2015 at 1:28 pm

      Matthew, thanks you for your opinion. It’s actually not a problem to recompile dhtmlx.js and dhtmlx.css to make your custom build. You’re welcome to ask for a help in our forum or open a ticket (if you have active support subscription).

  2. Jack Prock August 17, 2015 at 5:25 am

    Your new 4.0 version made it so difficult to transition from the 3.x versions that we have been unable to utilize any new versions. It will take several months of effort to transition and the frustration with your company is really high.

    • Ivan (DHTMLX team) September 7, 2015 at 1:38 pm

      Jack, thanks for your opinion. You’re welcome to write us on support@dhtmlx.com. We’d like to get learn about your problems with migration and provide any possible solutions.

  3. Craig Chernos August 17, 2015 at 7:24 pm

    Although I wish we could transition quickly and easily from DHX v3.6, we’re a small shop and don’t have the staff or the time to do so and simultaneously keep up with our normal development workload. We have a number of v3.6 (and v4.1) applications which are stable.

    What we’ll probably do is what we’ve been doing right along: keep running/maintaining existing apps using their original DHX versions, and perform new development in the latest DHX versions.

  4. Mauro August 19, 2015 at 1:55 am

    i’just trying to update from 3.6 to 4 but i’ve problems with skins.
    i must use ie8 where the Gradient CSS is non correctly supported (you confirmed the problem). So all the applications lose their look with skyblue skin. Before abandon 3.6 version you must solve this problem.

    • Ivan (DHTMLX team) September 7, 2015 at 1:31 pm

      Mauro, thanks for your opinion. We suppose that the problems with skins can be resolved. Please provide us a demo with the specified problem to support@dhtmlx.com and we’ll try to find a solution.

  5. Tim Sanders August 25, 2015 at 10:45 pm

    We have been trying to transition from 3.x to version 4, but after weeks of work we’ve determined it will take months to transition all of our pages. This is very disappointing since our pages were stable with 3.x. Our staff is very frustrated because the API is not backwards-compatible. We have not been able to utilize version 4 features because the transition is so difficult.

    • Ivan (DHTMLX team) September 7, 2015 at 1:36 pm

      Tim, thank you for your opinion. We can’t be sure, but it seems that you’re using hidden methods of the library. It causes the difficulties with transition. all public methods are available in our documentation. But it would be better if we could check our guesses, please contact us at support@dhtmlx.com, we’ll try to find a solution.

  6. Ivan (DHTMLX team) September 7, 2015 at 1:48 pm

    Thank you all for your opinion and for taking a part in the poll. Surely, we’re not going to ignore your problems and will consider each case individually. Don’t hesitate to contact us (support@dhtmlx.com or sales@dhtmlx.com).

Leave a Reply