However, you have not yet looked into the
important aspect of handling communications between Flash and the window, or Flash and the
Neko layer.
For those of you who have used other SWF2Exe frameworks to mobilize your Flash applications, you ??™ re
in for a treat. Usually, when developing against SWF2Exe frameworks, one needs to have to hand a
large document detailing all the available API functionality for inclusion into the Flash file. This can
become tedious as, not only does it make the framework limited in terms of capability and provide yet
more code for the developer to learn, but it also means the Flash developer has to hard code
functionality into the presentation layer, that would be better off elsewhere.
Part III: Extending the Possibilities
518
Asynchronous Communication
The simplest way to communicate between Flash and Neko is to handle calls from an FSCommand in
the Neko layer. The Flash object you create in the Neko layer, which eventually gets hosted by a Window
instance, provides a method, which you can override called onFSCommand :
flashObject.
Pages:
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962