Tim Hoolihan

This post is intended to go through the process of writing and publishing an app. It will be a high-level introduction. The idea is that future posts that will dig into specific topics in depth. This post will be updated to link to those future posts as an index of mobile development topics. The app [...]

…or some other catchy metaphor that will grab your attention. These technologies were hot over the last 5 years. Flex gained a particular amount of popularity in the Java community where UI technologies have a bit of a spotty record (that’s like saying my Bengals have a bit of a spotty record over a lifetime). [...]

Working on a relatively straightforward page, I want to have some of the simpler static contact come up as an overlay style of popup. Following web standards, it would be nice to have this code automatically work based on a CSS class. This would provide two benefits: easy to add more such links without writing [...]

I’ve had several discussion recently some of the more advanced features of JavaScript, such as functions as return values, namespaces, encapsulation, etc. In order to demonstrate some of these things, I contrived a simple example of a dependency injection tool. Never mind that dependency injection is not really a relevant pattern in JavaScript or other [...]

If you understand what’s going on when this runs, then you understand javascript scoping. var x = 5; alert(x); function foo(){alert(x);var x = 10;alert(x);} foo(); alert(x);

Employee = { New: function(fname,lname,em) { return { first: fname, last: lname, email: em, displayName: function() { return this.last + ‘, ‘ + this.first }, sig: function() { return this.displayName() + ‘ ‘ + this.email } } } } var tim = Employee.New(‘Tim’, ‘Hoolihan’,'tim@hoolihan.net’) tim.sig()

Douglas Crockford’s essay on Javascript’s history and resurgance is a great read, if you haven’t already read it. – “Given the process that created JavaScript and made it a de facto standard, we deserve something far worse.”