Comments on: RIA Unleashed 2011

By: Runtime Expectations Episode #12 – Hot Web Comics! | Runtime Expectations

Mon, 09 Jan 2012 05:19:18 +0000

[…] are still relevant. We brought up Jesse Warden’s recent RIA Unleashed Conference post-mortem: http://jessewarden.com/2011/10/ria-unleashed-2011.html. Preshow with Adrian and Rachel Adrian with the situation room to his back Rachel @CrowChick Mic […]

By: Shawn

Shawn — Wed, 02 Nov 2011 16:55:34 +0000

If anyone cares (probably not!), I updated the post with much better examples to show how easy this is to integrate into your workflow.

Ok, I’ll stop spamming your post now, promise :p
http://esdot.ca/site/2011/fast-rendering-in-air-3-0-ios-android

By: JP Venter

JP Venter — Wed, 02 Nov 2011 15:19:10 +0000

"I personally blame Adobeâ€s lack of hard marketing about how awesome it is to build mobile apps in Flex" - perhaps this should be our 'call to arms' as dev's to show the world what's possible? I was just browsing the list of mobile jobs being posted on elance, and it seems the industry (mostly) is not entirely sure which software stack to adopt for a mobile solution - pinned to the job requirements is often just android, ios and blackberry ca-ching! I spot opportunity!. And even those specifying objective C, Java or HTML5 - I'm sure are just oblivious and wouldn't mind a dev presenting a Air based solution to their proposal. So I'm thinking we be the marketing force, attack elance and 'mobile' job posts with killer Air proposals/solutions, viva le Air Army! So anyone got ideas on attack formations ;) .... I'm talking some nippy marketing slang phrases to toss around here?

By: Runtime Expectations Episode 12 – Hot Web Comics! | CodeBass Radio

Runtime Expectations Episode 12 – Hot Web Comics! | CodeBass Radio — Wed, 02 Nov 2011 02:57:54 +0000

By: Shawn

Shawn — Tue, 01 Nov 2011 20:40:00 +0000

In reply to Josh Tynjala.

Wierd, I get group 1’s issue, though almost all of that can be worked around with draw(). Just have a sprite that’s never added to the stage, draw to it, or add filters, and then cache it to bitmap yourself.

Group 2, I don’t get. This is code you can write in 20 minutes, just set up some static properties, and a method to name them. Or, have a dedicated class for each type of sprite, with a static .cachedData property, and all new instances can just check that property.

Personally I’ve found it amazingly effective, and really really easy.

Even when stage3d hits, we’ll still have a similar workflow. You’ll still need to rip everything to bitmapData, and pass it to a container for rendering, you will just covert it to a ‘texture’ first, and use Sprite2D as the container instead of bitmap().

Same shit different pile really…