Lately there are some further discussions going on how to store data for use to create a proper user interface for a driver/client.
I'd like to inform the group about some statements.
We store UI strings in different locales for features and their record (like the 'Media Size:' label and records 'Letter' and 'A4').
We store dependencies including the messages to be shown.
Currently we do not save any other UI content. We had some draft construction at some time to learn about requirements, but moved that to a later level of the spec.
The PSI group is proposing a different way to store this information in a capabilities schema. This is currently discussed between UPDF and PSI. the ideal outcome would be a common format for the common elements between the two standards.
The current proposal includes strings needed for features and dependencies. It shows one additional entry (displayGroup), where somebody can assign a feature to a group. Looks pretty Windows related and is more or less indended to tell, which tab a feature belongs to.
3. Free standards group
I'm not too close to the Linux efforts right now, but I know that people are working hard to store all information necessary to handle printing.
I'm even further away from this group, but I know there are similar efforts going on there too.
I've heard this week that these people are working on a generic way to store UI info too.
Knowing all this I will gather some info and comment on them today in short statements, all titled 'Generic UI: ...'.
I'm happy to send that to another reflector, too, if somebody wants me and tells me how.
69 Prescott Drive
North Chelmsford, MA 01863
This archive was generated by hypermail 2b29 : Thu Mar 27 2003 - 12:32:11 EST