tombray.com

And I didn’t have to do the work!  A million thanks to Jon from www.clockobj.co.uk for posting this perfect write-up.  I’ll re-record the session soon, probably over the weekend.  In the meantime, please let me know if you have questions.

If you attended my eSeminar yesterday and I didn’t get a chance to answer your question, see below.  Click the “read the rest of this entry” link below for more.Q: Why did you make the ChatModel constructor public instead of private?A: ActionScript 3 doesn’t support private constructors, so if you’re trying to create a Singleton, you need to throw an error in your constructor if an instance has already been created.Q: have you looked into using a singleton to dispatch events? I use one I found on the net that allows dispathc at any level to any level…. Similar to CairngormA: Earlier versions of Cairngorm used to bubble events all the way up to the controller. There are a few rare cases where that isn’t ideal. In order to participate in event bubbling, an object must be part of the DisplayObject hierarchy, so if you have some object that isn’t on the displayList, it can’t bubble up an event. However, that’s typically not an issue for most apps. Also, if you have a very deeply nested component that needs to dispatch an event and for performance reasons you need to handle it immediately, a Singleton EventDispatcher may be in order. Again, these two cases are rare in my opinion, so I use bubbling for simplicity’s sake.Also, even if you’re using CairngormEventDispatcher, you will likely want your events to bubble up at least a level or two and then be dispatched using the CairngormEventDispatcher by a more senior view.Q: Where would you handle Remote Services like AMFPHP in this framework? Read the rest of this entry »

Update:  I gave another EasyMVC presentation on 3/28/08 and it was recorded.

Apologies to everyone who listened in to my Adobe eSeminar this morning. Because of the audio issues, my voice wasn’t recorded so there’s no way to watch the presentation again. HOWEVER…I’m going to talk to the folks at Adobe about going in and re-recording the session on my own once their audio issues are worked out. If that doesn’t work out, I’ll record my own screencast.In the meantime, here’s the source code for the EasyMVC demo.Check back soon for info about the presentation.

Are you relatively new to Flex? I was a Flex newcomer once and I remember what it was like. I worked through some examples in the Flex documentation, read a few articles, set out to write my own app and quickly found myself with a mess and wondering, “Where should I put all this stuff?”. If you’re at that stage now, you should register for my eSeminar next Tuesday where I’ll show you a simple way to design your Flex apps so that they’re easy to maintain and extend.I’ll introduce my approach, which I call EasyMVC. It doesn’t require any special libraries, it keeps the “nerd-speak” to a minimum, and it’s flexible enough that if you later decide you want to use something more advanced like Cairngorm, it will be easy to switch.

If you’ve used the first version of the SearchCoders Dashboard, you may have noticed that the chat required registration. We’ve updated the Dashboard for AIR Beta 2 and threw in our new chat widget which does NOT require registration and the room usually has between 70 and 120 people in it these days. Be sure to download the new version at www.searchcoders.com.

Awesome. Robert and I are happy to announce that the SearchCoders Dashboard was one of the category winners for the AIR Derby contest. To download the app or try out the web-based widget, please visit www.searchcoders.com.

We’d like to send special thanks to all of the Adobe engineers who answer questions on the FlexCoders list. Without them, the SearchCoders Dashboard wouldn’t exist.

Also, congratulations to all the other winners!