Previous Next        Current Page: NeXtMidas Training / Option Trees / Overview / Things to Note
Start Here   
Background   
Common Midas Concepts   
Getting Started - Part 1   
Getting Started - Part 2   
Working with Files   
Option Trees   
   - Overview   
      - What is an Option Tree?   
      - Structure   
      - Structure (Large)   
      - Things to Note   
   + Using an Option Tree   
   + Lab 1   
   + Creating an Option Tree   
   + Command Dictionary   
   + Building an Option Tree   
   + Lab 2   
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   
Applets & WebStart   
Maps & Imagery   
X-Midas Interoperability   
RMIF & Remoting   
Installing NeXtMidas   
Support & Maintenance   
File Handlers   


  • Things to Note:
    • In written documentation option trees are usually referred to using uppercase names (e.g. UCL) while their directory names are always lowercase (e.g. ucl).
    • A subdirectory in an option tree are called an area. Areas are referred to using either uppercase or lowercase names (e.g. PRIM or prim). The directory names for the different areas are always lowercase (e.g. prim).
    • The cfg area of a NeXtMidas option tree always contains the command dictionary named commands.cnf. (More on this later.)
    • To fit the package naming scheme in Java all option trees must start with a top-level nxm directory. (There are multiple ways of doing this that will be covered later.)
Java Experts Take Note:
All Java classes in an option tree use a package name of nxm.<opt>.<area>. This provides for the uniqueness although it does not follow the Java standard (which would use <tld>.<organization>.nxm.<opt>.<area>). This deviation from the standard simplifies the package names and allows commonality between organizations.