[comp.windows.x] N3 specification

ruthlk@attunix.att.COM (11/23/89)

I've been receiving inquiries about the N3 user interface API
proposal, and thought this newsgroup would be a good way to convey
information to those who might be interested.

N3 is one of three proposals under review by the IEEE P1201.1
subcommittee on Application Programmer Interfaces (API) for graphical
user interface software. (The other API's submitted to IEEE P1201 are
the OPEN LOOK(TM) XT+ API and the Motif(TM) API). N3 differs from the other
proposals in that it supports multiple user interfaces -- minimally,
but not exclusively, the OPEN LOOK and Motif user interfaces.

The operational model for N3 is:
	- The user interface portion of an application's source code is
	  written once, to the N3 API specification.
	- N3 Toolkit implementations would exist for each of the supported
	  user interfaces.
	- At run time, the desired Toolkit library is dynamically linked
	  to the compiled application to produce a Motif, OPEN LOOK,
	  or other look and feel for the application.

The N3 specification has evolved from both the Motif and OPEN LOOK XT+
API's by defining a class structure that supports both user interfaces.
To a significant degree, look and feel specific details have been 
distilled from the API, and are provided in an API-independent
manner by the specific toolkit implementation.

The N3 API consists of the following object classes:
	- Primitives: Button, Label, List, MenuButton, Scrollbar, Separator,
	  Setting, Text
	- Managers: BulletinBoard, ComplexDialog, Form, Frame, LayoutManager,
	  PanedWindow, ScrolledWindow, SimpleDialog, Slider, TopLevel
	- Shells: DialogShell, MainShell, MenuShell

The following is specified for each object class :
Class Name, Class Hierarchy, Description, New Class Methods And
Fields, New Common Resources, New Feature Set Resources,
Inherited Resources, Callback Information, New Actions,
Keyboard Traversal Actions, and External Routines. 
(Feature Set Resources are resources that will have effect only if the
underlying toolkit supports a particular feature. An example of such a
feature is 3D.)

People who are interested in getting a copy of the N3 specification can
send me email (ruthlk@attunix.att.com), including paper mail address, 
and we'll add you to the distribution list. In addition, there will
be an open review meeting of the N3 specification on Dec. 4 and 5 at
the Hyatt Regency Hotel in Cambridge Mass. People interested in participating
should send email to Betty Dall, ejd@attunix.att.com.

			Ruth Klein
			AT&T Bell Labs