9.14 Action Bar Application Design Considerations

It is hard to understand how flexible and functional an action bar application can be by just reading guides and manuals. The only real way to find this out is to set up a small prototype system and try it out. How to do this is described in Prototype an Action Bar.

The following points are things that you should consider when planning or designing applications that are to use action bars.

Prototype an Action Bar

1.  Create a process of type ACT/BAR, and include into it one RDML function called PROTO, like this:

     DISPLAY FIELDS(#AB$OPT #PD$OPT) IDENTIFY(*DESC) 

             PANEL_ID(*NONE)

2.  After keying in the RDML command, compile function PROTO to assemble the prototype action bar. This dummy function shows the values of the special AB$OPT and PD$OPT fields from the action bar and pull down option chosen.

3.  Define in the action bar control table all required action bar options, and all associated pull down choices so that they all cause function PROTO to be invoked.

4.  The prototype can then be gradually converted to a complete application by successively generating the required RDML code for each pull down option, and replacing action bar control table references to PROTO with the "real" function.

Including other advanced CUA features such as prompt key processing into an action bar application design is vital if the design is to be simple, yet highly functional.

9.14.1 Applications Least Suitable for Action Bar Implementation

9.14.2 Applications Most Suitable for Action Bar Implementation