Abstract: A connector for connecting an add on building structure to a rim board of an original building structure, including a connector rod including an elongated hollow intermediate portion and smaller breadth externally threaded extensions extending from ends of the hollow intermediate portion. The first externally threaded extension is a length to extend through an opening in the rim board that aligns with an opening in the ledger board, and internally threaded sockets are threaded onto the externally threaded extensions at a positions straddling the rim board at one end and a supportive member within the joists of the add on building structure at the other end for holding add on building at a desired distance from the rim board and preventing rotation of the connector rod.

Abstract: A bracket includes a connector rod for mounting through aligned openings in a rim board of an original building structure and through the ledger board of an adjacent add-on building structure. The connector rod includes a stabilizer end of a length extending beyond the rim board and ledger board for connection to a support structure displaced from the rim board and ledger board. The fasteners there against the rim board, the ledger board, and a third fastener is displaced from the rim and ledger boards for connection to a supported structure.

Abstract: Communication among agile objects and context-bound objects within object-oriented programming environments, including communication across contextual boundaries, is disclosed. In one embodiment, a reference to a second object within a second context is wrapped in a proxy wrapper. A first object within a first context calls the second object via the wrapped reference. No direct reference is held by the first object to the second object. Other embodiments relate to agile objects. Agile objects called by context-bound objects execute in the contexts of their callers. The context of a calling context-bound object becomes the context of an agile object for calling of the agile object by the calling context-bound object. Direct reference to the agile object by the context-bound object is thus permitted.

Abstract: Communication among agile objects and context-bound objects within object-oriented programming environments, including communication across contextual boundaries, is disclosed. In one embodiment, a reference to a second object within a second context is wrapped in a proxy wrapper. A first object within a first context calls the second object via the wrapped reference. No direct reference is held by the first object to the second object. Other embodiments relate to agile objects. Agile objects called by context-bound objects execute in the contexts of their callers. The context of a calling context-bound object becomes the context of an agile object for calling of the agile object by the calling context-bound object. Direct reference to the agile object by the context-bound object is thus permitted.

Abstract: An object system provides composable object execution environment extensions with an object model that defines a framework with contexts, policies, policy makers and activators that act as object creation-time, reference creation-time and call-time event sinks to provide processing of effects specific to the environment extensions. At object creation time, an object instantiation service of the object system delegates to the activators to establish a context in which the object is created. The context contains context properties that represent particular of the composable environment extensions in which the object is to execute. The context properties also can act as policy makers that contribute policies to an optimized policy set for references that cross context boundaries. The policies in such optimized sets are issued policy events on calls across the context boundary to process effects of switching between the environment extensions of the two contexts.

Abstract: A method and system for editing actual work records with a start date, an end date and a work value. A period actual is entered, including a period actual start date, period actual end date, and a period actual work value. Before the period actual is stored as an actual work record, it is determined whether there is any overlap between the actual work records and the period actual. If so, any overlap between the actual work records and period actual is eliminated. Any overlapping actual work records that are completely within the period actual, i.e., with a start date and end date between the period actual start date and period actual end date, are deleted. For an overlapping actual work record that surrounds the period actual, i.e., the period actual start date and period actual end date are between the start date and end date, the end date and work value of the overlapping actual work record are modified and a new actual work record is created.