Thread View: comp.os.msdos.pcgeos
2 messages
2 total messages
Started by John Wiley
Fri, 22 Jan 1993 21:00
OOP flexibility
Author: John Wiley
Date: Fri, 22 Jan 1993 21:00
Date: Fri, 22 Jan 1993 21:00
37 lines
2599 bytes
2599 bytes
The OOP principles used in GW seem to have some amazing benefits. I'd be interested in any comments on the excerpt below (and whether such stuff should be posted here). The following description of GW's flexible UI is excerpted from the GeoWorks background info packet provided with the Zoomer press kit at CES: "In GEOS, an application's user interface is constructed using objects that generally describe the interactions the application needs from the user. For example, in a word processor, the application needs a user interface element to tell the application when the user wants to change the current test style to bold. The application does not need to know how or where that user interface element appears. In GEOS, a GenTrigger[tm] object would be used to describe this element in the application. The application does not know (or care) whether the "bold" GenTrigger is implemented as a menu item, a tool bar icon, or a gesture with a pen. When the application is opened, the system calls the specific user interface library to map the generic objects to their specific behavior. To change the user interface, only the specific user interface library needs to be changed. Different systems can have their own "look and feel" without requiring applications to be recompiled for each. For example, a calendar program might appear on a desktop system with a standard user interface like Motif[tm]. The same application can be plugged into a hand-held pen device with a specialized user interface using entirely different representations for user interface elements (UI elements might even be replaced with gestures). The application will run in this device without modification. This is a powerful way for hardware manufacturers to differentiate their products without requiring custom application development. The GEOS user interface independence also permits a single application to be scalable in its complexity, allowing users to pick the type of interface required for their experience, from novice to professional." There are descriptions of many other aspects of GEOS in this document. If anyone here is interested in more, the entire GW "background" info document is probably available directly from GW.
Re: OOP flexibility
Author: John D. Mitchell
Date: Sat, 23 Jan 1993 20:11
Date: Sat, 23 Jan 1993 20:11
26 lines
1538 bytes
1538 bytes
In article <1993Jan22.130029.22000@crash> johnlee@crash.cts.com (John Wiley) writes: > >The OOP principles used in GW seem to have some amazing benefits. I'd be >interested in any comments on the excerpt below (and whether such stuff >should be posted here). The following description of GW's flexible UI is >excerpted from the GeoWorks background info packet provided with the Zoomer >press kit at CES: As long as credit is given and appropriate copyrights are honored then I don't see how anyone would object. But that's just my opinion. :-) [...Generic UI description deleted...] The Generic UI is, without a doubt, truly awesome. >There are descriptions of many other aspects of GEOS in this document. If >anyone here is interested in more, the entire GW "background" info document >is probably available directly from GW. You can get the new and highly improved System Software Overview directly from GeoWorks (it's something like $10 or $15). John johnm@cory.Berkeley.EDU P.S. My opinions. GeoWorks speaks for itself.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads