Developing apps...

Ultimately, the purpose of the chumby, in my view, is to allow its users to express who they are, on the inside, as well as the outside. A critically important part of this is being able to develop ActionScript 2 / Flash apps in 2025. Without the ability to quickly iterate in the development process, the chumbyverse will only continue to shrink. Even more alarming is the ever shrinking host of tools which can be used to drive chumby development. Adobe blackholed the flash development suite the moment flash died. FlashDevelop is dead. The mtasc website leads to a photography site now.

Due to chumby's reliance on flash to drive its applications, this would be an existential threat to the chumbyverse, if not for the fact that the new offline firmware actually includes FOSS tools for flash development as native binaries!

Centre to this development suite is mtasc, which is included on the chumby's zurk framework. I need to wrestle with the classpath a bit, but here's a very rough workflow.

0) Actually create an actionscript to compile

1) Make sure the usb is mounted as read write, check with

mount | grep usb

if you see the permissions are ro (should be in the parens) set with

mount -o remount,rw /mnt/usb

2) Now again, this could be way cleaner, but you can compile actionscript into a runnable .swf with the following...

/mnt/usb $ ./swftools/bin/mtasc -swf tuto.swf -main -header 320:240:12 tuto.as -cp ./swftools/std

Given tuto.as is your input, tuto.swf is your output.

2.5) You might need to run stop_control_panel if you're out of swap space

3) Run chumbyflashplayer.x -i tuto.swf

4) I'm pretty sure you can eventually put the resulting swf in

/mnt/usb/lighty/html/zchannel/channels.c1/offline-mode

How to Zurk your Chumby

Day one with my chumby