Adobe AIR

20th November 2008 | 0 Comments

I finally made my first AIR app today.  It's a simple Excel to XML file converter I made for work.  I decided to use Flash CS3 to build it because I thought it would be easy, boy was i wrong.  CS3 doesn't have any internal AIR documentation even after installing the SDK.  You do get code hinting, but that's only helpful if you know everything about the API.  So I had to find a copy of Flex's AIR documentation and use that for reference.  CS4 apppears to have AIR documentation inside of it; however, CS4 tries to grab the documentation from online instead of using the local copy (There is a perference for that, but its hidden).

Google’s Documentation Sucks

11th November 2008 | 0 Comments

Google makes some pretty cool stuff and its generally is well engineered, except for that Android bug.  I recently had to use Google's Flash map component.  First of all, they need to make an MXP so it installs correctly instead of having users manually place it in the components directory which is hidden deep in the filesystem.  Second, some of their documentation is utter crap.  The Marker class has a property called gravity.  I have no idea what it does, but it sounds interesting.  So after consulting the documentation i found this little gem of a description:

A Number value that specifies marker gravity factor.

Why bother even wasting your time writing that, its a totally worthless description.

Code Courtesy

7th November 2008 | 0 Comments

As a programmer you get to see a lot of people's code and more often than not you have to change some of that code.  Sometimes all you need to do is change a sign or the order of a variable or two, but most of the time you have to make a modest change.  Now if that change has to go back to the orginial owner its a common courtesy to comment it.  Especially if there are hundreds or thousands of line of code within a project.  So why am I stating the obvious?  Because a co-worker of mine recently had a run in with a senior level engineer at another company.  This engineer didn't comment his changes and then had the gall to say "Can't you read code?" when asked to do so.  What kind of response is that.  Of course I can read code, but when I don't know what you changed it makes it a little hard to find those changes especially when there are over a thousand lines.

So the lesson here is don't be an asshole and comment changes you make to someone else's code.