1. Providing the Missing Pieces by The Master's Touch

2. Providing the missing pieces Creating an application no longer implies the use of one language or one application environment Identify the need Develop, or locate a software solution(s) Implement the complete solution that best serves the end-user.

3. The “Needs” identified I needed to be able to enter “text” (notes) in an environment that supported word-wrap, formatted text (fonts, colors, paragraphs, and prehaps spell checking). I needed more flexibility than “msgbox” provided – something that supports customized responses (more than OK, Yes, No, Abort and that could serve as a replacement for the fnDialog$ function found in fnSnap). I wanted to utilize windows controls for standard windows tasks (File Open, File Close, File Location). I needed information stored in the windows registry.

4. Implementation Goals Create tools that are usable in all versions of Business Rules. Utilize a consistent interface for communicating between applications. Design the tools to provide the maximum flexibility for implementation – Screen location – Content – Features – Ease of use

5. Tools currently released BRGrid – supports input from a formatted text file OR read directly from an internal BR file. Display is a grid with sort, filter, and find features. It allows selection of one or more rows for subsequent processing. BRRegister – allows you to read (and write if desired) entries directly from/to the Windows Registry Calendar – a graphic calendar for date selection (allows keyboard and mouse controls) File Open/Save – presents the standard windows dialog allowing the user to select the location and name of the file. Location Selection – useful in allowing the user to designate a location to be used for installations. This tool indicates a path but not file names.

6. Tools currently released Help Tips – designed to present the familiar “did you know” programming tips. (George uses this for field help.) Without parameters, this program functions as a viewer for the published BR errors.txt file. RadioChk – presents selections using radio dots, checkbox, or buttons with instructional message. SpellCheck – text entry with options for spell checking, find/search, supports text and RTF document formats (some limitations), word wrap and more.

7. Tools currently released Viewer – a read-only display developed to present formatted text, removing the ability to alter content (PFE allows user to change the text), with a small sized executable. Player – allows you to integrate sound clips in your BR application. – More ideas present more solutions and greater flexibility in existing tools MenuHelp Password

8. Features worth noting Command line interface User defined location and appearance, by positioning relative to BR screen, or absolute positioning on the display. Variable rows and columns supported in BR 4.1x User defined content Small executable size (quick loading) Switches on the command line may appear in any order.

9. RadioChk.exe This tool was originally designed as a direct replacement for the fnSnap “fndialog” Selections were expanded to include radio dots, check boxes, and the traditional buttons, limited only by screen size. Features include: – Customized colorization – User defined number of columns – Pre-selection of options (one or more) – User defined caption, message, options – Message Box (no options)

10. RadioChk.exe This is the original output of fnDialog$.

11. RadioChk.exe This is the modified output of fnDialog$ using RadioChk. Note that the message is centered on the BR screen!

12. What does it take to use RadioChk? The text above (red) should appear on a single line in a text file. This file will be referenced by the -F parameter. A sample command line is shown in blue below. -B999 identifies the result file name (DBDE999.txt) -XB indicates the use of buttons -Y4 indicates that the 4th line of the file (-F) should be used -D350 defines a fixed width for RadioChk

13. What does it look like? The next slide will demonstrate the various styles of output that RadioChk can produce. Only one character is different on the command line to indicate which style to be used. The output will be based on the text and command line presented on the previous slide.

14. RadioChk screen shots

15. Each of these screens was produced from an identical command line with one exception! The -X parameter was changed from -XB to -XC to -XR.

16. What does the BR code look like? To call RadioChk from within the BR program, you execute a system call 10000 execute "sys -w C:\BRAG\...\RadioChk.exe -B999 -Fcommandfile2.txt -XB -Y4 - D350" To obtain the result, read the file created by the -B parameter above. A full discussion of the various options is contained in the documentation. Using the example, the result file will be written to the same location as the executable file. (The dots in the example represent whatever path may be used) 10010 dim longstring$*300 10020 sleep(.25) ! allows the file to be written and closed by RadioChk 10030 open #100:"name=c:\brag\...\dbde999.txt",display,input 10040 linput #100:longstring$ 10050 close #100,free: 10060 ! check for unexpected exit from exe 10070 if pos("TIMEOUT,CANCEL,ESCAPE",uprc$(longstring$))>0 then select=0: goto abort 10080 ! buttons and radio controls have only one response 10090 x=pos(longstring$,"1") 10100 select=x ! the xth button was selected 10110 abort: !

17. What results do I get? Should you use the Checkbox format, the result would have to be analyzed differently since multiple items may be selected. The routine to determine which choices were selected in the BR program might look something like the lines below: 10200 for i=1 to len(longstring$) 10210 if longstring$(i:i)="0" then nextitem 10220 ! do whatever you need done here 10230 ! with the choice that was selected 10240 nextitem: next i "0" indicates the choice was not selected, "1" was selected

18. How flexible is RadioChk? RadioChk offers even greater flexibility than the original fnDialog$, as the choices are not limited to three options. You are limited only by the physical screen size. Using the additional switch on the command line: -Z4, the choices are spread over 4 columns.

19. Changing the appearance The example below utilizes the additional switch: -Z3 -W120 to force the column widths to a fixed 120 pixels.

20. Just a Message, No Selections RadioChk can also be used to provide information that requires no response from the end-user. In this case the message is displayed with an OK button. The “paragraph appearance” is accomplished by inserting “\n\n” in the single line text in the file specified by -F.

21. Advanced Capabilites The “Advanced Capabilities” include the ability to colorize the text or choices. This is done by using ^ at the beginning of each section followed immediately by the RGB color code expressed in hexadecimal representation. Color should be used with care or it loses the impact. ^FF0000This report will print all claims for the selected policy by year.\n\nThe demonstrates the use of RED text.|Print Select Policies from a list|^990099All Active Policies|Recently Terminated Policies

22. “Take Aways” Ability to use external tools to provide a complete solution to the end user. Confidence in your ability to think of new ways to present your application to provide a more complete Windows appearance. Using the GUI of BR version 4.1x is only part of a complete solution.

23. Workshop Exercise Provided: A census file in CSV format, BR (any version you choose), a copy of brctrl.dll and RadioChk.exe. This practical exercise is the basis for tomorrow's exercise using BRGrid. Today, using the census.csv file, create a BR program that calls RadioChk to allow you to select one or more column headings. 1) You should NOT need to create any files (except for use with -F). 2) You should NOT hard-code any values in the BR program. 3) You must be able to explain the logic to the group. 4) All column headings must be available for selection.