because the result of the EVAL or script feeds a queue of information to a list format builder class that then returns a string for use with format…
it assumes the user is going to define their own window control views using a GUI View manager.
the classes are already built… the last step is the little list format window for the user to select the fields to view.
The list formatter is to provide a basic view of a list.
Coming from an accounting back ground i can tell you that the end user has a VERY VERY short attention span. Dont put more that a few options in front of them or me…
At the moment we are only testing an evaluate compliant procedure to set some basic properties on a flat queue.
The same procedure can also be processed by an expression engine for more complex statements.
That wonderful example looks very interesting with a comprehensive model and certainly im sure some parts of it would be very valuable for developing runtime list box format solutions.