mis/chore library
Chore for organizing work flow. version: 0.0.8. - 13.3.2019.
- Sub-ordinate of Mission, with wide operative flow capabilities. devState : 27 % - In GitHub: yes
Primary functionality: get notes-list aso data from input/clay and DB. Incoming data (clayIn) comes from customer. coders OR sample aso. Controlling work-flow and processes. Wrapper round of your small piece of code: Put your actual code inside Chore. Chore has also outside-class functions. In normal operation Chore engages #FLUX (In plan phase) 100s of times to access: Outer Dawo actions and answers in pervasive roll-mill-say-join-loop where all #LANG references will be resolved.
chore became eventually its own, independent package, and it did fly
out of dawo 1915, with it's own wings. Here will be small version of it. Chore is again growing big, but with different means.
hist: hkl 6.5.2014 0.0.1 dawo/lib "w o r k flow" methods for dawo
idea: Place ALL W O R K procedures here. Automatic- life-cycle / W O R K / messages and rolling. NOTE chore do not have own named out-buffer
Classes
- BlanketChore
- Many important dawo classes are extending Alpha class.
Properties
- choreBuf ↔ StringBuffer
-
This is for ALL chores,
getter/setter pair
-
choreComL
↔ List<
BlanketChore> -
Chores that operate in common area, outside Mission class.
getter/setter pair
- dawLibWorkReadiness ↔ num
-
using - getters -example
getter/setter pair
- pBNotNow ↔ bool
-
TODO Temporary hack.
getter/setter pair
Functions
-
choreEffort(
String caller) → void - Quick hack to run effort from test aso files. This is only access to effort. TODO dd parameters: BlanketChore chr, var _act
-
choreToEffortUserJson(
String caller) → void - QuickHack TODO add parameters: BlanketChore chr, var _act
-
doChore(
BlanketChore chr, dynamic _act) → void - main W O R K routines
-
endChore(
BlanketChore chr, dynamic _act) → void - routines, after W O R K is done
-
handler(
String _key, dynamic _inS, BlanketChore chr, dynamic _act) → void - #QUEST: Construct functions outside of Chore and use them for something. Assume that Chore needs outside-activity to organize all-Chore's. Outer functions return a String value to Map<String, String> operations. Some elementary: "execute-in-every-user-command-if-flagged" ideas. Sometimes these 11 functions are executed in EVERY occasion / keystroke..
-
initChoreSystem(
) → void - TODO devNote: == #chore, that is always in dawoApp So dawoApp uses chore to maintain it's work-projects. Initializing of chore system. Update dev-class. CalledBy: dawo_app build.
-
lowGrant(
BlanketChore chr, dynamic _act) → void - USAGE: Execution of EVENT is meant to be slowed-up.. as long as possible.
-
renderChore(
) → StringBuffer - example / testing chore ---------------------------------------------- Should show use-case of all Chore inner and outer methods.
-
sideGrant(
BlanketChore chr, dynamic _act) → void - USAGE PLAN: Run occasionally / timely, in sidebar.
-
startChore(
dynamic roller, dynamic aLog, dynamic xList, dynamic yChore, dynamic zSignal) → void - flow of chore might be like this... Functions to execute W O R K flow
-
topGrant(
BlanketChore chr, dynamic _act) → void - Function named like this, should act with highest priority.
-
uniteChore(
BlanketChore chr, dynamic _act) → void - United chore W O R K routines.