Zinc, SWF Studio, and AIR are known to be called SWF2Exe
applications, because they convert an SWF into an executable format, hence SWF2Exe is SWF - to -
Executable. This is something that the Flash IDE and player can already do in the form of a projector, but
what a projector can ??™ t do is provide an entire framework of desktop - based functionality that can be
accessed by the Flash movie. This is what Zinc, SWF Studio, and AIR do that make them invaluable. The
only problem is, in order to provide such extra functionality, the executable structure with which the
SWF Flash file must coexist has to provide an entire framework with the compiled application, as it
doesn ??™ t know exactly what functionality the Flash SWF file might want to call. Zinc and SWF Studio
achieve this by simply embedding the framework within the same executable file that contains the SWF,
so that it can be ported from machine to machine much like any other standalone application. Adobe ??™ s
AIR, on the other hand, takes a more arrogant approach by assuming that everyone who uses an AIR
application will likely want to use many other AIR - based applications, so have packaged their entire
framework into a runtime installation that must be carried out before any AIR programs can execute.
Pages:
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944