Conference vaxuum::document_ft

540.0. "<SUBCOMMAND> and "informational-name" argument" by DSSDEV::FISHER (Work that dream and love your life.) Mon Jun 22 1987 10:59

SUGGESTION:  Provide an "informational-name" argument to <SUBCOMMAND>, 
since you provide it for <COMMAND>.

Using   doctype:  layered
        devices:  mail/ln03
        template: Command Template


The "informational-name" argument to the <COMMAND> tag is very useful. 
It would be just as useful for a <SUBCOMMAND>.  By not providing this 
argument for the <SUBCOMMAND>, you may be discouraging people from 
using this feature.

Also, I feel that the informational-name argument should be place 
below the command title, in a different font or point size.  The 
em-dash technique is difficult to read at a quick glance and it 
obscures the <COMMAND> title.  The informational-name argument should 
not have an equal visual-cue status with the <COMMAND> title.


					--Gerry

    
    Re this NOTE and 539. We will look at this items in planning
    for future versions.