We
see this as the AIR platform ??™ s eventual undoing.
The approach taken by ScreenWeaver HX is different. So different, in fact, that it cannot be considered an
SWF2Exe framework at all. By supplying a loose communications layer between a Neko application and an
SWF, the whole compiled library theme is removed for something that is more pick and mix in nature. As
you can choose to include or exclude any library you like from a Neko application, you can do exactly the
same with one that utilizes SWHX, thus making the overall file size of the application absolutely minimal.
Also, as an SWHX application is essentially a Neko application, it means you have an infinitely extendable
framework, which can transfer from machine to machine without requiring a complex installation.
Another benefit of SWHX that is worth bearing in mind is one that has been mentioned consistently
throughout this book. Providing you develop your applications with haXe, you will essentially be
developing the entire application with a single language.
Pages:
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945