Through my computer science university experience, my need to download SDK’s was limited. Much of our work was done in Java and so the biggest requirement was to download and install Eclipse and the Java JDK. I was fortunate to be able to take a course in iOS development at university as well (one of the best courses I took by far). The setup experience for iOS development is similarly simple. Just download and install the iOS SDK. XCode and all the other tools are automatically configured and prepared for you. You just open XCode and start coding. I found these setup experiences to be generally quick and painless. I recently needed to test a PhoneGap application in an Android context. I had never done so before and I, perhaps naively, expected the setup to do so to be equally as painless as I had experienced before. Wow was I wrong.
Dude Where’s my workflow?
We would start out with a series of events and function calls to attempt to chain together the bootup but it would quickly become hard to inject in new tasks. This prompted us to use the tinyHippos mantra “There has to be a better way”.
I wanted to start this article with the actual definition for closure, so I went where everyone goes: Wikipedia :-) Here’s what they have to say about closure:
Well then… that statement really confused me, I mean seriously… a closure is said to be “closed over”, brilliant! Let’s try and define closure in plain English and let’s first look at the two major requirement that a language must implement to be able to have closure.
In this article we’re going to present our favourite way of creating objects and doing inheritance. Keep in mind, this peg will not fit into just any size hole. Take the time to learn JS and then apply the patterns that match your needs best. We recommend this book to get started: