Previous Next        Current Page: NeXtMidas Training / Applets & WebStart / Applets
  • NeXtMidas and Applets
    • Generally, NeXtMidas macros can be installed as an applet with the simple addition of one html file. An example is included in the Applet section of the NeXtMidas User's Guide.
    • A number of properties can be set to allow you to configure the NeXtMidas environment for the applet. They include:
      AUX    - The write AUX and read AUX list (default is "RAM RAM|DAT")
      CMD    - The command to run
      HOME   - The home directory to use
      NMROOT - Overrides the default NMROOT setting (matches the codebase)
      NMS    - The macro to use in place of nmstartup.mm
      OPTS   - The option trees to add to the path (e.g. "UCL,SYS")
      WIN    - Window name (the special ID that can be passed via a switch
               (/WIN= for a graphical primitive OR
                /WIN.PANEL= for a graphical macro)
               to PANEL to allow the PANEL to embed in the browser rather
               than show up in a separate window)
      
      See Applets in the NeXtMidas User's Guide for details
    • Some rules regarding Applets are:
      • Applets can not access local files.
      • Applets can not run native code.
        • Turning off native code is a good idea when testing your application. You can disable native code in one of two ways:
          nM> env set USENATIVE NONE
          or
          $ nm -DNONATIVE=TRUE
          nM>
      • The only remote server accessible is the one from which the applet is launched.
      • Not all properties from System.getProperties() are available.
      • See http://java.sun.com/ for more information on Java Applets.
Don't Make This Mistake:
Applets can be very browser-dependent and have a number of security restrictions. You may want to consider using Java WebStart instead.