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

Why Am I So Excited About AngularU?


    What is Angular? If you work in the web development space, unless you have been hiding under a rock for the past couple years, you must know what Angular is.  If not, let me tell you.  Basically, it’s a   JavaScript toolset that allows you to build single page web apps (SPA’s) efficiently, while at the same time deliver great user experiences and programmer development experiences.  What I mean by this is that Angular just feels good to program in.  It does not make you feel like you are using something artificial to build your web sites that transpose some cryptic language into the web, but it makes you feel like you are talking the web’s language. In addition, Angular has a huge number of … Continue Reading

Routing and State (The AngularJS Discussions)

I’m a big fan of the Adventures in Angular podcasts.  At a recent podcast that happened at ng-conf in Salt Lake City, there was a lively discussion around the topic of routing and URL’s.  Specifically, one side of the discussion was that a URL defines a state of an application.  The other side said that is not true. Personally, I think it’s ridiculous to think that a URL can define that state of applications.  My first proof is that there is a huge amount of discussion around it.  If it was clear and true, there would not need to be discussions about it. I believe that URL’s are simply pointers to places in web sites.  That’s it.  Any more than will breed confusion.  The most trivial example is that … Continue Reading

Refactoring C# Code With ReSharper Help


  A pattern that I do quite often is to first right out code that actually works, then when I see a pattern repeat itself, I like to refactor that code to try and avoid the repetitive code.  Reasons include: Smaller Code Less Chance For Error Don’t Repeat Yourself (DRY) As an example, the c# code I’m working on now involves reading key values to be used with the Stripe payment service.  Here is the code I first wrote: [crayon-5655512c6589e181623961/] The first thing I do is to look for the pattern and try and pull out variables that I know are going to be helpful in refacotring. You can see below that I pulled out the keyAppName variable and I also changed the assignment to be to a new variable rather than … Continue Reading


Get every new post delivered to your Inbox

Join other followers: