2016: How It Was. 2017: How It Will Be

| Comments (4)

Hello friends! 2016 was bright and remarkable year for our company and we want to summarize what has happened and what our plans are for 2017.

dhtmlxSuite

Our JavaScript library for creating enterprise web applications acquired modern Google-like look, new TreeView component, Font Awesome support and its own Form Builder tool. All these features were released as part of 5.0 Major Update, but we are already excited about future 6.0 that will bring us fully updated and responsive Form and Layout. More details will be published soon, and the start of first Beta tests is planned.

dhtmlxGantt

Accessibility support, performance improvements, updated critical path calculations and auto scheduling – that’s what 2016 and dhtmlxGantt developers brought us. But surely we won’t stop at this and have already started preparing a major 5.0 update with the features like inline editing in grid, configurable layouts, material design and more.

dhtmlxScheduler

A couple of years ago we achieved that point of dhtmlxScheduler development, when the calendar has everything you might need. That’s why 2016 was directed at support for existing functionality and some small fixes and improvements. Nevertheless, we are about to release 4.4 with Accessibility support and some other improvements. Besides, our team started working on Major 5.0 version that will give you a completely new experience of the event calendar you know.

2016-2017

What is more

2017 will begin with PHP and ASP.NET Platform Samples, new framework and some useful educational material in our blog. Don’t forget to follow us on Twitter, Facebook and Google+ to be the first to know what’s new.

And wishes. From all of us

Let 2017 bring you interesting projects, personal development and lots of joy. We hope you’ll share the most important events of the upcoming 365 days with us. See you next year!

new year

Comments

  1. Khalid January 14, 2017 at 3:29 am

    Great job.. we are always waiting for your new updates .. but you have announced that 2017 will begin with php and asp.net platforms.. what about java platform examples ?.. why not as early as php and asp.net ? When java new examples will be announced?
    Thank you

    • Maria (DHTMLX team) January 17, 2017 at 11:17 am

      Hi Khalid, thanks for your comment. In fact, we’ll share the common principles of working with DHTMLX and server-side platforms. So, based on the examples we’ll provide, you’ll be able to use our UI components with any server side including Java. Our choice of PHP and ASP.NET is based on the most common requests and use cases.

  2. Chris Saunders February 3, 2017 at 10:54 pm

    Thank you for sharing these exciting plans for the future!

    Can you provide a more granular timeline on the features you have outlined for Scheduler in 2017?

    “Nevertheless, we are about to release 4.4 with Accessibility support and some other improvements.” When would 4.4 be released? Also, what are “some other improvements”?

    • Aras Kairys (DHTMLX team) February 6, 2017 at 3:22 pm

      Hi Chris,
      > When would 4.4 be released?
      dhtmlxScheduler 4.4 was released on February 2, 2017. Please check this: https://dhtmlx.com/blog/scheduler-4-4-released-accessibility-support-minor-improvements/
      > what are “some other improvements”?
      There were quite a lot of minor things that make sense for specific use cases but too minor to include them in the release notes. E.g.
      public events for quick info extension http://docs.dhtmlx.com/scheduler/api__scheduler_onafterquickinfo_event.html
      http://docs.dhtmlx.com/scheduler/api__scheduler_onquickinfo_event.html
      small fixes in locale files, overall stability improvements (e.g. state scheduler after server errors via ajax), etc.
      > Can you provide a more granular timeline on the features you have outlined for Scheduler in 2017?
      Right now we’re working on major update/refactoring of Scheduler, the main goal of which is to structurize the inner API of the component and make it more maintainable and extendable, while keeping public API 100% backward compatible with the current version. There probably will be some new features added, but we are not ready to announce them at the moment.

Leave a Reply