connector library

connecting ( as #client's) app - mission - chore together,

mediating them. separate objects work together in outer processes, using #LANG -specific commands to configure their proceedings. using #dawolang package in path dependency method String weightString(String _aS) checks #C messages dawo version: 0.0.8. - 13.3.2019 * devState : 15 %

devState: 30%
Hist: hkl 10.9.2017 0.0.1 dawo/lib connector.dart #name: connector ..is not nice. change to: ______ ?? #unite-6 merge-0 mix-0 blend-0 pool-0 unify-0 #name: placard : 1 !! App -mission - chore work together in same sphere, and there is something, that they have in common; abstraction layer, in which they work together.
Every #little operation is "connector-operation", and connector has
knowledge for all of them and can interact with them.
Sending messages between objects. Stance, approach
"Connector-operations" have access to certain up-level variables.
- - - companions in process * * *
Using :affair: class to operate, for :corporate: or :mission: system.
#LANG : command-words to give regulated behaviour to user actions.
ADD IS-GLOBAL bool field to :affair: classes.
Connector might change objects precedence in Mill-op.
Might trig some action in their connected sister-operations.
In roll -> loop should be phase where :con:objects are checked.

Classes

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 .. NOTE howTo extend class that have constructor with arguments?

Connector

Properties

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