Rabidgremlin's
Soapbox

Yeah you read that right. I just received an interesting email from Brightcove (the video delivery guys) about issues with their Flash based solution and Windows 8 running the new Internet Explorer 10. To quote:

We wanted to make you aware of a development with Microsoft around Windows 8 that may affect your video content delivered through Brightcove Video Cloud.

Background

Microsoft is expected to release the next version of Windows, Windows 8, on October 26th. With Windows 8, Microsoft has made a decision to limit the use of Flash as a means for delivering content and move toward a concept of a plug-in free experience in Internet Explorer 10. As a result, sites will not be allowed to serve Flash in Internet Explorer 10 unless they have been given prior approval and have been whitelisted by Microsoft.

What this means for you

The default browser experience in the new Windows UI will not allow Flash unless the site has been approved and granted access by Microsoft. Therefore, if a Brightcove Video Cloud customer is looking for a full featured playback experience that is on par with Windows 7 today, they will need to submit a request to Microsoft in order to be whitelisted.

My initial reaction was “surely not???” and a quick search of the web indicates that there is a great deal of confusion as to what the IE10 behavior will actually be. However the Brightcove email provides an link to a handy Microsoft support article which clears things up.

Basically:

1. Windows 8 ships with two (!) versions of Internet Explorer 10. One for the desktop experience and one for the Windows UI experience.
2. Both ship with a built in version of Flash BUT the Windows UI version won’t run Flash unless your site is on a whitelist. The Desktop version will run Flash as normal.
3. You can add a meta tag to your pages which will trigger a prompt to the user to run your site in the desktop IE if they visit it using the Windows UI version of IE (a lovely user experience… not)
4. Lastly they give details on how you get you site added to the whitelist (basically emailing Microsoft with the details of your site and details of how it conforms to Microsoft’s Flash Content Guidelines)

Buried in the support article is the following reasoning for the difference in behavior between the Desktop and Windows UI IE version’s Flash support:

While any site can play Flash content in Internet Explorer 10 for the desktop, only sites that are on the Compatibility View (CV) list for Flash can play Flash content within Internet Explorer 10 in the the new Windows UI. We place sites with Flash content on the CV list if doing so delivers the best user experience in Internet Explorer 10 with those sites. For example, how responsive is the content to touch? Does it work well with the onscreen keyboard, or affect battery life? Do visual prompts comply with the Windows Store app user experience guidelines? Sites that rely on capabilities (for example, rollover events and peer-to-peer (P2P) functionality) that are not supported within Windows UX guidelines for Windows Store apps, and don’t degrade gracefully in their absence, are better off running in Internet Explorer 10 for the desktop with Flash.

Which seems fair enough but kinda underscores the point that having the Windows UI on the desktop version of Windows 8 (and making it the default) doesn’t really make sense when you consider what the user will be doing when they sit down at a PC to work.

It will be interesting to see if Windows 8 lands with a splash or a thud on October 26. I suspect it might be a thud and a whimper. Certainly it looks like Flash and the web are going to be in for a rough ride.

Over the weekend I published my first flash game, it’s called Jumbler. There is not too much to the game, to be honest. It was really more the result of me tinkering with the Flixel game framework to see what it could do; rather then my idea of a “blow your mind, addictive game”.

I’m must say that I’m pretty impressed with Flixel. Jumbler took less then 10 hours to put together and the bulk of the time was spent on the theme and graphics (such as they are). The initial game code (with box only graphics) took only about 3 hours.

The other cool thing was that this was built with entirely free tools and assets:

• Flixel – is a really great AS3 game framework. It does a fantastic job of turning flash into a game engine and letting you focus on writing a game, not on fighting with Flash.
• Flex SDK – The flash compiler and tools given away by Adobe.
• Flashdevelop – An open source Flash IDE. Syntax completion is a dream.
• Inkscape – An open source vector editor kinda of like Illustrator. It uses SVG as its native format and has excellent .png export support. All the graphics in Jumbler are drawn with Inkscape which made it really easy to resize, edit and evolve them on the fly.
• Flash Kit – Excellent resource for free sound effects.
• dafont.com – Excellent resource for free fonts. This is where I found the Boingo font that I used to drive the look of jumbler.

If you are interested in getting started with Flixel, then check out these links. The first is a basic “Hello World” tutorial, which shows you how to get your environment set-up and write a simple Flixel app. The second shows you all the key concepts you need to understand to build a game in Flixel, by creating a simple Defender style game.

I’m thinking of porting my half-finished “nac” game over to Flixel and integrating Box2D for the physics. It should be interesting.