Read: /doc/hist_versions.txt in gitHub to see full changes to this, and coming versions.

Blog: http://dawopack.blogspot.fi/search/label/dawo

Dependencies: Dawo is using my other package: dawolang: 0.0.1, for word recognition in connector.

Usage

// 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.
// To run dawoApp in rumba demands two imports:
import 'package:dawo/rumba.dart';
import 'package:dawo/dawo_app.dart';
/// Instance of dawoApp is already created inside package.
dawoApp.name = 'Play-rumba:dawoApp';
dawoApp.motto = 'By: dawo_example: dawoApp rolls missioms');
// or using init:
dawoApp.init(':dawpApp:daily:bundle:', 'By: :daily:bundle:test:');
var rumba = new Rumba();
// This returns in addition a StringBuffer, that is not used here.
rumba.dance(dawoApp);
// Example apps presents output-data on windows console in flow, or in two kind of boxes.

Packages shape

Purpose and direction of this package: do one clearly restricted thing and do it well.
Not commercial program; using promos, demos to imitate realWorld functionality.
Extra functionality is done by plugins that connect to other packages.

Brainstorming

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.

Practise to use Dawo by finding it's properties in editor, and think their importance in app.

Versions

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!!

// play with them in IDE:
dawoApp. // dot notation gives you hint of classes properties.
var mission = new Mission('#name','#state'); // #state ? :)
mission.
var ch = new Chore('#name','info');
// play with them:
ch.
/// connector is in very early state
var connector = new Connector('name','info');
connector.

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.

Like:
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.