Beginner Dart programmer sketching class, that allows objects to
participate in #commonOperation, and connect to other objects there.
Project in early stage, a bunch of inspirational ideas, not meant
to be developed to production app. Learning process.

Monday, October 16, 2017

..is out. The quest for clarity in the structure of the package, continues. Fine-tuning details in daily basis, and using dawo dev-notes to collect ideas and to track development of work. Stopping in #big areas, and presenting there only screen-full of random demo; that is our work-safe plan. Develop highly intelligent process-system, that is duty for other packages, not for dawo. Dawo is frames around ideas. Motto: do not take too big duties to yourself. Do not get lost in too big system; plan safe heavens there.

3 days before publish went with little changes and I plan to keep 3 days off after publish, to free mind and get distance to pack. Reading meanwhile actively all kind of programming stuff. I have enough ideas to dawo for next 5 GitHub update sessions and all they seem interesting and meaningful. Dawo is on the track.

Reading daily dartlang new stuff and talks is very interesting and educating. When you done it for years, it is getting new shapes: goals and phases in learning are more clear, and my vision inside language is changing. More clarity, more speed in reading. And now waiting Dart 2.0 ..

Dawo still includes much mess, forgive that, but we really are in early stage. Reading code might be heavy, but each new commit will make it more clear.

It seems to have taken for me years to reach this peaceful state of mind;
1. Be patient, plan "dead-ends" where you can throw nice demo and leave actual production (of wanted action) to other packages that are more suited and more advanced.
2. Trust yourself, and be happy of daily learning.

About 10 improvements are on the table for next, 0.0.5 version. What is subject of days work, is most often question of intuition, and is resolved in minutes, when I study files. Removing tools to new tl-class will however be the first one. But first I'll take three days off.
.

7. DONE StringBuffers to every important class and file for output.
- this also adds visibility for variable-name

8. _h__ Start: Connector-class; Connect App-Mission-Chore classes functionality in mill-process
- in this phase this is gonna be very elementary, schematic
- At the end this is fine-graded and long development plan. ( DIFFICULT :( )

Wednesday, September 6, 2017

To see own package in pub is glorious, crossdart ( hyper-linked source code ) is deeply elegant to display source code, api docs is behind the link and link to github code, it is all there.Very elegant system, and now it is easy to start using dawo, and further it's development. Dry-publish was good to practice publishing. A very exciting event all over the place!
Code is all written about 2-3 years ago, so it is really elementary "beginners code".
And Dart's package system is deeply elegant and effective.
Picture of publishing event in windows cl window:

One file is missing, I think hist.txt was left in my dawo_old folder. Shall add it here.
Publish event was very fast and I can see my package and all links there in minutes.
Crossdart took a little longer. Bot tracking additions to pub.
Development line seems now quite clear.