milburn@me10.lbl.gov (John Milburn) (05/07/91)
The package contributed by HP to to the Interex exchange tape is available via anonymous ftp from me10.lbl.gov (128.3.128.110). Be sure to use binary mode. (rs :-)) A couple of the packages require C++ to compile (dvi.tar.Z, wacco.tar.Z). Binaries are provided for MH(6.7.1), HUGE(HP Unsupported Emacs), perl, and a modified /bin/sh. The rest is provided as source. If someone cares to compile dvi for the various platforms, I'll post the binaries. I don't think changes have been made to MH, patch, or perl from the std distribution, but I could be wrong as I only glanced at it. I don't know what wacco, dld and winterp do. Linkem is a tool to change identical files in a given path from distinct files into links. As always, the standard disclaimer applies: --------------- This archive contains various extentions for HP/UX. The software available here is all provided as is, and is entirely unsupported by HP and by me. Use this software at your own risk -- no guarantees are made that they will work as expected. The contributors are not responsible for any damage which may result from the use of their software. --------------- BTW: the most recent ftpd stats are: Since Oct 8 there have been 2757 external ftp connections from 1035 different hosts. These hosts retrieved 7633 files. 1026 of these files were unique. -- John Milburn milburn@me10.lbl.gov (415) 486-6969 "Curse you, Inspector Dim. You are too clever for us naughty people."
milburn@me10.lbl.gov (John Milburn) (05/07/91)
In article <12873@dog.ee.lbl.gov> I wrote: >The package contributed by HP to to the Interex exchange tape is >available via anonymous ftp from me10.lbl.gov (128.3.128.110). Be >sure to use binary mode. (rs :-)) I should have mentioned that the stuff is in pub/interex. -jem -- John Milburn milburn@me10.lbl.gov (415) 486-6969 killed a LOT of old people in my time, and I'm not above doing it again."
mayer@hplabs.hpl.hp.com (Niels Mayer) (05/14/91)
In article <12873@dog.ee.lbl.gov> milburn@me10.lbl.gov (John Milburn) writes: >The package contributed by HP to to the Interex exchange tape is >available via anonymous ftp from me10.lbl.gov (128.3.128.110). Be >sure to use binary mode. (rs :-)) > ... >I don't know what wacco, dld and winterp do. > As the author, I happen to know what WINTERP does: ============================================================================== WINTERP: An object-oriented rapid prototyping, development and delivery environment for building user-customizable applications with the OSF/Motif UI Toolkit. ------------------------------------------------------------------------------ WINTERP is a Widget INTERPreter, an application development environment enabling rapid prototyping of graphical user-interfaces (GUI) through the interactive programmatic manipulation of user interface objects and their attached actions. The interpreter, based on David Betz's XLISP, provides an interface to the X11 toolkit Intrinsics (Xtk), the OSF/Motif widget set, primitives for collecting data from UN*X processes, and facilities for interacting with other UN*X processes. WINTERP thus supports rapid prototyping of GUI-based applications by allowing the user to interactively change both the UI appearance and application functionality. These features make WINTERP a good tool for learning and experimenting with the capabilities of the OSF/Motif UI toolkit, allowing UI designers to more easily play "what if" games with different interface styles. WINTERP is also an excellent platform for delivering extensible or customizable applications. By embedding a small, efficient language interpreter with UI primitives within the delivered application, users and system integrators can tailor the static and dynamic layout of the UI, UI-to-application dialogue, and application functionality. WINTERP's use of a real programming language for customization allows WINTERP-based applications to be much more flexible than applications using customization schemes provided by the X resource database, Brunecky&Smythe's Widget Creation Library (WCL), or OSF/Motif's UIL (user interface language). An environment similar to WINTERP's already exists in the Gnu-Emacs text editor -- WINTERP was strongly influenced by Gnu-Emacs' successful design. In Gnu-Emacs, a mini-Lisp interpreter is used to extend the editor to provide text-browser style interfaces to a number of UN*X applications (e.g. e-mail user agents, directory browsers, debuggers, etc). Whereas Emacs-Lisp enables the creation of new applications by tying together C-implemented primitives operating on text-buffer UI objects, WINTERP-Lisp ties together operations on graphical UI objects implemented by the Motif widgets. Both achieve a high degree of customizability that is common for systems implemented in Lisp, while still attaining the speed of execution and (relatively) small size associated with C-implemented applications. Other features: * WINTERP is free software -- available via anonymous ftp from export.lcs.mit.edu. * Portable -- runs without porting on many Unix systems. * Interface to gnuemacs' lisp-mode allows code to be developed and tested without leaving the editor; * Built-in RPC mechanism for inter-application communications; * XLISP provides a simple Smalltalk-like object system. * OSF/Motif widgets are real XLISP objects -- widgets can be specialized via subclassing, methods added or altered, etc. * Automatic storage management (via garbage collection) of Motif/Xt/X data. * Contains facilities for "direct manipulation" of UI components; You may obtain the latest released version of the WINTERP source, documentation, and examples via anonymous ftp from internet host export.lcs.mit.edu (18.30.0.238): in directory contrib/winterp you will find the compress(1)'d tar(1) file winterp-???.tar.Z. (??? represents the version number). Slides, papers and further documentation can be found in directory contrib/winterp/papers. There is also a mailing list for WINTERP-related announcements and discussions. To get added to the list, send mail to winterp-request%hplnpm@hplabs.hp.com or hplabs!hplnpm!winterp-request. For discussions about XLISP, see the USENET newsgroup comp.lang.lisp.x. ------------------------------------------------------------------------------- Niels Mayer -- hplabs!mayer -- mayer@hplabs.hp.com Human-Computer Interaction Department Hewlett-Packard Laboratories Palo Alto, CA. *
mjs@hpfcso.FC.HP.COM (Marc Sabatella) (05/16/91)
>I don't know what wacco, dld and winterp do.
dld is presumably the dynamic linking package by W. Wilson Ho described in the
April 1991 Software Practice and Experience. It provides a fairly convenient
interface to allow a programmer to dynamically load and execute new code. It
is similar in concept to Domain's loader_$ functions, SunOS's dlopen(3X),
or the shl_load(3X) in HP-UX 8.0. The primary advantage of the dld package is
that is is much more intelligent about "unload" operations; it's primary
disadvantage is that it doesn't tie into the shared library scheme of the
systems on which it runs.
--------------
Marc Sabatella (marc@hpmonk.fc.hp.com)
Disclaimers:
2 + 2 = 3, for suitably small values of 2
Bill and Dave may not always agree with mejenings@hpfcbig.SDE.HP.COM (Byron Jenings) (05/18/91)
Marc Sabatella <mjs@hpfcso.FC.HP.COM> writes: |>I don't know what wacco, dld and winterp do. |dld is presumably the dynamic linking package by W. Wilson Ho described in the |April 1991 Software Practice and Experience. It provides a fairly convenient |interface to allow a programmer to dynamically load and execute new code. It |is similar in concept to Domain's loader_$ functions, SunOS's dlopen(3X), |or the shl_load(3X) in HP-UX 8.0. The primary advantage of the dld package is |that is is much more intelligent about "unload" operations; it's primary |disadvantage is that it doesn't tie into the shared library scheme of the |systems on which it runs. Fairly close guess, except that dld isn't based on any of the above systems. It was developed independently back in the HP-UX 2.0 days. It also provides an unload capability, allowing you to remove code that you're no longer using. wacco is a parser-generator that generates a recursive descent parser with automatic resync on parse errors from a grammar spec. It tends to generate much better error messages than a yacc-based compiler would. wacco stands for "why another compiler compiler?".