Randy Troppmann

An amazing photo from Leonard Nimoy! He tweeted this on Mother’s Day.

At the recent Google IO conference Adobe announced the public beta of Flash Player 10.1 for Android and the public prerelease program for AIR on Android.

I’ve been working with the AIR for Android SDK for a bunch of weeks now and Adobe loved my prototype of Trackometer (info on the iphone version) so much they were going to include it in the Day 2 keynote demos at Google IO. I guess Google put serious time constraints on things and the demos did not happen on the main stage. However, Trackometer was demonstrated in the Adobe booth and the AIR team featured it in their blog. Ted Patrick also included it in his demo in the video below (see 2:00). Adobe also used the Trackometer source code with Flash Builder to do a live demonstration of compiling and moving the application to a device.

Work continues on the Trackometer app. It will have more features than the iPhone version currently has.

Adobe’s recognition is a huge thrill for me and a nod to independent developers. My inclusion in the private prerelease group was a direct result of the 360Flex presentation I gave in San Jose this past March. I have to pass on a big THANK YOU to Andrew Westberg for asking me to co-present a topic and to Tom Ortega/John Wilker for accepting our presentation proposal. This proves that sometimes you just need to get away from your computer, get on a plane, and go and talk to people in the industry. Face to face.

Adobe loves choice. They believe you should be able to develop once and deploy across multiple screens. Or devices. RunningMap Trackometer is a real example of this happening. To the right is a swf that is a proof of concept for an app that is being developed to run on Android-powered devices using Adobe’s AIR for Android runtime. To make the point clear, this swf was compiled from the same source (minus some device specific calls) that is used to compile the app that runs on Android mobile phones.

I have developed apps for the iPhone – one of them award nominated. RunningMap Trackometer for the iPhone was accepted for sale October 2009. I think it is a great platform to develop for and has tons of potential. But, learning Objective-c and Cocoa was and is tough for me. It’s pretty foreign and it still sometimes takes a long time to solve simple things. I have no doubt that will get easier over time and I love to learn new things. Once you get into it Objective-c has an oop-elegance about it. The real barrier in my mind to creating apps for the iPhone is the torturous process you need to go through to test, provision and submit your app so that you have maximized your chances at Apple blessing it and allowing it to be sold on the App Store. Anyone who has been there knows what I am talking about so I will stop there.

Trackometer for Android is not so much a port of the iPhone app as it is a port of the RunningMap.com application itself, with far fewer features. I’ve been developing for the Flash platform for 10 years and, unlike when I program in Objective-c, problems are solved very quickly. The workflow is like butter. And this is full blown Flash. While developing using the AIR for Android SDK, I did not need to change my well-honed workflow in any way, shape or form. RobotLegs is there. GTween is there. Flash Builder goodness. The API is only limited by the new paradigm; MOUSE_OVER, for example, is not possible with a touch interface. In fact there are a host of new APIs. Geolocation for example. And Trackometer uses that. Try to take your laptop for a run and see how fun that is.

So far I am amazed by how well AIR for Android performs on my Motorola Droid.

Getting the app on your phone is SO MUCH EASIER than with iPhone apps. No provisioning etc. Android phones could install Trackometer directly from this blog post if I placed the package here. But I can’t be cause a) Trackometer is not finished and b) the AIR for Android runtime is not released yet. I’m not sure when but I hope to know soon. I can’t wait.

An important lesson I learned today: the onRegister() method of a Mediator in the RobotLegs framework get’s fired when it’s view is added to the stage. This means that the event mappings and event listeners that you place in the onRegister() method will get invoked each time and (assuming you are adding and removing the view multiple times) unless you use the onRemove() method to un-map and remove the event listeners, you will most certainly get a memory leak. Good to know!

This is a little inconvenient because I was hoping that I could use the mediator event handlers to update a view while it is not on the display list. As it turns out, the mediator will not respond to event mappings when it’s view is removed from the stage. Also good to know.

Any input on this appreciated!

It was Ted Patrick‘s fault. He dared to come to Edmonton in January and I was so impressed with his presentation at EFUG that I registered for the first 360Flex conference which was being held at EBay HQ in SJ. Never been there before. Didn’t know anyone there. Friend and fellow Edmontonian Grant Skinner was going (and presenting) and that gave me confidence that at least I would know someone there (as it turned out, he was quite busy with the Adobe peeps and I didn’t see him much).

Leading up to the conference the buzz on the 360Flex website was to sign up on Twitter. I signed up under the name of “brando”. Remember, this is February 2007. NO ONE knew what Twitter was. Seemed like a useless service to me but it gave me a bunch of new Flex-knowing friends and maybe it would help me connect with some people when I got there. Through twitter I met PolyGeek and told him I was going to hunt him down and say hi.

On the flight to San Jose I met another Edmontonian who was going to the conference: Victor Rubba. Great guy. Now I have another friend to hang out with at the conference.

The morning of the first day I walked from my hotel to EBay and in the main entrance and I couldn’t believe my eyes. Thousands of miles from home, feeling like I was not in Kansas anymore, a guy was standing there with an Edmonton Oilers jersey on. (turns out he was from Calgary, which is ironic to the extreme). I met Tom and John for the first time and they offered me Chocolate cake that Tom’s wife made (nice!). They asked me what my Twitter sig was. They said in unison “Ah, Brando”. While waiting for the keynote I was chatting with some guy who looked really familiar to me. I asked him where he was from and he said San Diego. I shrugged and walked away. Sorry, Josh Tynjala, I was out of touch.

After the first session I was getting Danny Patterson to sign his book on Design Patterns for me when I looked up and saw two smiling faces in front of me. Zach Graves and Aaron King were developers on the Y! Maps team. Because RunningMap.com makes good use of Yahoo! Maps, I was pretty active in the maps online group. I had told them I was coming to the event. They found me first. Now I knew I had someone to hang with. GREAT GUYS. Aaron even gave me his staff issued Y! backpack (at Max 2008 Allen Rabinovich asked me where I got it because they are exclusive to Y! employees).

The food was amazing considering what I paid for the event ($150). I phoned my wife while sitting on the green grass by the ponds of coy and she was extremely jealous. Back home it was -15C˚ with snow up your waist. While chatting with Grant and some other guys I did a double take. “Phillip Kerman?” His was the first Actionscript book I have ever read. Chris Cantrell. Can’t miss Mike Chambers. Victor introduced me to Peter McKiernan who showed up on day two with the same shirt as me. LOL. I did in fact find Dan “PolyGeek” Florio and introduce myself. I didn’t chat with him long because I had to run and pee. Er. RunPee.com.

The presentations were amazing. Ely Greenfield’s was my favourite. Deepa Subramaniam. Mike Chambers. They were all great. I went to a presentation on ANT and the speaker, Joe Berkovitz, asked the audience if they were not using version control. I raised my hand then looked behind me. I was the only one with my hand up. Heh. Still don’t. Just kidding. Maybe not.

Ok, this post has gone on too long already and I think you got the point. Sign up for 360|Flex, San Jose, you will meet a ton of people and have your head filled up until it explodes. It’s the best Flex conference out there so sign up!

For ActionScript 3 development I have just begun exploring the Open Source Media Framework (OSMF) and the MVC based framework called RobotLegs. What better way than to use them together? The best way to learn this stuff is to dive in and apply it to real solutions. PLEASE leave a comment if I have gone astray.

You can download the source code here (based on OSMF sprint 8 and RobotLegs 1.0.2).

Here is the working proof of concept with video served by Castfire.com:

Project goals:

1. Build a production ready video player
2. Learn OSMF
3. AS3 only compiled with mxmlc
4. Keep things organized

1. Build a video player

This is a longer term goal. The video player presented here is only a proof of concept. Video on the web continues to evolve and now seems like a good time to re-factor some key video player projects to bring them up to date and address new requirements.

2. Learn OSMF

Strobe Open Source Media Framework is an Adobe initiative to bring some standards to video player development. I have been itching to get my hands dirty with this new framework to decide for myself if it is worth buying into.

Some may think it is inevitable that OMSF will be over-architechted and therefore full of bloat. I can't really answer that yet. But I can say that I REALLY like the convenience methods that come with the MediaPlayer class. This build is 90k which includes RobotLegs ... acceptable.

Sure, you can build a video player that comes in at 15k. However, as soon as you start adding modern day requirements (CDN services, advert engines, analytics, chapters, xml lists etc) things quickly get complicated. The promise of OSMF is that all these things can be integrated into your video using a plug-in architecture which will greatly ease the burden of development.

3. ActionScript 3 only

Every video player I have worked on to date (other than a few Flex experiments) have been made with Flash Professional which means they need to be compiled from the Flash IDE. Using Flash Builder to compile the application de-couples the workflow from the Flash IDE which makes possible all sorts of interesting ideas.

This does not preclude the use of Flash Professional made libraries that can be used for things like the control bar. After all, the Flash IDE is still really good at some things.

4. Keep things organized

I have made probably a dozen or so custom video players to date. When building one from scratch it does not take tong before it gets complicated: video players are the mothers of all things asynchronous. I have my own particular way of using design patterns and structure but have never took the time to think through a solid framework and ultimately my projects get big enough that they no longer feel like they are on solid ground.

Someone else has thought it through and this is where RobotLegs comes in. I have had a pretty good experience with Cairngorm over the last couple years but it requires the Flex framework. Dependency Injection seems to be the hot topic recently and I have read some good things about RobotLegs so I thought I would give it a try. This video tutorial from John Lindquist helped me to put together this first implementation.

The thought here is that there are other views to manage than just the video player and control bar. RobotLegs will help make these views and OSMF plugins manageable and modular.

Some code

Here are a few classes to show how video player events flow through RobotLegs to the DetailsView so that bytes loaded and playback time can get updated. Download the source for the full meal deal.

The MediaPlayerViewMediator class captures the events from MediaPlayerView which sets a property in the model.

The model extends the RobotLegs Actor class can use the RobotLegs dispatch() method so that the event can be listened for from anywhere within the RobotLegs ecosystem.

In this experiment, DetailsViewMonitor listens for the events from the model. Since it is injected with the DetailsView instance, it can hit its property setters with new data.

Conclusion

Reading framework documentation makes my eyes bleed. The only way I can really intrinsically understand how they fit into how I build applications is to use them. RobotLegs is a winner. I have not worked with OSMF enough to have an opinion one way or the other ... it has not reached a dot oh release yet.

Early this month Apple banned a developer whose 1000+ apps then disappeared from the app store. Wow. Apparently Apple felt they were gaming the review system which is probably not that difficult to prove.

This story hit home with me recently because my own iPhone App, RunningMap Trackometer, has been getting a few bad reviews on the US App Store. (you can see my blog post about it here). This is obviously devastating for sales and shows how important reviews are. My first thought was to get some friends to post some good reviews to counter the bad ones. And it would be easy to do. But think twice if you think its a good idea.

The problem of bad reviews is exacerbated by the fact that when you uninstall an app, you are prompted to review the app which I am sure encourages far more bad reviews than good ones. Ouch. Apple's review system is broken!

Not so fast. There are some subtleties here. The App Store will show reviews only for the "current version" while hiding the rest under the "all versions" button. The App Store also prominently shows "what's new in version ..." so there is hope!

What will I do with my Trackometer app? Fix it. Improve it. Earn some better reviews. My customers will be able to see that I have read about their concerns and improved on the product. But I won't fake the reviews.

I use a MacBook Pro as my main machine. When I am in my office it is plugged into an external monitor and sits on a stand. I use a wired Apple keyboard and an inexpensive wired Logitech mouse. I have tried many different combinations of wired and 'less keyboards and mice and I much prefer wired devices. Batteries problems, connection problems, tracking problems. It would take more than a mighty effort to change my mind.

Then came the bluetooth wireless "Mighty Mouse". Unlike other third party bluetooth mice, it connects quickly and tracks well. I like the little scroll ball (although when it gets dirty it does not work so well). I really don't like the side buttons. There is one fatal flaw with this mouse: the whole body of the mouse is the click mechanism. If you need to lift the mouse because you run out of space, the mouse unclicks. Big problem. That being said, it has worked really well for me as a mouse I keep in my backpack when I am using the MBP away from the office. But, it didn't change my mind.

I am happy to report that Apple's brand spanking new "Magic Mouse" has solved this problem. You hold the mouse by the bottom half of the mouse. This is the single biggest reason I decided to write this blog post. No one is talking about what I think is a great fix to a gargantuan design mistake! Like the Mighty Mouse, the whole mouse is one big button which is a "left click" if your finger is pressing on the left side or "right click" if on the right. Leo Laporte complained on TWIT that this means you have to lift one finger and click with the other. That is the height of lazy! It's a non issue to me.

The design is stunning: it's like they put the Mighty Mouse on a diet. It is thin, sleek, shiny and light. I like the way it fits in my hand because I tend to hold a mouse and move it with my fingers. A mouse that is designed to fit my whole hand "erognomically" forces me to use more of my wrist and arm when mousing, which leads to shoulder pain. The sharp edges of the top take getting used to.

Now the killer feature: 2/3 of the top surface of the mouse is a trackpad. Gone is the scroll ball. With the lightest of touches of a single finger you can scroll a web page up, down left or right. Flick your finger and the window scrolls with momentum that stops immediately when you touch the top of the mouse again. Works brilliantly well. The only multi-finger use is side to side navigation using two fingers. I can see lots of possibilities. For example, click and drag is an ergonomic problem to me. Imagine clicking, release and move your finger to select text. I am sure there are more multitouch features to be added in the future.

Nice design. Tracks well. Connects quickly. Added rechargeable batteries. Magically changed my mind FTW.

UPDATE (25-03-2010): Hold yer horses. My home machine is a unibody MacBook Pro connected to a 23" Cinema display, and the mouse works really well. I made my employer pony up for one to go with my dual quad core Mac Pro and the mouse is terrible! Nothing I did made it any better. It was mousing through molasses particularly when clicking and dragging up at an angle. Shrug. I gave up on it and am looking for another wireless mouse.

Axiis is the open source data visualization framework Tom Gonzalez talked about at Adobe Max earlier this month. Watch his presentation here. At this session Tom announced the release of Beta 1.0 of the library which is built upon Flex 3.

I recently finished and deployed a complete rewrite of the map mashup RunningMap.com which uses Axiis to display elevation data in a line graph. After seeing his presentation 360|Flex last May I decided to give the (then alpha) Axiis framework a try. Upgrading to the Beta 1.0 release was painless and immediately I noticed the drawing performance of the graph went from slow(ish) (which actually was not a bad effect) to instantaneous.

Connecting my data source to the graph was a challenge and I had to use the debugger to get the data wrapped "just right". I put together an example that illustrates:

• use of Axiis LineSeriesGroup
• wrapping an array collection "just right" so it can be bound as a data source
• overlaying the graph on a map
• setting the data tip using a function

The live example is here which is source view enabled.

Comic Sans gets a rough ride. Let's face it. I am joining the chorus of John Wilker's post to say yes! I agree! I think though that this makes it now an international day since my blog comes out of Canada.