On Mon, 3 Oct 2011 12:05:01 +0000, Steve Coalbran <
coal...@HOTMAIL.COM> wrote:
>Hi Bob
>
>What on earth is a FLOWER box ?
>Can you add an example - perhaps an image of what you'd expect before &
after your planned-process ? (keep it simple for us)
/*---------Language: REXX-------------------------------------$$PROLOG*/
/* Program Name: MVSSYM */
/* Description: Return the value of an MVS system symbol, or */
/* null if not defined. (external version). */
/* Customization: None */
/* Input Parameters: 1. symbolName */
/*-----------------Changed 12-Mar-2008 by: Bob Stark -----------------*/
/* 1. Initial coding */
/*--------------------------------------------------------------------*/
Above is a very small "Flower Box"
>Is the use of dynamic areas a real requirement or just something you want
to play with.
>EDIT uses the values ZDATA,ZSHADOW for it's display but remember that this
is only the VISIBLE part of the data.
>If your flower-box has too many flower-pots in it then they won't all be
visible ?
The change history can get long, and so can the section (omitted above) that
describes in detail the syntax of the program arguments. Scrolling up/down
will cure this. I don't think I will need to scroll right/left.
A dynamic area allows me to use color, reverse video, and to design the
pop-up to match a set of specifications.
Yes, I could just customize a panel definition for each site, instead of
building the pop-up dynamically from specs. Just not as elegant for the
end-user, or as easy to get up-and-running
My real question is: Where is a simple and elegant example of managing input
fields in a scrolling dynamic area