corp/corp library

Classes

Affair: conduct? affair!! Second or third alternative to operations, besides :corporate: Global operations. Some dawo #operation could relay on these. Order: #actor #sender #receiver #command #msg Early development state, idea: 15% This can be #sub-process, that normal rollOp uses. #Connector may give this extra power and connect to other operations. For that, here should be added fields. IDEA: Change this name to class CoOp. So why not: Coup.
Bind: Class Bind keeps and handles message-based bindings between objects.
Collector: Construct almost same class: but for collecting data. Would like to extend this from Connector: class, but it do not have a none argument constructor. .. but Connector do not have .. howTo:class extend class that have constructor with arguments?
Connector
CorpInterfaceBasis: interface-Base class for corp classes, serves more like a model to further develop more complicated classes. users: affair, bind, corp_interf, corporate, store
Corporate: Here objects work together after #connector joins them to system. usage: howTo:mixin hkl: extended class should not have mixins inside only extenders have mixin
CustomerBasis: Sample for Customer cass
Resolve: Solve word-command searches and validating for bind - bing and connector.
Store

affair ↔ Affair: getter/setter pair
bind ↔ Bind: getter/setter pair
connector ↔ Connector: Create instance of Connector.
getter/setter pair
connectorBuf ↔ StringBuffer: Buffering out-data ( #clayOut )
getter/setter pair
connectorMotto ↔ String: This other motto is just for to get more visibility to WORD: connector.
getter/setter pair
corporate ↔ Corporate: Creating instance.
getter/setter pair
resolve ↔ Resolve: Instance, although I remember reserving WORD: #res for something else.
getter/setter pair
store ↔ Store: Create instance of Store
getter/setter pair