There may be a middle option ... separate the operator's manual from
the installation / maint / troubleshooting / detailed / programming
guide or whatever you want to call it.

If a one page describes how to perform most functions (I have seen
'howto' lists and tree navigation diagrams work well) then THIS
becomes the operators manual. This would keep the spirit of the
requirement.

When I am flying I do not want to have a large manual or navigate a CD
to learn how to perform an operation. It is probable that if I am in
this situation (learning equipment whilst airborne) then I may have
other issues to deal with and I am just increasing my workload.
Scanning a tree diagram (sorry, operations manual) is an acceptable
workload and the sign of well designed equipment. Anything else is
either because (i) I am playing with details of a non-critical
component or activity and should probably stop (ii) I have failed to
be familiar with a critical operation / equipment - this is poor
planning / decision making and I should not be flying this
configuration or (iii) the equipment is not suitably designed for
cockpit operations. Jim - your equipment does not fall into category
(iii).

Construction, learning capabilities, detailed programming,
configuration &c. should be ground operations - PDF / CD / print the
sections that you need should all work well. I use this criteria for
purchasing equipment and in my own construction.

A one pager for operations would be great. I'd hate to see great
products suffer because of the need to have trees fly instead of
letting them continue to produce oxygen and fuel.

Best Regards
Steve