fred@hpcvlo.UUCP (05/15/87)
Now that the X-ray user interface library has been released for several
months, people are starting to develop their own field editors. The
X-ray team at the Corvallis Workstation Operation of the Hewlett-Packard
Company has now put together a means by which these people may contribute
their new field editors. These new field editors will be considered for
incorporation into into libXr.a on the basis of functionality, portability,
robustness, and quality of documentation. We won't be able to serve as
a QA department for other people's code and documentation, so if we find
too many problems we'll route it back to the author for further work.
Worthwhile field editors that are not incorporated into the main library
will be included within the /usr/contrib/Xr/editors portion of the source
tree, but we (HP) will not be responsible for qualifying it or verifying
that it behaves as it is intended.
To contribute a field editor, the following pieces should be mailed
to Fred Taft (hp-pcd!fred):
1) A manual page describing the new field editor, in comparable style
to current field editor man pages.
2) The source code for the field editor.
3) An include file containing any defines and structures used
by the new field editor.
As a side issue. When a new field editor is developed, the editor
is normally assigned (by its developer) a unique inputType code,
which is placed within the inputType field of any X-ray events
generated by that editor. The Hewlett-Packard Company has reserved
all input codes in the range 0 - 0x3FFF. Editor writers should feel
free to use any numbers outside this range. When an editor is
contributed to us, we will reassign it a unique inputType number
within our reserved range.