Tuesday, December 8, 2015

Certain phase in building my Dipp app: now I think to be ready for to build my first big app. Actually I need this for my learning; otherwise I might get stucked, and this brings some discipline here.

What? I'm building very thin, elementary and quick expansions (1-24) to Dipp. This "tree" is meant to be thin, for to avoid burden, which might come, when is time to make big fundamental changes. I hope to avoid later big changes, if I create in early phase some common-use methods and classes.

How am I here? Hard work, many erros, stupid slowness... and unwillingness to read howTo:s. Project Dipp seems right way to test-learn, and maybe -leave- it at any minute, if it feels so. Route is more important than goal.

How long will it be fun? Small steps policy... yep.. it means fun forever.

How is this work done? Very patiently and slowly, one step at a time. One happy hour a day.. at least. None of those 1-24 phases should take more than an hour to complete, by an exprerienced Dart programmer (not me).

How thin are they? Hermes might be just to check, that words in streams belong to 170-words lists. Server and-client parts: ready code examples with one default answer. Some might be just: -Not Ready Yet. HTTP requests are simple.. aso.

About Dipp app: Dipp is for collecting and presenting information in various ways.

About 50 classes are grouped under control of 4 main classes: DippApp,wich keeps plugins and extras. Venue,is like theatre where main flow happends, aso. Parade,which presents Frames. Worker package is used in Hermit class.

Dipp has 4 main parts / ideas:

1. Plugins, that give extra functionality and data to other apps

2. Human / labor like entities, that have their own nature, like Newton.

3. Main data-flow and UNLRS-class which gives main functionality to central Dipp classes.