• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Part VI: APPENDIXES > PLANNING DEPLOYMENT OF FLASH MX ON A TOUCH-SCREEN KIOSK

PLANNING DEPLOYMENT OF FLASH MX ON A TOUCH-SCREEN KIOSK

The first question you need to ask yourself when laying the groundwork for a Flash MX based kiosk on a touch-screen system is: “Will I be able to make the kiosk do what I need it to do with Flash alone, or will I have to use additional software to complement Flash MX?” Perhaps you may need to control hardware devices or peripherals attached to the kiosk. For example: Your kiosk project may need to receive input from a bar code scanner that is attached to the kiosk, or receive input from some other specialty input device.

Obviously, these extra devices may dictate the platform or operating system that is the core of your kiosk, but one avenue to consider if you are deploying on a Microsoft-based platform, such as Windows 95/98/ME/NT/2000/XP, would be to use an ActiveX control to handle talking to the hardware. FScommands or geturls issued from within your Flash MX application to a hidden frame in a browser-based design could trigger commands that contain embedded ActiveX objects. These ActiveX objects could be programmed to talk (at a lower level than Flash is currently capable of) to the actual system drivers, such as a bar code scanner serial driver, or even the operating system itself.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint