.
                 TYPICAL PROGRAMMING USE
                 =======================
.
Generic programming situation...
.
      "I want to do X... how to do it?"
.
      "Well, I would need to know A, B... C...
             and D... maybe an E..."
.
Now where does this A thru E information come from? Typically
 most if not all of it comes from .properties.
.
Then, how to implement it now that we have our data?
 we typically SET some .properties. It might involve creating
 and using several forms, but, you change properties whether
 a few or a whole bunch...
.
*most* if not all of the process involves:
1) arranging buttons,listboxes,labels to represent it faithfully
2) getting .properties
3) setting .properties
.
and yes, in the context of a larger software project, file
manipulation in and back out is a given.
.
with enough thought and planning put into making the forms and 
 controls, I always found it sort of "naturally" breaks
 up the bigger overall programming task; yes, there is always
 "that one button" with a couple hundred lines of code behind
 it on larger projects... strategy?
 Try to "make" that into another FORM, which would spread it
 out over controls and break the process down more.
 Perhaps this isn't something the end user "needs" to see and
 watch; but if it serves to break down the large process into
 more manageable chunks of code by having the extra form and
 controls on it, then i vote for that.
.
PROGRAMMING:
 I find myself working on the TAKKY engine itself, following
 this mantra. I am about to implement "colored TEXT" property.
 I need a new .property, its for setting the color of the .text,
 I suppose I will call it ".textcolor".
 I "make" this .property "real" by adding it to the
 "templates" and "templatesCANNED" file(s) so its automatically
 available.
 right after I get the '.text' property?
 I will 'GetMakeProperty' on this new '.textcolor' property.
 (this allows me a handy time to add a default setting, BTW)
 Then? I will go about *using* this new .property where I want.
 .
