Mocking Ajax calls with Siesta
In the past couple of months we’ve received a few requests for mocking capabilities when it comes to Ajax requests with Siesta. We are actually quite interested in this feature ourself so we we’re very happy when we realized how easy it was to accomplish. The solution: Ext.ux.ajax.SimManager, is found in the Ext JS examples/ux folder.
Introducing the Ext.ux.ajax.SimManager
This class (docs here) has actually been around for …
describe(“Siesta 1.2.0 with BDD support”)
BDD, or Behavior Driven Development has been all the hype for a while now when it comes to JavaScript development. One of the most known JavaScript BDD test tools is Jasmine, and it does a great job of producing readable tests. We’ve received lots of feedback from the Siesta community to add support for writing BDD tests in Siesta. Since we’re getting close to releasing the 1.2 version of …
Using Ext Scheduler in Sencha Architect
We’ve been asked quite a lot how to use our components inside Sencha Architect. With the recent release of Sencha Architect 2.2, this is now very easy to solve. Please note that third party components still aren’t fully supported by Architect and they won’t render in the canvas (but it’s still very useful). If you’re in a rush and just want to see how this is done, you can see …
The 2.2 release is here
Today we’re happy to announce the new 2.2 release of Ext Scheduler and Ext Gantt. Both products have been upgraded to support Ext JS 4.2 (v4.2 GA is required). A lot of effort went into this release, to clean up and remove old Ext JS overrides, so supporting future versions of Ext JS will require much less work. You can also read about some of the internal changes for 2.2 …
Introducing UberGrid
Introduction
We’re proud to present the new UberGrid component – a grid with super powers for Sencha Touch! UberGrid aims to support as many grid features as possible while also providing excellent performance on a wide range of mobile devices.
The UberGrid is the latest member of our product family. It already serves as the base component for another of our products – the Touch …
Testing a Sencha Touch application
I recently joined Arthur Kay for an online webinar about writing tests for Sencha applications. As a follow up to the webinar, I thought we should really have a basic sample showing how to write application level tests with Siesta. Note that application tests are very different from unit tests, where you typically take one class and focus on testing its API. For an application test, we typically just …
Under the hood of the Socket.IO + Express example
You might have seen one of the sneak preview videos on YouTube about a collaborative demo app using our scheduler with Ext JS and Sencha Touch. With our recent release of the first 2.2 beta version of Ext Scheduler, it’s now time to look under the hood of this demo application. When we were about to release the Touch Scheduler, we thought we should really put it to the …
Road to Ext Scheduler 2.2: Upgrade guide
We just released the first 2.2 beta version in the CustomerZone. This release has quite a few changes due to some major refactorings mentioned in my previous post. To sum up, we adapted a lot of the code to be shared with our Sencha Touch version and we have also tried hard to eliminate as many private Ext JS overrides as possible. A few of the changes in this …
Road to Ext Scheduler v2.2: Overrides
We’re currently busy finalizing a major refactoring of our Ext Scheduler component which will be released as v2.2. There are two major reasons for this refactoring. First of all we needed to refactor to enable certain pieces of the core functionality to be shared with our Touch Scheduler. These bits of code relate to non-UI parts of the component, such as stores, models, utility classes etc. The second reason for …
Managing stores in a complex component
The Ext Gantt chart deals with a lot of observable data stores: Tasks, Dependencies, Assignments, Resources etc. A typical view component will observe its data stores and react to their changes. When building a view component that consumes data from one or more stores, it’s important to remember to de-register any store listeners in the Component destructor. If you don’t, you can end up with hard-to-trace errors after creating multiple …