dawo 0.0.6

  • README.md
  • Example
  • Installing
  • Versions
  • 50

dawo 0.0.6

Learning Dart; by building complicated Dart package with many libraries. Organizing it, finding it's inner connections and developing multipurpose methods. Beginner Dart programmers kickoff to learn by developing a glorious package. Latest code in GitHub: https://github.com/heiklap/dawo


// Mission Class has wide access to data, since they have instances of
// Chore classes inside them, in choresL : List<CommmonChore>

// Example files here rolls only once, without loops, and output their data in console.
var dawoApp = new DawoApp('Play-rumba:dawoApp', 'By: dawo_example: dawoApp rolls missioms');
var rumba = new Rumba();

// This returns in addition a StringBuffer, that is not used here.
// Example apps presents output-data on windows console in flow, or in two kind of boxes. 


Get people together, let they present ideas, collect best ideas to libraries and group them meaningfully. Start building first new classes, but keep your mind open for intuitive solutions. Leave room and time to resolve, what will be the direction of this package. Practise to use Dawo by finding it's properties in editor, and think their importance in app.


First dawo version was kind of artistic mess, as a consequence of long-time brainstorming. Dawo 0.0.1 shows starter programmers confusion, and records ways and steps out of this mess to clarity and understanding. Latest code in GitHub: https://github.com/heiklap/dawo

0.0.1 demonstrates how data is messy, when it is not inside classes. But you have direct instant access to every piece of it. Check for pollution of public namespace!!

0.0.2 version was to weed out some of the material and create a couple of classes. Theme : baseStructure, base_lib, dawo_mill, connector, learn/code_snippets

0.0.3 Was for building first control-flow structure (Rumba.dance) to use Class-data inside app. Theme: Present different Mission ( = Client / customer) data and small, elementary work-flow. Chores ( 7 chores by default in every Mission). dawo_example.dart gives 14 screen-full data output.

0.0.4 Version Theme: Statistics, output, variation, versatility, documentation in doc-folder. dawo_example.dart gives 11 screen-full data output.

0.0.5 High level connections between objects, placard, glb, commonOp and states.
0.0.6 box_serve presentation and corporate.
0.0.7 Basic idea and orientation of package to resolve. 0.0.8 Incubator idea: -move first too big parts to independent packages. Maybe chore(process) and team


code_snippets, learn / copy-paste stuff:

  • aldente_func : Simple functions, including some logical errors. Can you spot errors?!
  • bat_loop : Control flow structure samples.
  • learn_stream_sync : Examples of simple Streams. So. async stuff.

app files

  • alpha : Structuring base classes. These two libraries do not depend other dawo files.

  • beta : Develop common properties, that other libraries should depend on.

  • dawo.dart : main file, exports : dawo_src.dart.

  • dawo_app : DawoApp class, handles Missions and keeps out-put-buffers in Map.

  • dawo_src : File created by stagehand plugin app.

  • mill : Plan: processing commands orderly, all they in row, by given priorities.

  • rumba.dart : Rumba classes .dance method runs here dawo's control-flow (once)

  • shower.dart : presentations on console, mostly box-shaped. src/box_serve.dart makes it better!

  • tools : Helper tools, sleep, stamps, lists aso.Helper functions for cl (command line)and screen output.

  • mis/missions : Chunk of command-processing between app and chore. Caring Chores. Missions keep and process data ( #clay) of their favorite area.

  • mis/chore : Start of bigger "job" / "chore" for real-world-work. Imitating functionality of other, bigger, same kind of library.

  • mis/effort.dart : Human activities, chores sub, main user-activity and presentation.

  • mis/equipment.dart : Controlling material resources for Mission and Chore.

  • corp-folder has corporate, affair, resolve and store classes.

  • corp/connector.dart Connecting ( as #client's) app - mission - chore together, mediating them. Seeking deep, inner connections of objects.

  • clay-folder has data

  • (? dawlib_coll : Resources. Examples and hacking material of Dart collections. Missing / todo)

  • dawo_dev : Classes and data, that help in developing this package.

  • src/box_serve gives frames for box_shaped cl outputs.

  • src/glb keeps global variables.

Creating Dawo variables in new file:

//  create instances of classes::
var dap = new DawoApp('exampleApp', 'Testing in dawo_example');
// play with them in IDE:
dap.   //  dot notation gives you hint of classes properties.
var mission = new Mission('#name','#state');  //  #state  ? :)

var ch = new Chore('#name','info');
// play with them:
///  connector is in very early state
var connector = new Connector('name','info');

// Using Dawo in your web app: (Dawo do not include HTML-code)

Add to your pubspec.yaml:
  dawo: 0.0.6
  browser: ^0.10.0
  dart_to_js_script_rewriter: ^1.0.1
//  your main.dart
import 'dart:html';
import 'package:dawo/dawo.dart';
import 'package:dawo/rumba.dart';
import 'package:dawo/dawo_app.dart';    
main() {
  //  Create classes as above. Or copy code from: Usage:
  var dawoApp = new DawoApp('Pplay-rumba:dawoApp', 'By: dawo_example: dawoApp rolls missioms');
  var rumba = new Rumba();
// Run code in browser and check console output: Ctrl-Shift-i 
// Or make html templates that catch output to text fields / elements.

About variable names and Classes in Dawo

Play in IDE editor with alphabet: a..z to see, what variables are available. See how common namespace might become polluted with unnecessary stuff, and try to find a way, to organize them/ your variables to meaningful classes.


goals, teams, temps
morn, night, day 
dev, make, init 

Test objects in code_snippets-folder / learn... -section. These files might be best, when copy-pasted and studied in computer.

Joker.., aldente...  bat...

sleep(), start..()  

ride....()   roll(....) 
// Watch: init.. build.. roll.. show.. done method-cycle.

Features and bugs

Please file feature requests and bugs at the issue tracker.



  • Box_serve console presentation.


  • Effort, diagonal and schedule console output.


  • Console output of mission, chore, dev; in box-form.


  • Rumba.dance() method rolls mission-chore data.


  • Classes are ready but no client data or roll-all.


  • Elementary messy data, waiting for pruning and classification.


// Copyright (c) 2017, Heikki K Lappalainen. All rights reserved. Use of this source code
// is governed by a BSD-style license that can be found in the LICENSE file.
///  *  dawo_example   dawo version   0.0.6.  -  27.11.2017
///  *  dawo_example creates 28 screens of console output data presentation.
///  * Find:  :con: :connector: :opCom:  :corporate:

import 'package:dawo/dawo.dart';

///  watch difference, when importing dawo/dawo_src.dart
///  dawo_src only #imports all dawo files except dawo.dart
///  dawo.dart exports: export 'package:dawo/dawo_src.dart';


import 'package:dawo/alpha.dart';
import 'package:dawo/beta.dart';
import 'package:dawo/dawo_app.dart';
import 'package:dawo/shower.dart';
import 'package:dawo/rumba.dart';

import 'package:dawo/mis/chore.dart';
import 'package:dawo/mis/missions.dart';

import 'package:dawo/corp/bind.dart';
import 'package:dawo/corp/connector.dart';
//  import 'package:dawo/tools.dart';
import 'package:dawo/src/glb.dart';

//  Unused package is marked with grey, and #warning.
//  import 'package:dawo/mill.dart';

//  You can use any name for classes, that you create:
//  var da = new DawoApp('exampleApp', 'Testing in dawo_example');

/// Mill class is planned to be method runner / scheduler of dawo.
//  var mill = new Mill();

//  Example, how extra instance of mission is created:
//  var missionX = new Mission('Mission-class', 'example:dawo_example');

//  Made by Google Stagehand automatically, when creating a new package.
//  This serves as an example of class, and user can develop it further.
var awesome = new Awesome();
//  When you try code below, you can see 6 properties of awesome class.
//  awesome.

//  Used once here to run method roll()
var ch = new CommonChore('ChoreInDawoExample', 'Test-Chore');

//  create classes, that do not already have an instance inside dawo::
var dawoApp = new DawoApp(':play-rumba-test:dawoApp',
    'By: dawo_example.dart: dawoApp rolls missioms');
var rumba = new Rumba();

///  Data fields:
///  Information of #user for :con:  :opCom: and :corporate:
Map<String, String> placardM = {
  'actor': 'D-example',
  'sender': 'Dawo example',
  'receiver': 'D-ex-loops',
  'command': 'D-ex-cmd:',
  'msg': 'D-ex-msg:',

///  Local variables for this presentation.
bool _pB = true; //  Boolean value used to control printing.
String dexS = ':d-ex:'; //  Prefix for print messages and easy find.
int dexC = 0; //  counter for activities in this example.
String connectorMsg = ':ORDER of :OUTER process is :ANY KIND ';

///  For 0.0.6, main function is 17.11.2017 separated to small functions.
///  In dawo package there is no main-function. Only in example files.
///  Every dart program starts it's execution from main method.
main() {
  var sw = new Stopwatch()..start();
  DateTime start = new DateTime.now();
  ///  Call function that adds #actor and #count to this String and prints it.
  exInfo('==>>==>>==   dawo_example    ==>>==>>==');

  print(':glb:print:states:  set to false. only :buf: used');
  print('-- Change print status: glb.setGlbPrint(true or false) ------');

  exInfo('==>>==>>==   dawo_example  awesome: ${awesome.isAwesome}');

  //  example of empty function, that can be modified to do #things!!

  ///  All connector activity is marked with: :connector: in output.
  //  exInfo('==>>==>>==   dawo_example calling :connector:    ==>>==>>==');
  //  Later:  connectorOp(dexS); //  function below.

  // This method also returns a StringBuffer, that is not used here.
  rumba.dance(dawoApp); //  15 screens of output.

  exampleMethodsPlay(); //  Add more 13 screens output.
  dawoApp.box(dexS);  //  2. time here-

  exInfo('    ==<<==<<==    dawo_example done    ==<<==<<==');

  print("Executing dawo_example.dart took: ${sw.elapsed}us");
  DateTime stop = new DateTime.now();
  print(' \nStoptime::  $stop');
  print('FlowServe calls::   $flowI ');

} //  -----  end of main.

///  To allow easy-run of these 8 separated activities.
void exampleMethodsPlay() {

  ///  Calling Class scheduleBox method, in dawo/shower.dart
  ///  Nice screen of collected data in boxed for,


  exInfo('==>>==>>==   calling choreEffort---------- dawo sets, goals:');
  exInfo('    ==<<==<<==    calling choreEffort done  dawo sets, goals:');


///  Form  message row to easy-find and print it if: _pB
void exInfo(String msg) {
  String dexCS = dexC.toString();
  //  String: -exInfo appended here, as an example. It is 16 times in output.
  String _msg = ' -exInfo $dexS $dexCS $msg';
  if (_pB) print(_msg);

///  Place where :corporate:  :opCom:  and :connector: play together.
void connectorOp(String caller) {

  connector.opJoin(placardM, connectorMsg, ':Dawo:example:');

//  TODO  #IDEA: for courier carrier, to do something really nice.
//  :courier: marks this message carriage functions activity.
void courierMessage() => print('d-ex-exmpl: * *  :courier: Mission!. * * ');

///  This class instance has been created in dawo, and it is usable here.
void exampleMission() {
  exInfo('    ==<<==<<==    roll mission op/ init -open - roll: -close==<<==');
  exInfo('\n ==>>==>>==   rolling :packDawo:Mission:    ==>>==>>==');

  ///  Eventually opRoll handles all these others.
  packDawoMission.opInit(1, 'empty parameter');
  packDawoMission.opOpen(2, 'second empty parameter');
  //  calls void function that prints a String.
  //  In front of String is line feed, and another String with interpolation.
  exInfo('\n $dexS-:dw:-ex: -----------  rolling :courier:Message: ------ ');
  packDawoMission.opRoll(3, courierMessage);
  exInfo('  - -:dw:-ex: -----  rolling :courier:mission: opFunc  done ---\n');
  packDawoMission.opClose(); //  No  parameters.
  exInfo('    ==<<==<<==    rolling :packDawo:Mission: done    ==<<==<<==');
  //  When you print row below, you can see all methods.
  //  packDawoMission.

void lonelySampleChore() {
  exInfo('\n ==>>==>>==   rolling lonelySampleChore    ==>>==>>==');

  ///  Sample lonely Chore, that is created here
  exInfo('    ==<<==<<==    rolling lonelySampleChore: done    ==<<==<<==');

void sampleDawoBuffers() {
  exInfo('\n ==>>==>>==   rolling sampleDawoBuffers    ==>>==>>==');
  outBuffersPrint('$dexS dawo_example', 'no-prevent-printing');
  exInfo('    ==<<==<<==    rolling sampleDawoBuffers: done    ==<<==<<==');

void sampleJsonData() {
  exInfo('\n ==>>==>>==   rolling sampleJsonData    ==>>==>>==');
  exInfo('==>>==>>==   encoded - decoded    ==>>==>>==');
  exInfo('==>>==>>==   chore > effort > user_json render   ==>>==>>===');
  exInfo('    ==<<==<<==    encoded - decoded   done    ==<<==<<==');
  exInfo('    ==<<==<<==    rolling sampleJsonData: done    ==<<==<<==');

void connectorExampleReport() {
  exInfo('==>>==>>==   calling :connector: report    ==>>==>>==');

  exInfo('    ==<<==<<==    :connector: report done    ==<<==<<==');

void schedulePlay() {
  exInfo('==>>==>>==   calling :schedule:play:    ==>>==>>==');
  exInfo('    ==<<==<<==    :schedule:play: done    ==<<==<<==');

/// Empty, or message method
void noteToMe() {
  //  lol  You can not access local private variables.
  dawoApp.printControl(false);  //  no top-level getter dawoApp ??
  connector._pB = false;
  dev._pB = false;
  mill._pB = false;
  missions._pB = false;
  shower._pB = false;
  tools._pB = false;
  rumba._pB = false;

///  For to check variables visibility.
void wordPlay() {
  //  Play with variables: watch something from every file
  //  base
  // baseLibMotto

  //  baseStructMotto;

  //  chore
  // choreBuf

  //  dawo
  // dawoBuf

  //  app  3 variables
  // appMap;

  //  dev  17 variables
  //  devBlame;

  //  flow*  2 variables

  //  mill  4 variables

  //  DawoMill

  //  mission
  //  Mission  class

  //  out  15 variables
  //  placard* : 1

  //  toolsActive;

  //  play with classes

  ///  testing dawo
  //  daw... ok

  //  render   //  there are 5 render-functions

  //  No, too much noise.
  //  printBuffers();

///  Empty not used method.
void playDawoSrcDart() {}

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:

  dawo: "^0.0.6"

2. Install it

You can install packages from the command line:

with pub:

$ pub get

with Flutter:

$ flutter packages get

Alternatively, your editor might support pub get or flutter packages get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:

      import 'package:dawo/dawo.dart';
Version Uploaded Documentation Archive
0.0.75 Jan 8, 2018 Go to the documentation of dawo 0.0.75 Download dawo 0.0.75 archive
0.0.7 Dec 18, 2017 Go to the documentation of dawo 0.0.7 Download dawo 0.0.7 archive
0.0.6 Nov 27, 2017 Go to the documentation of dawo 0.0.6 Download dawo 0.0.6 archive
0.0.5 Nov 6, 2017 Go to the documentation of dawo 0.0.5 Download dawo 0.0.5 archive
0.0.4 Oct 16, 2017 Go to the documentation of dawo 0.0.4 Download dawo 0.0.4 archive
0.0.3 Sep 25, 2017 Go to the documentation of dawo 0.0.3 Download dawo 0.0.3 archive
0.0.2 Sep 11, 2017 Go to the documentation of dawo 0.0.2 Download dawo 0.0.2 archive
0.0.1 Sep 5, 2017 Go to the documentation of dawo 0.0.1 Download dawo 0.0.1 archive
0.0.0 Sep 21, 2013 Go to the documentation of dawo 0.0.0 Download dawo 0.0.0 archive


We analyzed this package on Jun 19, 2018, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.0.0-dev.63.0
  • pana: 0.11.3


Describes how popular the package is relative to other packages. [more]
0 / 100
Code health derived from static analysis. [more]
100 / 100
Reflects how tidy and up-to-date the package is. [more]
100 / 100
Overall score:
Weighted score of the above. [more]
Learn more about scoring.


Detected platforms: Flutter, web, other

No platform restriction found in primary library package:dawo/dawo.dart.


  • Fix analysis and formatting issues.

    Analysis or formatting checks reported 17 hints.

    Strong-mode analysis of lib/clay/user_json.dart gave the following hint:

    line: 36 col: 17
    'JSON' is deprecated and shouldn't be used.

    Strong-mode analysis of lib/corp/connector.dart gave the following hint:

    line: 335 col: 15
    The value of the local variable '_sw' isn't used.

    Similar analysis of the following files failed:

    • lib/dawo_app.dart (hint)
    • lib/src/box_serve.dart (hint)
    • lib/src/glb.dart (hint)
  • Package is pre-v1 release.

    While there is nothing inherently wrong with versions of 0.*.*, it usually means that the author is still experimenting with the general direction API.


Package Constraint Resolved Available
Direct dependencies
Dart SDK >=1.23.0-dev.11.5 <2.0.0
browser ^0.10.0+2 0.10.0+3
dawolang ^0.0.0+2 0.0.1
Transitive dependencies
path 1.6.1
Dev dependencies
test ^0.12.24+2