Flash Lite

Transition from normal mode to fullscreen on Symbian is not made instantly. The Flash Lite Player allows itself a small delay in this transition, possibly because the fscommand2("Fullscreen", "true") code is yet to be played. This side-effect also accounts for the SWF filename to be briefly revealed, which I consider to be something less elegant in presenting your application.

Know what error code #6 or #9 are in Flash Lite content? How about "#3"? :)

If not, check these out:

http://flashmobile.scottjanousek.com/flash-lite-error-codes/

What's the big deal? Well, these are what consumers of Flash Lite content can potentially get ... what does that mean? Well, a potential BAD EXPERIENCE if you imagine you don't know anything about FL and get a big fat Symbian error screen with one of these obscure error numbers on it ...

Adobe, please rethink how errors can be better managed on mobile and devices going forward (esp Flash 10).

Here's a good summary post explaining why FL error codes need to change, esp under device constraints where errors are much more likely to be thrown!

http://dalerankine.com/index.php/2009/07/flash-error-codes-still-an-issue-after-all-these-years/

Would it be possible to catch and handle these OS level errors? Would it be possible to customize these errors? their descriptions? give a custom, user defined error menu inline with FL app??

All of these ideas have been suggested as far back as Flash Lite 2.x ... here we are at 3.x, and now Flash 10 coming, and hopefully we can make this area a bit better to manage!

Currently, getting any decent distribution (and revenue) from Flash content on devices is not an easy proposition. Packaging formats, swf versions and content-type fragmentation leaves users with a lot of confusion. Make the road to market much, much easier. If not, Apple/iPhone will likely be the only REAL game in town.

Why not default Device Central and Flash CS4 to AS 2.0 instead of AS 1.0 for development when starting a new project?

Are people really using AS 1.0? Those doing 1.1 are using Flash 4 syntax, (which is not really 1.0), and those doing 2.x and 3.x are developing either using a Flash 4 style, or using ActionScript 2.0 (and being very very careful about it).

Changing the default from 1.0 to 2.0 would say us one less step, please it will save a few of us from 5 minutes of debugging when we figure out the content targetted was not AS 2, but Flash ended up selecting 1.0!

Is there a way to change this behind the scenes in a text config file someplace? or is it built into the products? I'm too busy too look for it right now, but maybe someone else knows, or is willing to look.

Would it be possible to target any testing environment from CS4 tools, esp Flash CS4 ... for example instead of launching from Flash CS4 into Device Central CS4, a developer could configure Flash CS4 to publish into various SDKs? like Nokia S60 emulator, etc ... can't recall if BREW publishing worked this way or not ... but ideally it would be nice if developers could target whether they wanted to test inside of DC or not ... right now I'm stuck because I have a nasty bug that crashes Device Central CS4 ... however, there's no way to tell Flash CS4 to use a different testing emulator .... I think it would be useful regardless, so that developers could test in other emulators available. please evaluate this feature request. thanks.

iPhone uses default.png before startup of an application ... Flash Lite up to this point has not making starting of flash lite apps kind of "clunky" ... typically when launched a FL app will show articacts before blowing to fullscreen mode ... would be a lot cleaner looking if a custom default.png could fade in or appear, making a FL appear to load faster, while also giving a better user experience.