module Fox

This is the detailed mapper constructs for FXRuby.

Internal Docs

Note that normally you should not need to know these details.

Excution Flow

when you declare fx_app and all the nested delacrations, they are initially noted in a tree of OS (OpenStruct) objects, and then later the actual underlying FXRuby (and subsequently, FOX Objects) are created. At this point the resultant objects are plugged into the OS objects so they can be referenced.

So there are 3 phases: # Construction of the OS tree (through your declaractions) # Construction of the FXRuby objects # Construction of the underlying FOX Objects at activation time.

A stack-based method is used to keep track of all of this during the construction of the OS tree.

Issues

For many FOX / FXRuby operations, you will need the FXApp object. If you used full composition (via fx_app), the base object will be the FXApp object. If, on the other hand, you used compose inside of a declared FXRuby-derived class, base will be set to the first declared component.

Normally this is not a problem, unless you use ingress_handler, in which case it will not know how to find the FXApp object.

Conventions

NOTE WELL

This file is generated by fxruby-enhancement.
Do NOT modify this file. Modify the ERB template
file instead, and run 'rake scrape'.