no question to ask, all clear and interesting
congratulations for your work

>Visual FreePro introduces the ANDAL instruction, which is abbreviated as ".&&." and is short for "and also," pronounced either "and-all" or "andle" -- you choose (I find myself going back and forth between them depending on when/where I'm referencing them). :-)
>
>The purpose of the ANDAL instruction is to remove the code constraint of coding only vertically, and to make use of horizontal screen space for certain code blocks which are straight-forward and simply don't need to take up a lot of vertical screen space. Today we can use code folding for this, but the purpose of the ANDAL is to leave that code visible while removing vertical screen real-estate usage.
>
>Consider:
>

FOR lnI = 1 to 10
>    * Let the remote know it's time to process this numbered block
>    foo(lnI)
>NEXT

>
>In this example, we have a simple FOR loop with a comment and some code. To look at the screen it requires a little bit of processing to determine what's happening. By using ANDAL it can be refactored:
>
>

* Let the remote know it's time to process each numbered block in turn
>FOR lnI = 1 to 10  .&&.  foo(lnI)  .&&.  NEXT

>
>The Visual FreePro IDE will recognize this syntax and visually highlight these commands inside of their own cask. The surrounding cask will visually isolate each component making it clear in appearance that these are three separate commands. And since it is part of a FOR loop, it will also employ a natural "FOR keyword" syntax highlighting color to make it even clearer.
>
>In short, instead of just having "code folding" collapses, the Visual FreePro IDE will be able to completely collapse this sequence down to a single FOR cask indicating that there is code inside, along with the comment, so that once it is debugged and working it doesn't need to be seen unless it needs to be seen. The developer will be able to use the Visual FreePro debugger to step over these ANDAL blocks with a single line operation. In addition, if several items are collapsed all the way down, the developer can step over large blocks of code using the single line-step debugger feature.
>
>These features allow the developer to keep only those parts which are in active development as actually being open inside the source file, while providing the added benefit of allowing a follow-on developer the ability to come in and see the program flow in general outline and comment form, without being initially bogged down with all the details of the mechanics of the implementation. And the developer will be able to collapse and un-collapse these blocks during debugging or editing, allowing a truly robust set of developer tools.
>
>Everything I am providing here for information about Visual FreePro is of the general philosophy: Concepts first, then details, for within that "ownership" of philosophy, it's not just the mechanical details of the code that are known, but rather the bigger picture of what's going on. It's why people get PhD's in a wide variety of disciplines ... because they understand the philosophy of what's going on, and not just the mechanics.
>
>Please ask any questions.