Seattle.BloggersPub

AOL is shutting down a bunch of properties. Frankly, AOL is probably not the kind of company you look to when you think of leading edge. But they’re a significant player on the web with a very high user base and they’ve got a lot of valuable properties including their AOL instant messenger stuff and AOL mail. So it was interesting to read the full text of an email about where they are planning to focus their energies:

- Toolbar: Accelerate the distribution and monetization of toolbars to drive revenue derived from search and recirculation.

- Desktop: Develop and launch desktop software promotion push to drive increased ROI through the acquisition of new free software users.

- Mail: Increase effective monetization of mail while pursuing distribution opportunities to grow audience and engagement. Drive growth though new ad inventory (Quigo, etc.), ad packaging and sales strategy development, affinity and cobranding partnerships and open services.

- Truveo: Monetize the over 50 million UVs Truveo receives monthly through our O&O site and APIs through a phased approach including banner advertising on the site and monetization of the APIs.

The web browser is great. But you know what? Most people - the people who REALLY spend money and click on internet ads - they’re still using a lot of desktop software. They still interact with data and content through a combination of desktop and web browser applications. They haven’t made the full switch to web apps because they know and understand the desktop model. There’s a big market out there for web developers who want to target those people and create a desktop app that appeals to them.

That’s the bridge I see AIR being. You can keep up with the digerati by building applications for the web browser but you can take that code and start creating a desktop experience for those users who are drawn to it. It’s really all about providing the experience users want at minimal cost. Regardless of AOL’s problems or vision, the desktop has played an important role in what they do and there is still a tremendous amount of money to be made on the desktop. AIR opens that market up to web developers in a cross-platform way.

Rob just sent me a link to PlayCrafter which is a suite of games built entirely in Flex 3. It’s a really cool, customized example of a Flex application and as you browse around the site you’ll see that there doesn’t appear to be a standard component anywhere. They’ve basically taken Flex and designed it well enough that it feels like a regular Flash application. The games are fun, the interface is nice, and the application is very impressive. Between this and SmallWorlds, I think we’re getting into a whole new world of Flex!

Heh. I always love when I find out stuff we’re doing by clicking on a Techmeme link. I must not have been paying attention, but it looks like we’re adding Sony content to Adobe Media Player. As Liz from NewTeeVee notes, it’s mostly old stuff like Jerry Maguire and Men in Black, but who doesn’t love the classics? And it’s a first (I think) that we’re getting full length movies in AMP, so that’s pretty cool.

It also sounds like we’re going to be adding some new CBS stuff and according to CNet we even get Ghostbusters. Kick ass!

Hiromi made it safely to Seattle last Tuesday. I managed to stay away from the office all day, though I did a little bit of work during Hiromi's inevitable afternoon crash.

Though I arguably had time to do something more elaborate, we kept it simple, mostly due to the warm weather Seattle's had the good fortune to encounter for the last few weeks.

Grapefruit segments, red onion, soft chevre

We wanted something refreshing, so I segmented some nice ruby red grapefruit, sliced a little red onion, and sprinkled on a touch of salt. With a little drizzle of good olive oil, some freshly ground pepper, and a few dabs of soft chevre, this is perfect for a warm summer night. If it weren't so much work to segment a grapefruit, it would be almost no effort at all.

Stuffed eggplant with farro

In spite of the warm weather, I did turn on the oven. Both Hiromi and I have a weakness for stuffed eggplant, so I make variations on the theme on a regular basis when eggplant is in season.

When I make stuffed eggplant as a main dish, I typically use rice, but this time I elected to make it with farro, a nutty variant of spelt. It was gently seasoned with fresh rosemary, but works well even when the rosemary is more assertive.

This version is made with that same soft chevre along with some mozzarella, but I like almost any kind of goat cheese along with a mellow cheese that readily melts.

I've managed to keep us incredibly busy most of Hiromi's first week, but we actually have part of the upcoming weekend free, which is absolutely shocking. Somehow, I doubt the nice holes in our schedules will last...

Juan Sanchez took the weekend to check out some of the new skinning capabilities in Gumbo (Flex 4). The first one is kind of an intro and compares and contrasts the Flex 4 versus Flex 3 model. The second one uses a new Gumbo build and uses some of the transitions. Both are well worth checking out.

Holy hell. I’ve been tearing my hair out all night trying to figure out how to make a fully transparent and chrome-less native window using the mx:Window class. Luckily, thanks to Bradical from this post, I found the solution. You just need to set showFlexChrome equal to False in your mx:Window component. So quick mini-tutorial for anyone doing custom chrome/transparent native windows:

If you’re looking at a lot of AIR documentation you’ll probably see references to a NativeWindow class and think that’s what you want to use to create a new native window. If you’re doing Flex work however, you won’t be able to add any components from the Flex Framework to that NativeWindow because NativeWindow is a Flash class and doesn’t include the Flex (mx) libraries. So what you’ll want to do instead is create a custom component which extends mx:Window:

<mx:Window xmlns:mx="http://www.adobe.com/2006/mxml" width="200" 
        height="75" styleName="chromeless">
	<mx:Style>
		.chromeless
		{
			showFlexChrome: false;
			background-image: "";
			background-color: "";
			padding: 0px;
		}
	</mx:Style>
	<mx:Image source="@Embed('assets/notifier.png')" id="background" />
</mx:Window>

Notice I set up a style called chromeless, knocked out the background imgage/color and set the padding to zero like any other custom chrome application, but I’ve also set the showFlexChrome property to false. Now you’re good to go and you can start using all of the Flex Framework in your native window. In this case I’m setting the other native window chrome properties when I actually create the window (in my main Application file):

	public function createNewWindow() : void
	{
		var win : NotificationWindow = new NotificationWindow();
		win.systemChrome = NativeWindowSystemChrome.NONE;
		win.type = NativeWindowType.LIGHTWEIGHT;
		win.transparent = true;
		win.open(true);
         }

NotificationWindow is just the name of my MXML component (NotifyWindow.mxml) and I can set the system chrome options in that file directly, or on creation like I did above. If you’re going to be using the same chrome settings for your custom native window class, it’s probably easiest just to set the system chrome options inside your component.

Hope that helps other folks, and a huge thanks to Bradical, wherever you are!

As I’ve mentioned before, I didn’t come from the Flash world. I got hooked on the Macromedia juice via ColdFusion and Flex. I was always jealous of the Flash guys/gals because they could create some really cool stuff. So I was happy when Flex came out and we started seeing some “developer Flash” instead of all “designer Flash”. And then AS3 came along, which I loved, because programming Flex 1.5 was a headache and AS3 made a big difference to me as a developer. So I plunged headfirst into the world of AS3. But stuff didn’t look or feel as cool as all the Flash stuff out there I admired, so I started thinking heavy thoughts about the designer/developer workflow and getting more design into my development. That’s one of the reasons I am really excited about Thermo - it helps bridge the gap and allows me to add some really nice design elements to a Flex application.

But I was reading a Guardian article about 4chan that came a couple of days after reading Colin Mook’s treatise on AS3 versus AS2 and I started looking around 4chan (do so at your own risk). There’s an entire section dedicated to Flash. Right there next to Rules, the FAQ, and the Blog, they have a “Flash” tab which contains an archive of Flash stuff. They’ve also got an entire Flash section (oddly under Japanese Culture) which contains some of the most bizarre, gross, and morbid Flash content I’ve ever seen. (Warning: 4chan is basically the end of the internet and the links and content are definitely NSFW - the first 4chan Flash link is mostly okay, but the Japanese one and the rest of the site will probably offend just about anyone). Regardless of how completely messed up you can get with Flash, it’s a very, very creative medium, and people flock to that. The fact that it has an entire section on 4chan is a) disturbing, and b) indicative of how much people love using our platform to show off their….work. Better examples are sites like Orisinal or Animator vs. Animation- on the design side Flash is everything from games to big-time TV shows and It’s reason number one that Flash became so successful.

As a developer, I really want to see Flash evolve into a great application platform, and I think we’re getting there. But more and more I realize that we can’t stray too far from the design roots in the process. I think adding things like 3D effects and inverse kinematics to Flash Player 10 and Flash CS4 help with that, but I hope our core customers, our showcases, aren’t feeling ignored. One of the compelling things about Flash was that it made animation relatively easy so anyone could start expressing their creative side and we shouldn’t lose that. I know Lee thinks a lot about this, so if you have any thoughts, spend some time reading and commenting on his blog. Tell us everything from how you want to see the tools evolving, to how scripting fits into your workflow. The louder you are the better, and if we’re doing a good job, be loud about that too. Don’t be the silent majority.

J Wynia posted a pretty good (if semi-hacky) tutorial on how to get AIR applications running in Ubuntu 64. Like every other 64 bit question aimed at Adobe, I have no idea what the status of official 64 bit support for AIR is, but hopefully this gets you part of the way there.

Big congratulations to the eBay Desktop team on hitting the 1,000,000 download mark. The eBay application was one of the very first applications we showed off and even though I admit to getting a little tired of seeing it demoed, it quickly gave people the gist of what we were talking about with this newfangled AIR runtime business.

Last month I was at the eBay developer conference and sat down with Alan Lewis, one of the drivers of eBay desktop to get his thoughts on RIAs, user experience, and everything else he’s up to.