rhyne@qaddafi.cad.mcc.com (Tom Rhyne) (09/20/90)
While attending a CAD Framework standards meeting last week I was told that there was an IEEE Standards group working on a composite standard that blended Motif and Open Look into a single presentation-management interface. That sounds like a great idea. Can anyone out there give me some further information on this effort: who? where? when? Thanx. -- === UUCP: ...!cs.utexas.edu!milano!cadillac!rhyne ARPA: rhyne@mcc.com ==== | TOM | "I found me a place where I can do good with- | Opinions are not | | RHYNE | out doing any harm." Boaz from the caves of | necessarily those| | MCC-CAD| Mercury by way of Kurt Vonnegut, Jr. ======== | of the sponsors. |
klee@wsl.dec.com (Ken Lee) (09/21/90)
In article <RHYNE.90Sep20075041@qaddafi.cad.mcc.com>, rhyne@qaddafi.cad.mcc.com (Tom Rhyne) writes: |> While attending a CAD Framework standards meeting last week |> I was told that there was an IEEE Standards group working |> on a composite standard that blended Motif and Open Look into |> a single presentation-management interface. IEEE P1201 is looking into this. They aren't getting very far, though. Apparently the best they've done so far is an API that supports subsets of the 2 toolkits, but not enough of either to be really useful. P1201 is part of the IEEE Computer Society. -- Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@wsl.dec.com uucp: uunet!decwrl!klee
preece@urbana.mcd.mot.com (Scott E. Preece) (09/24/90)
From: klee@wsl.dec.com (Ken Lee) | IEEE P1201 is looking into this. They aren't getting very far, | though. Apparently the best they've done so far is an API that | supports subsets of the 2 toolkits, but not enough of either to be | really useful. P1201 is part of the IEEE Computer Society. --- I'm not sure which of P1201's efforts the writer is referring to. Last winter the group worked for some time on a merged toolkit (called N3) that was taken as far as a proof of concept which demonstrated that it could, in fact, cover at least a subset of the OPEN LOOK (Xt+) and OSF/Motif toolkits; the effort was ended before it was determined how far the merged toolkit could be pushed. Since April the group has been working on an approach based on having a new (non-widget) API, presenting a look and feel independent abstraction of window system functionality, which can be mapped onto either native toolkit at compile time. One of the technical issues the group is facing is the technical coverage of this approach -- (1) what percentage of applications could be coded entirely in the new API, without reference to the native toolkit underneath and (2) what percentage of a typical application could be written in the new API versus what percentage in a native toolkit. Since, in fact, neither the OPEN LOOK nor the OSF/Motif toolkit covers enough window functionality to be really useful (any serious application in either is going to contain a significant amount of code reaching down to lower X layers), it is not necessarily disqualifying for the new API to fail to cover the entire problem space. Those with strong opinions on the question and (ESPECIALLY) those with experience with window system toolkits supporting more than one delivered look and feel are eagerly invited to join the P1201.1 work group meeting at the next IEEE TCOS meeting, in Seattle, 16-19 October. The group is trying to put its political wrangling behind it and move on to a very full plate of technical issues and could use all the willing workers it can get. -- scott preece motorola/mcd urbana design center 1101 e. university, urbana, il 61801 uucp: uunet!uiucuxc!udc!preece, arpa: preece@urbana.mcd.mot.com