Roadmap for Ext Gantt/Scheduler 6.0

It’s been about 15 months since our last major Ext Scheduler/Gantt release, so it’s time to start revealing the plans for our upcoming 6.0 release. Since the 5.0 release, we’ve received lots and lots of feedback, bug reports and feature requests – which we’re very thankful for. Please keep it coming so we know which features are important to you. Let’s dive into the details of our next major release!

Filtering Resources And Tasks In Ext Scheduler

Filtering is a critical feature in any data table or scheduler component where you want to work with large data sets efficiently. In our Scheduler component you would typically want to filter resources or their tasks but you can even filter the TimeAxis. To show how easy it is to filter your ResourceStore or EventStore, we built a small sample:

In this sample …

Siesta 4.4.0 Released With Headless Testing Support

Today we are pleased to announce the Siesta 4.4.0 release. This is a fully backward-compatible release which brings support for the newest versions of Chrome and Firefox, and contain some important features affecting the performance of your test suites. Below are the major highlights from the changelog.

Support for headless testing with WebDriver

Siesta now supports a new headless mode of the latest Chrome (>=60) and Firefox (>=57). To …

Adding A Powerful Gantt Chart To A SharePoint Site

In the recent months we have received multiple requests for a guide showing how to embed our components into a Microsoft SharePoint site. We are happy to announce that we have created a guide and a new example in the format of a Visual Studio Solution, showing how to create a basic SharePoint add-in for our Gantt component.

With this solution as a base you can deploy any …

Detecting Broken Promises With Siesta And RootCause

In modern web development Promises are very useful when dealing with asynchronous code flows to avoid “callback hell”. A “>Promise can be either resolved, pending (neither resolved/rejected) or rejected. When you are rejecting a promise, you need to have a catch method attached to it. See below:

Attaching this catch handler is very easy to forget however, and if forgotten an unhandledrejection event is …

Gantt + Scheduler 5.1.5 released

We are happy to announce the 5.1.5 release of our Ext Scheduler & Ext Gantt components. In this post we’ll outline the most notable changes.

Ext Scheduler 5.1.5 – Enchancements

The scheduling suite demo is our most advanced and fully featured demo, showing off the integration between our various UI components. This demo has now been restructured and simplified and it now also shows an Agenda view and a Year …

Bryntum Calendar 1.0 is available

We are excited to announce the release of Calendar 1.0. Since the first 0.9 version was released, we have added lots of functionality to create a flexible calendar suite which you can easily add to your web application. Let’s walk through the main changes in the 1.0 release.

New agenda and year views

Calendar now comes as a pre-configured Container with 5 different view modes: day, week, month, year and …

Welcoming Andrey Kozlov To The RootCause Team

Hello, everyone! I’m Andrey Kozlov, a full stack developer and I recently joined Bryntum to work on the RootCause product. In my past I’ve worked a great deal with javascript, and I’ve been using Ext JS since 2007.

In my past role as principal software developer, I’ve always seen a lot of value in logging javascript errors. Without a good monitoring system it’s just too …

Introducing RootCause – Next Generation Error Handling For Web Apps

A few weeks ago we did a soft launch of our new javascript error monitoring and debugging tool called RootCause. As web developers, we face bug reports with very varying quality and content. Sometimes we receive bug reports saying “Feature X doesn’t work” and other times we get a nice error message and call stack. The time it takes for a developer to fix a bug is proportional …

Debugging memory leaks in web applications using iframes

Many of our customers use popular third party javascript frameworks inside an iframe as a part of a larger application. Typically, each “sub-page” in this type of application is implemented in its own iframe that is part of the top HTML document. In most cases this works well, but in some cases it causes major memory leaks as iframes are added and removed repeatedly. We were recently asked to assist …