Previous Next        Current Page: NeXtMidas Training / Background / NeXtMidas Benefits/Features
back
Start Here   
Background   
   - Midas Product Family   
   - What is Midas?   
   - Midas Family Tree   
   - Current Frameworks   
   - Framework Interoperability   
   - The Midas Philosophy   
   - What is NeXtMidas?   
   - NeXtMidas Design   
   - NeXtMidas Benefits/Features   
   - NeXtMidas Option Trees   
   - Why use Java?   
   - Why use Java? (ctd.)   
   - Why use Java? (ctd.)   
Common Midas Concepts   
Getting Started - Part 1   
Getting Started - Part 2   
Working with Files   
Option Trees   
Macros - Part 1 (Basics)   
Macros - Part 2 (Graphics)   
NetBeans - Part 1 (Setup)   
NetBeans - Part 2 (GUIs)   
NetBeans - Part 3 (Profiler)   
Eclipse - Part 1 (Setup)   
Eclipse - Part 2 (GUIs)   
Primitives   
WebStart   
Maps & Imagery   
X-Midas Interoperability   
RMIF & Remoting   
Installing NeXtMidas   
Support & Maintenance   
File Handlers   


  • Why Use NeXtMidas?
    Cross platform (Linux, Windows, etc)
    Web-enabled
    A single NeXtMidas macro can be deployed as a stand-alone application or via Java WebStart
    Direct support for network-protocols (like HTTP)
    Embedded Java VNC client (VNC option)
    Ease of GUI development
    Supports the use of GUI builders (such as NetBeans) and easy-to-use Java profilers (such as the NetBeans Profiler).
    Easily integrated with other Java software and Midas systems
    Can run X-Midas FORTRAN/C++ primitives and use URL syntax (XBC option tree)
    X-Midas can run NeXtMidas primitives (NeXtOPT)
    Imagery Mapping (NeXtEarth)
    Ability to serve images in Google-like manner to a remote client (PLOT)
  • Enhancements to Standard Midas Features:
    Pipes "Hot-connect" and "warm-start"
    Controls Sections Non-blocking
    Real-time Widgets No wrapper code!
    Messages Distributed queue and simple message passing
    Error Trapping Built into the macro (no TRAP command needed)
    Web Access All file-based primitives can access remote web services
    Tables Result collections
    Threads Primitives run in separate threads not processes

back