Just for the record, I’m speaking on continuous integration in RIA development architectures

It read as follows:
Unable to transcode Assets.swf

I wasted a bunch of my own time (and some of Abdul Qabiz’s) trying to figure it out, but nothing I tried seemed to work. Of course I googled for help, and the results their were even more mystifying. The only post I could find that sounded remotely close to what I was experiencing was this: http://www.codeverge.net/item.aspx?item=100658 and even though “mac_55″ was able to get it working, he had – as he put it, “No idea why it wasn’t working before.” That didn’t help much.

I started to suspect that Flash was somehow to blame, so I tried using another existing asset SWF that I had used w/ success in a previous project. Low and behold, it worked perfectly. Okay, that’s a clue… it’s somewhere in Flash.

Next, I saved the .fla that created the SWF that was working to the desktop and recompiled… then I tried using the resultant SWF in Flex again. You guessed it, it didn’t work.

Now I was really starting to think I was on to something, Flash was creating corrupt SWFs for some reason. I had crashed Flash about 10 times earlier trying to import PSDs, so I thought a restart may be in order, hopefully to resolve some phantom memory leak. So, I restarted.

After restart, I opened the previously successful, but now failing .fla and rebuilt. I noticed a ton of errors. Apparently, when I saved the .fla to the desktop, I broke the dependency chain somewhere and caused a bunch of errors. I realized that I hadn’t seen the errors before, most likely because the Output window was buried beneath a bunch of panels. Then, I opened the .fla for my apparently un-transcodable SWF – published the movie and poop, an error. Apparently “Background” is a reserved name, and my library item w/ the linkage id “Background” was causing the error. I changed the name to “BG”, it compliled fine, and worked perfectly in Flex.

The morale of the story is: if you see the “Unable to transcode” error message, make sure you’re freakin’ SWF is building properly. duh.

Hopefully someone on the Flex team can make sure that we get a more verbose error message in Flex 4.

If you are one of the fortunate attendees of this year’s FlashForward conference, by all means say hello if you see me

This year, FlashForward is a single track conference, so that means I could potentially cover each and every seminar… I’m not promising that, but I will promise to keep you up to date on the items that are the most interesting (IMHO). I’ll be doing my best to invoke conversations with all of the speakers and many of the attendees, and I’ll be sure to take and publish plenty of notes, including of any interesting URLs or examples for people to try.

If anyone has any idea on how we might make the live blogging from the event more relevant or useful, please let me know ASAP. I’m often too busy writing code to stop and blog, but things are changing soon… in a major way. Stay tuned for updates

For those of you who don’t know, here’s the blurb on Vuvox:

VUVOX is an easy to use production and instant sharing service that allows you to mix, create and blend your personal media – video, photos and music into rich personal expressions.

http://ebayinkblog.com/2008/06/23/vuvox-on-ebay/
http://seekingalpha.com/article/82695-ebay-acquires-vuvox?source=feed

Congratulations to Brian, Jim, Belmer, and Luke… Great work fellas

It’s a tool built in Flex that allows you to view a “real-time look at what’s selling at CafePress, the colorful marketplace brimming with millions of user-created products that express your passions and points of view.”

This project, which is conceptually very simple, is testament to the rapid development one can achieve with relative ease using Flex and the Flash Platform. There’s not much eye candy, but nevertheless it’s launch is a feat that shows how quickly a large company can get cutting edge projects out the door using Adobe® technologies. The tool is totally customizable due to it’s content model which is largely XML based and thus can be customized by non-technical people w/ ease. Also, I think it’s cool that this project will continue to take shape over the next year as the elections progress.

A big thanks to all the folks at CafePress who helped make this happen

The solution that I’ve found is simple, elegant, and totally familiar with anyone who has ever had to view a typical server log output.

Basically, I used “tail -f” and pointed to the local flash log. Unfortunately, this has the same problems as viewing any server log output using tail; it’s not very pretty, and it can be hard to read at times. However, it hauls ass and is easy to implement, and that is all that I really want.

It was easy to take it a step further in order to make it an easy to access command. Basically I just edited the “.bashrc” file found in my home directory, and input the following line:

alias flashTrace='tail -f /Users/USERNAME/Library/Preferences/Macromedia/Flash\ Player/Logs/flashlog.txt'Obviously, you’ll want to replace “USERNAME” above with your local machine username (If you don’t know how to get this, just open Terminal and type “cd; pwd”. The part right after “/Users/”is your local machine username).

After that, you can open a terminal from anywhere and type “flashTrace” to see the output (hit ctrl-c to return to the command line).

If you are a Windows User and don’t already have a shell solution, do yourself a favor download cygwin to access a unix-like shell and then you can also implement the above.

Simple, easy, and effective… at least it works for me

Cheers