
                                    IDE
                                    ===
Easy: IDE stands for Integrated Design Environment.
      (and RAD stands for Rapid Application Development)
.
Just about *every* VB clone out there, has more or less the
 same/similar IDE approach. We all know what it looks like.
 Its I am sure like that for the reason that its the
 end-result of what most people want and need while IDE
 working.
.
TAKKY doesn't have that "signature" RAD-IDE "look and feel".
.
Originally, while working on the basics, my program did not
 have access to forms, labels, textboxes, listboxes. I would
 create a def'n file with (the LINUX version of) NOTEPAD.
 Then I would fire up the TAKKY engine, and see how it was
 working. I could switch between NOTEPAD and the program,
 seeing my WYSIWYG results.
.
I honestly think every user should, at some point, sit down
 when not rushed... and just *play* with making a simple
 def'n file, and seeing it fire up under TAKKY and what it
 does. Looking at a project-maker one-form-startup def'n
 file, before TAKKY gets to it? Is the PERFECT place to
 start; you can easily NOTEPAD a start up form.
.
slowly change properties and see the results. You can easily
 create controls one at a time, and add and change properties
 and see the instant results. But, by working
 NOTEPAD/RUN-TIME and bypassing any IDE... you are seeing
 how EASY it would BE, to make a program edit the definition
 file on demand.
.
It reminds me of the old, original HTML editors. You work on
 what is essentially a TEXT FILE, which has characters in it
 to tell the GUI what to paint. This is the same situation,
 just a more detailed version of it. The idea is the same.
.
                       *** IMPORTANT ***
                  You do not *need* an IDE;
               an IDE is just a convenience for
                              RAD
  The Definition file, if without errors, will go *straight*
                      into run-time TAKKY 
                       *** IMPORTANT ***
.
so, I'm in the position pre-IDE I dont have enough TAKKY
 done that I get access to forms and controls to use in the
 TAKKY engine, and I need something faster than NOTEPAD-ing
 it.
.
This caused a "fork" in the project. I tried (with limited
 sucess, BTW) to manage both an IDE version and a RUN-TIME
 version. I would inevitably end up "working" on the GUI
 engine routines, then have the awkward "which fork did i
 work on *that* in??" mouse chase later on.
.
this FORK nonsense was unmanageable; I think this went on
 from about 002 through before 005.
.
What was "better", was by version 005, I had learned how
 little I had to change, to go from IDE to RUNTIME. I found
 I was able to "unify" the forked IDE and RUN-TIME code.
.
so now? you will see the 'ide-sw' in the global variables
 header...
.
     ide-sw = 0 'this is RUN-TIME
     ide-sw = 1 'this is IDE
.
if you are working on the programming, and decide you want
 to move something or change a few colors, you simply change
 the 0 to a 1 on that line, and RUN it... its automatically
 IDE mode. Change the 1 to a 0? Its back to RUNTIME.
           ---------------------------------------
The main difference is, that under IDE mode... clicking on
 an object does not do what it does at runtime, which is go
 looking for your user code to execute. That is suspended.
.
In IDE mode, when you click on an object? You must want to
 view the properties, or change a property, or move an
 object. Thats the "big 3".
.
a "click" will bring up the property viewer/adjuster, which
 is self-explanatory, once you see it, I think.
.
a "right click" will activate those signature "alignment
 lines" on the object, so you can move it with ARROWS, or by
 a simple mouse click. (the mouse click? is the top left of
 the object you are moving)
.
the arrow keys are nice and smooth; you hit <enter> to stop
 arrow-moving.
the mouse click works fine, it s just slower. "clearing the
 mouse" will induce a small but irritable delay. 
.
I myself? like to mouse click to get close, hit <enter> to
 keep the mouse-click location... then i fine-tune the
 location with the arrows and hit <enter>.
.
TECH TIP: hit F1-save every time you move anything, or making
 a new object will re-paint and lose your changes. I am
 looking into an autosave idea.
.
TECH TIP: if you are just wanting to MOVE a few things,
 change some properties like colors... then going IDE mode,
 F1 to save the changes, then going back to RUNtime mode...
 works fine. 
.
Until I work out a system of automatically saving any and
 all user programming in their given click-procedures
 auto-created for them, and bringing it back in seamlessly,
 I heartily recommend you "finalize" the number of objects
 before you start programming in the click procedures. Right
 now, without the user manually cut and pasting their work?
 running another "OutputProjectBones" would wipe out their
 work.
.
so, for the pre-BETA and near future, be aware of this, and
 temporarily think of "finalizing" the objects, IE, hit the
 point you will no longer need to create and destroy
 objects... THEN you can go to make BONES and get
 programming.
