We've been examining the specifics of how to create event driven programs for the last several blog posts. But somehow, we need to integrate jQuery custom events with our server code. In this post, we'll see how we use Ajax to do just that.

[More]

In my last blog post, we took a more in-depth look at jQuery custom events to learn the specifics of how they're used. How, though, do you identify the events in your event-driven architecture? That's the subject of today's post.

[More]

In the last post, we got started with event driven programming. In this post, we're going to look a bit more at the mechanism for event driven programming, jQuery's custom events.

[More]

I was talking with a friend recently about event-driven programming. He and I have been heavily into working with custom events for a few years. We've both seen the benefits of robustness and maintainability that event-driven programs provide. Why, I asked him, have more people not adopted EDP? His answer really surprised me.

[More]

Arguments in JavaScript functions are optional. I might declare that a function accepts 3 arguments -- but users of the function may pass in 0, 1, 2, or 3 arguments. Question: how do I know whether all arguments were passed in? And if only some of them were, how do I know which ones were?

[More]

In yesterday's blog post, I began answering an email about jQuery custom events. Today, I'll show code that uses jQuery custom events to deal with the fact that Ajax calls are asynchronous.

[More]

I got a lot of nice responses from my post here on a JavaScript skeleton. One person, though, wanted more...

[More]

A developer wrote me recently with this plaint: "I'm doing more and more JavaScript, but I don't think I really understand it well enough. There are self executing functions, anonymous functions, anonymous self-executing functions. Then we need to namespace and keep some things private. I've got enough theory. I need some practical help. I'm hoping you can give me some."

[More]

Well, I finished that monster prototype, with much credit to my coding partner, Maciej. I figured that over 11 days, I worked 165 hours. Whew! Yesterday, we gave the presentation to a large multi-national corporation. To my relief and gratification, they were very impressed. Which leaves me, now, with only one small problem...

[More]

Yesterday, we looked at some simple server code that is called by events generated on the client. We saw that the server returns an EVENT property in its response -- but that my example never uses it. Today, we're going to see how that is used -- and why I think EDP is a BigDeal(tm).

[More]