attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2600.0" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT size=2>We have spent a bit more time on the design of a user interface structure and think this should be the proposal to discuss.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>1. We have moved the user interface section to the Locale schema.</FONT></DIV> <DIV><FONT size=2>that allows a different UI for different locales (think about Arabic, Hebrew, Asian, etc.).</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>2. The design units are pixel.</FONT></DIV> <DIV><FONT size=2>The developer of a device description is strongly recommended to follow a standard VGA (640x480).</FONT></DIV> <DIV><FONT size=2>This should leave enough room for design.</FONT></DIV> <DIV><FONT size=2>Higher resolution are expected to go with the designed positions.</FONT></DIV> <DIV><FONT size=2>If a driver knows about the screen resolution and it's lower than VGA, it could downsize by recalculating the values. Therefore it needs to rely on a reference resolution.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>3. As you can see in the latest design, there is a Logo attribute to the DeviceConfiguration element of the device configuration schema.</FONT></DIV> <DIV><FONT size=2>This is supposed to be a file name reference for one picture and would typically be used for a company logo.</FONT></DIV> <DIV><FONT size=2>When you check the Control element you see that you can use that picture everywhere in the UI, even multiple times.</FONT></DIV> <DIV><FONT size=2>The only supported picture format would be JPEG.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>4. A Configure dialog like any other dialog considered part of Device Properties is not part of a device description. It is a generic dialog created by the driver by reading and interpreting the device's configuration files. </FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>5. Composite features can be handled as any other feature in the UI design.</FONT></DIV> <DIV><FONT size=2>As we discussed the driver may offer a subdialog to view and/or edit the components of a c.f. as well as to add a new set of components or remove a user defined one.</FONT></DIV> <DIV><FONT size=2>This functionality is supposed to be supported under Device Properties and cannot be influenced by the UI design.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>6. A dialog for managing custom media sizes is as well considered part of Device Properties and not available for UI design.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>7. As you can see a PushButton can be specified as a special predefined button (OK, Cancel) or to open a subdialog - again a predefined dialog (About) or any of the UPDF design dialogs (by referencing the dialog ID).</FONT></DIV> <DIV><FONT size=2>One button can only open one dialog. If you think further about this you see that tabs on tabs are not possible.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>9. The order of the dialogs is supposed to be:</FONT></DIV> <DIV><FONT size=2>system dialogs, generic driver dialogs, UPDF dialogs in the order they are designed.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>10. Labels</FONT></DIV> <DIV><FONT size=2>As you can see the latest design show a Label element under some controls.</FONT></DIV> <DIV><FONT size=2>That means you are absolutely free in designing the position and size of any feature control (like a combo box) and its label. Regards from Murphy!</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Quintessence:</FONT></DIV> <DIV><FONT size=2>If we'd allow a UI design as part of the UPDF specification, we consciously limit ourselves to a certain set of functionality, as every driver is expected to interpret all tags properly.</FONT></DIV> <DIV><FONT size=2>However the UserInterface structure will certainly be optional. And a driver is allowed to ignore any designed section while working with its own design.</FONT></DIV> <DIV><FONT size=2>We do not think of allowing multiple user interfaces per locale, but just one.</FONT></DIV> <DIV><FONT size=2>While the design screen is supposed to be a graphic desktop of some kind, we think the structure can also be used by a command line type of desktop (which would ignore position attributes, of course).</FONT></DIV> <DIV> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Norbert Schade<BR>69 Prescott Drive<BR>North Chelmsford, MA 01863<BR>978-251-1017<BR><A href="mailto:norbertschade@attbi.com">norbertschade@attbi.com</A></FONT></DIV></BODY></HTML>