Topic: Flash Lite Tutorials

Here are a few tutorials for Flash Lite

Please post more !

http://www.biskero.org/?page_id=342

Liam

Re: Flash Lite Tutorials

I should point out that those tutorials appear to be for FlashLite 1.1, which is quite primitive compared to the FlashLite 2.0 we're running in the chumby.

Re: Flash Lite Tutorials

The official resource at http://www.adobe.com/devnet/devices/flashlite.html is actually quite useful, particularly for 'traditional' flash programmers (Flash Full Fat?)

http://www.metah.ch/blog/?cat=5 is a nice blog with plenty of flash lite and often shares source code and tips (ex http://www.metah.ch/blog/?p=191) that I find very useful

Re: Flash Lite Tutorials

Note that the FlashLite 2.0 vm will happily play FlashLite 1.1 / Flash 4 SWF and FlashLite 2.0 / Flash 7 SWF so the old tutorial are still good. Also Flash 4 is quite ugly but the applications will be smaller and faster than Flash 7 ones.

Regarding the specific implementation, though, I do have some questions.
Can somebody list what Chumby specific "commands" are implemented and how to call them ? (I am assuming via FSCommand2).

There is a long list here: http://livedocs.macromedia.com/flashlit … l#wp215896

Some are specific to phone-like devices but it would be good to know which one the Chumby supports.
Is the "FullScreen" command required or is the chumby always in full screen ?
Do you implement any other specific to the chumby ?

Also, is the "squeezy" thingy accesible from Flash ? Would it generate a key press or something (and if yes, which keyCode) ?

Of course I could answer all these questions myself if only I had a Chumby, but... smile smile smile

Re: Flash Lite Tutorials

Virtually none of the FSCommand2() suite is supported, because, as you say, they mostly apply to phones.

Most of the extra chumby functionality is currently implemented as ASnative() calls.

It's very unlikely that a *widget* needs to use many of those calls, and, in fact, using them arbitrarily could risk interfering with the operation of the chumby itself.

Once those calls have been finalized, we'll document them.  A widget built around the current suite would become incompatible very quickly.