ExtJS Store and Cannot read property ‘buffered’ of undefined


Sencha’s ExtJS does a great job in general of giving you friendly error codes when you are building Single Page JavaScript applications.  One error however I seem to always get and to me it simply means “Oh, you forgot to include the store definition” is simply “Cannot read property 'buffered' of undefined” It sure would be nice if this error just said that. :) … Continue Reading

Showing The Record Count in a Sencha ExtJS Grid Made Simple


I use Sencha’s ExtJS for lot’s of data maintenance type applications.  One such application is an email response manager where it’s convenient to know how many different URL’s got clicked.  Basically, how many rows in the gridview.  Certainly, counting is an option but showing it in the title makes a lot more sense. The tip here is that often you have to call store.load() on the store associated with a grid so with just a couple extra lines you can put the count in the title of that grid.  Those extra lines are basically just a callback to the store.load that then grabs a reference to the gridview.  In my case, I have a button on my toolbar (just above the gridview), and in the button’s handler I execute the … Continue Reading

Add a Data Driven Combobox to ExtJS Form


I’ve been enhancing the session editor for AngularU  (Written in ExtJS 4.2)  and I’ve recently had to add a couple data driven comboboxes.  One to specify which track the session is in and one to assign which track the session is in.  Having done it a couple times in a row, my muscle memory is pretty good so I thought I’d do it again but this time on my blog. This is what the result looks like: The basics of the relationship between the table data is that we have a Session Table and a Track Table as follows: For the sake of the controls, we actually have two rest feeds.  One Track and one Session.  You can see them both here: http://angularu.com/rest/track http://angularu.com/rest/session The track … Continue Reading

Synchronizing Sencha Architect and Sencha’s CMD Compiler


Phil Strong has an excellent article on how to update an existing Sencha Architect (SA) project so that it will work with Sencha’s CMD compiler.  Basically, the problem is that SA and CMD do not agree on where the app.js should be by default.  This article will give you a recipe to do a file/save as from SA and then turn that new directory with the SA project into a place where you can, from the command prompt say: “sencha app build production” or “sencha app build testing” to generate a completely optimized version of your web app for deployment. For those that don’t know what either is, Sencha Architect is an awesome tool that Sencha started working on literally 4 years ago and finally released about a year ago.  It’s a beautiful tool … Continue Reading


Get every new post delivered to your Inbox

Join other followers: