After evaluating what a number of technologies theoretically allowed us to do, we decided to further investigate Bryntum's library, as it was both specifically made with ExtJS in mind and incredibly powerful, with a host of features designed to cater for a wide array of requirements.
We first developed a “Demo” scheduler, in order to understand not only what could be done “on paper” but how we could perform certain operations and how it would have looked, helping ourselves with the great examples on their site in order to get up and running as fast as possible. This activity led us to understand that what we really needed was a “Scheduler” library, rather than a full-blown “Gantt” library. It also showed that Bryntum's technology was an exact match to our requirements and, in fact, all of them could be implemented with relative ease.
There are several reasons for this:
- Integrating into existing ExtJS pages, even though those pages might be complex with border layouts and complex panels and maps presented no problem for the library
- A massive amount of complexity related to timeline views we no longer had to worry about
- There is a huge number of options in the library that gave us great flexibility when working with GeoPal job data.
This new section, that we named “Planner”, has since then been released, many of our customers favour this solution and the technology behind it proved to be of very high quality. While it's inevitable that individual needs drive technological choices, Bryntum's is certainly suitable for a lot of purposes and it turned out to be the best choice to embed GeoPal Job Scheduling functionality on our system.
Our old Gantt section (Picture 1) was based on jQuery and developed several years ago. The developed functionality was perfect for the company objectives and the customers we had. Over time, with the technology improving and the company growing, it started to show its age and a number of features that we - as users - are now accustomed to expect from modern web applications were completely missing. Furthermore, users’ feedback over time revealed that while the tool was fine for certain scenarios it was far less useful for other ones.