The Faint Object Spectrograph (fig. 2) is a versatile instrument that can obtain the spectra of extremely faint astronomical objects in the ultraviolet and visible wavebands. A spectrum is a distribution of colors, or wavelengths, created by passing a beam of light through a prism.

A spectrum reveals the nature of the source we are viewing. We can tell whether it is hot or cold, dense or rarified, and even its chemical composition. Analysis of the spectrum also yield the remoteness and relative velocity of the object being studied.

The spectrograph works by picking up the image of a star, galaxy, interstellar dust cloud or other object that appears on the telescope's focal plane as a point of light. Then, via a system of optical mirrors and gratings that work like prisms, the light beam is spread out, from ultraviolet through the visible.

The fanned-out beam is recorded on an imaging device called a digicon detector , which counts the photons of light in each region of the beam. The resulting spectrogram is then transmitted to Earth for study. spectrographic An extremely sensitive camera capable of pinpointing and electronically intensifying dim objects.

This instrument, being built by the European Space Agency , uses the spatial resolution of the telescope to capture images of very faint objects in the universe (fig. 1) .

It is expected to be able to detect stars as faint as the 28th magnitude and will easily pick out stars of magnitude 24, which is about the best a large ground observatory can now do. Magnitude is a designation of brightness - the lower the number, the brighter the object. The dimmest star the average person can see with the naked eye are magnitude 6. The planet Venus is magnitude -4.

The Faint Object Camera has a basic focal ratio of f/96 and is capable of observing faint objects or extended structures near bright sources. This device will have four filter wheels , each containing a variety of filters in 12 positions, which can be inserted in the optical path.

The system works by gathering and focusing incoming feeble starlight on an electronic image intensifier. The intensifier's output is scanned by a vidicon camera tube and an image consisting of 250,000 picture elements is obtained. Exposure times for very faint objects could run as long as ten hours.

An f/48 focal ratio camera system will permit the camera to operate in a spectrographic mode which is ideal for studying the structure and dynamics of the center regions of galaxies, the area where black holes are thought to occur. Thus the Faint Object Camera serves as a third, general-purpose spectrograph. This mode of operation will employ fourteen insertable filters. pointing stabilization control orientation fine guidance censors Instruments used to locate and lock on to a target object, maintaining position of the telescope relative to the target.

Because of the very high spatial reolution of the Space Telescope great pointing stability is required. Two of the fine guidance sensors will be used to locate and lock on to a target while the third is free to view and precisely measure the relative positions of other stars in the vicinity.

The three fine guidance sensors are expected to produce distance measurements ten times more accurate than those done from Earth . The sensors work through a complex system of mirrors and light detectors to locate the position of a star against a background of other stars. In measuring the distance to a star, ground controllers will focus the sensors on a foreground star to transmit its position relative to the stars in the background. Similar measurements are made about six months later. Changes will indicate the distance of the star from the earth .

The precise measurement of star positions is called astrometry. Information provided by the fine guidance sensors will assist in resolving the open-versus-closed universe question. filter wheels fig. 1 (fig. 1) A diagram of the Faint Object Camera with labeled components. optical mirrors gratings digicon detector fig. 2 (fig. 2) A diagram of the Faint Object Spectrograph with labeled components. goddard ground controllers Goddard Space Flight Center/STOCC NASA center in Greenbelt, MD which will operate the Hubble Space Telescope once it is in orbit.

Once the Space Shuttle carries the Hubble Space Telescope into orbit, project personnel at Goddard will operate the satellite through the Space Telescope Operations Control Center (STOCC), located at Goddard.

The STOCC is the largest and most complex control center for a scientific satellite to date, and will enable astronomers to utlilize the Hubble Space Telescope much like a ground observatory. The astronomers typically will work at the Space Telescope Science Institute in Baltimore. They will send their observing requests to the STOCC where the Hubble Space Telescope's controllers will program the observations. The data and images obtained by the Telescope's instruments then will be transmitted to the STOCC and on to the Space Telescope Science Institute , where astronomers will study the information and present their findings to the world community.

It is expected that the STOCC will operate 24 hours per day and provide a schedule of 3,500 hours of observing time annually. By comparison, ground observatories, which can operate only during the night, offer just 2000 hours of observing time per year. An instrument capable of obtaining the ultraviolet spectra of individual objects in crowded fields. The High Resolution Spectrograph (fig. 3) will be able to use the full resolving capability of the telescope to see much dimmer objects than previous space-born instruments. Although it performs in much the same way as the Faint Object Spectrograph , it will be much more accurate because it will be using more light and resolving it into much finer increments. The High Resolution Spectrograph will be looking at only the ultraviolet region of the spectrum, wavelengths that do not reach Earth. This ultraviolet region should provide the most detailed chemical composition information yet obtained on objects in space. The instrument's extremely fine resolution will enable it to pick out individual stars in crowded fields. In addition, binary stars that cannot be differentiated optically will be resolved so that each star can be studied separately. The spectrograph will be able to study such objects as supernovae, active galaxies, bright quasars, and even phenomena in our own solar system such as planetary atmospheres, auroral activity, and the presence of deuterium in comets. Deuterium, thought to have been manufactured during the Big Bang, occurs throughout the universe. If found in comets, it will reveal more about the relation of our solar system to the original cataclysmic explosion. Measures the brightness of an object, either within a particular wavelength or throughout the entire spectrum; detects fluctuations.

The High Speed Photometer (fig. 4) is designed to provide accurate observatons of the total light from an object in space, note any fluctuations in brightness on a time scale down to microseconds, and to detail any fine shapes or structures associated with the light source. These measurements are made over a wide spectral interval, including the ultraviolet.

It is the simplest instrument of the group, containing no moving parts, and relies entirely on the pinpoint accuracy of the spacecraft's fine guidance sensors to accomplish its work. After the light of a star or other source is received, a detector can measure either the total brightness or the intensity of light within a particular portion of the spectrum.

The High Speed Photometer, in addition, will transmit accurate information on fluctuation in brightness over time. Detection of rapidly spinning neutron or other compact stars will be possible, as well as detailed data on the shape and structure of the fine spikes or flares often associated with such compact objects.

The instrument will also be of special value to astronomers in establishing calibration standards for faint stellar objects. high resolution spectrograph fig. 3 (fig. 3) A diagram of the High Resolution Spectrograph with labeled components. high speed photometer detector fig. 4 (fig. 4) A diagram of the High Speed Photometer with components labeled. Introduction article A short description of the telescope and its purpose.

Imagine trying to see the clouds from the bottom of a muddy pond. That is how astronomers describe their view of the stars and planets through the Earth's atmosphere. As advanced as astronomical technology has become, our capabilities will be forever limited by the turbulence and brightness of our atmosphere. Even the finest ground observatories, such as the one at Mt. Palomar, California, are restricted by these conditions. In addition, the selective absorption of the atmosphere, which lets in visible light and radio waves emitted by stars and planets, but excludes most other forms of energy, limits our knowledge of celestial bodies.

To open the universe to observation in infrared, ultraviolet, x-ray, gamma-ray, and cosmic ray energies, NASA launched numerous satellites, each helping to explain different processes behind astronomical phenomena. But, to date, the value of these orbiting observatories has been limited by their relatively small size and limited spectral capability.

Now, for the first time, a ground-sized observatory will be placed in orbit to view the universe in visible and ultraviolet light unobscured by Earth's atmosphere.

Called the Edwin P. Hubble Space Telescope , the new observatory is a NASA-wide and international cooperative effort . Its name honors Edwin P. Hubble (1889-1953), who discovered that the universe extends far beyond the Milky Way galaxy.

The Hubble Space Telescope will weigh about 25,000 pounds (11,300 kg) and will have a length of 43 feet (13.1 m) and a diameter of 14 feet (4.26 m). Its major components are an optical telescope assembly , five scientific instruments , and a support systems module . !home An artist's conception of the space telescope in orbit.

- NASA's Office of Space Science and Applications, Washington, DC, is responsible for overall direction of the Hubble Space Telescope Program.

- Marshall Space Flight Center, Huntsville, AL, is the leading NASA center for the Hubble Space Telescope, providing day-to-day management of the project. Marshall also directs the construction and integration of the telescope and spacecraft systems.

- Goddard Space Flight Center in Greenbelt, MD, is responsible for development of the Telescope's four American-contributed scientific instruments , the development of the ground system, and Telescope operations once in orbit.

- European Space Agency (ESA), a consortium of eleven western European nations, is responsible for developing the Faint Object Camera , one of five scientific instruments aboard the Hubble Space Telescope. ESA is also developing the solar arrays which power the spacecraft and will provide a small resident staff to help operate the Space Telescope Science Institute in Baltimore.

The ESA's principal members include: Belgium, Denmark, France, West Germany, Ireland, Italy, the Netherlands, Spain, Sweden, Switzerland, and the United Kingdom. Associate members include Austria and Norway.

- Johnson Space Center in Houston, Texas, will launch the Hubble Space Telescope using the Space Shuttle.

- Kennedy Space Center, Florida, is also involved in Space Shuttle launch operations.

- The Association of Universities for Research in Astronomy (AURA) has responsibility for operating the Space Telescope Science Institute in Baltimore, MD, under contract to NASA's Goddard Space Flight Center . AURA includes: University of Arizona, California Institute of Technology, University of California at Berkeley, University of Chicago, University of Colorado, Harvard, University of Hawaii, University of Illinois, Indiana University, Johns Hopkins University, Massachusetts Institute of Technology, University of Michigan, Ohio State, Princeton, University of Texas at Austin, University of Wisconsin, and Yale. responsibilities fig. 6 (fig. 6) A chart illustrating the organizations working on the Hubble Space Telescope and their responsibilities. resp. - word support system resp. - word optical telescope assembly resp. - word fine guidance resp. - word faint object camera resp. - word goddard resp. - word Scientific instrument scientific instruments The wide field/planetary and faint object cameras, the faint object and high resolution spectrographs, and the high-speed photometer. The five scientific instruments, four American and one European, are located behind the primary mirror, at the focal plane, where they can pick up light reflected from the telescope. They are the wide field/planetary camera , the faint object spectrograph , the high resolution spectrograph , the high speed photometer , and the faint object camera , the latter provided by the European Space Agency . In addition, the fine guidance sensors , part of the support systems module , because of their ability to accurately locate stars, could be considered a sixth scientific instrument. Each instrument is housed in a separate module and will draw 110 to 150 watts of power. All are exchangeable during maintenance visits by the Space Shuttle. hubble space telescope space telescope edwin p. hubble space telescope main telescope A diagram of the telescope with major components labelled.

The module has four main sections: the light shield, the forward shell, the equipment section, and the aft shroud. These four pieces fit together like stacked cannisters to enclose the telescope assembly and scientific instruments.

The aperture door , which also serves as a light shield, is located at the front of the Support Systems Module. The telescope must be shielded from the Sun, Earth, and Moon so that the scientific instruments are not damaged by a flood of light. While in operation, the telescope will not be turned to within 50 degrees of the Sun, precluding observations of the planet Mercury. Internal baffles in the Support Systems Module door and just below the secondary mirror prevent scattered light from degrading the focal plane image.

Just behind the light shield and the forward shell is the equipment section of the spacecraft. This doughnut-shaped section is made up of 10 compartments that house the electronic and control modules. Access to many of these modules will be easy as most compartments open from the outside via a hatch or access door. An astronaut can open a hatch, disconnect a module from its plug-in compartment, and insert a new module, all without disturbing the other instruments in the spacecraft.

The aft shroud fits over the section containing the scientific instruments and the fine guidance sensors . Access covers on this shroud enable astronauts to get at the instruments and sensors for removal or maintenance.

Handrails and portable foot restraints are fixed on the external surface to permit astronauts to perform their maintenance and refurbishment tasks. Four magnetic torquers , also located on the shroud exterior, work with four reaction wheels within the Support Systems Module equipment section to control the spacecraft's orientation in space. The magnetic torquers are magnetized metal rods controlled by an onboard computer. A change in their position causes the spacecraft to re-align itself in relation to the Earth`s magnetic field.

Electrical power is supplied by onboard batteries, which are charged by the two solar arrays during the sunlit portion of the telescope's orbit. An average of 2.4 kw is needed to operate the spacecraft and its instruments. Wide Field Planetary Camera A camera that can take photographs either in "wide-field" or "planetary" mode. The resulting images are transmitted by radio to Earth.

This instrument (fig. 8) can operate in one of two modes. In "wide field" mode, its focal ratio of f/12.9 will permit examination of large areas of space, leading to more accurate plotting of the spatial relationships of distant objects such as galaxies and quasars. High-resolution images of planets within our solar system can be obtained by the planetary camera, which has a focal ratio of f/30.

Images telemetered to Earth by radio will be far better than pictures produced by ground-based cameras. Pictures of Jupiter, for example, will be comparable to those taken by the two Voyager spacecraft in 1979. Pictures of more distant planets will not be as clear as those taken by Voyager, but will be far superior to those taken from Earth.

The camera consists of a complex system of instruments and mirrors. The field of view is split by a pyramidal mirror into four separate areas which are focused onto four charge-coupled devices . These devices have been designed to receive light of low intensity at very high resolution. A portion of the image is received on each target plate and is subdivided into 640,000 picture elements (pixels). The light intensities of each pixel are transmitted to Earth via telemetry signals for assembly into images for study. Images can be created from different spectral bands by directing the light through any one of 50 spectral filters within the camera. !index Blinking Eyes
Debug panel
Faint Object Camera - exploded view
Faint Object Camera
Faint Object Spectrograph - Exploded view
Faint Object Spectrograph
Fine Guidance Sensors
Font Menu
Forth Interaction
Goddard Space Flight Center
High Resolution Spectrograph - exploded view
High Resolution Spectrograph
High Speed Photometer - exploded view
High Speed Photometer
Hubble Space Telescope - Main View
Miscellaneous popups
NeWS Forth TIES PostScript Demos
NoWhere
Optical Telescope Assembly - diagram
Optical Telescope Assembly
Participating Organizations
Pie Examples
Pie Menu Demonstration
Project Responsibilities
Root Pie Menu
Scientific Instruments
Scroll Bar Madness
Space Telescope Science Institute
Spin the Earth
Spinning Earths
Stop the Earth
Sun Workstation
Support Systems Module - Exploded View
Support Systems Module
The Founders
The Space Telescope in Orbit
Through the Hacking Glass
Why the Hubble Space Telescope?
Wide Field/Planetary Camera - exploded view
Wide Field/Planetary Camera
NeWS window system Nee-WiS A description of the NeWS implementation of HyperTIES. List of NeWS classes used by NeWS Forth HyperTIES.
Demos of NeWS Forth HyperTIES features.
content contents A lengthy multi-media piece -- the document proper The content may contain references to other documents, which are simply the titles or synonyms of those documents, embedded in the text (or connected to a graphic), and marked by the author. (See How to make a link ).

Since the storyboard is a pure text document, it uses a special markup language to indicate page layout, font types, and to specify the inclusion of graphics.

The content is part of the storyboard . It follows the ".content" command. (or ".contents", ".CONTENT", or ".CONTENTS") overview of the data structure A description of the file structure of a Hyperties database.

The Hyperties database system is implemented in the standard file systems available in most operating systems (though UNIX and MS-DOS are of primary concern).

A Hyperties database is made of a collection of articles.

In general, a document (i.e. a node in the hypertext network) is represented by a collection of files. The only necessary file is the storyboard which serves as the primary description of the article's format and content. It is a text-only file, therefore human readable.

Other associated files contain picture description (or other data, such as digitized sound, that will not normally be represented as human-readable text) and information used to allow rapid presentation of the document at browsing time.

One special file, the master index , exists to provide the association between the article files and the database as a whole. A special directory, ties/global , contains all the defaults settings and initializations.

The new Hyperties database format permits great freedom in the organization of a database's component files. An author can impose a hierarchical structure (or any other that is suitably mnemonic), using the features of the standard filesystem found in UNIX and MS-DOS, to simplify access to components of the database when a fully-integrated authoring environment is not available, and to "flatten" the structure of a database to optimize use of storage when authoring is fully supported.

Also, the new format will allow spreading the component files of a database across multiple devices, allowing larger databases to be used on floppy-based systems. description short description definition A brief textual, graphical, etc. piece, usually used to summarize an article. But some documents have only a description and no full article. You are reading the description of "The article description"!! An overview of the documentation This documention describes the current version of Hyperties on the SUN. It describe the functionalities, the data structure , the markup language . It also covers the organization of the software . To browse and find information in the documentation, follow the embedded links or use the Table of Topics . Forth formatter The formatter is the main part of the browser. It formats the components of the storyboard to fit in the display windows. Several simplifying assumptions have been made, which impose limits on the browser interface. It is assumed that articles are to be viewed by paging rather than scrolling, so that formatting produces a collection of page images. On more powerful systems, the formatting could be performed at browsing time for resizable and/or scrolling windows. Finally, a Hyperties database is assumed to be static, i.e. the contents of a database will not change during browsing. With a more powerful database management system to handle file requests and arbitrate access conflicts, dynamic databases should be possible as well. These restrictions, however, are not inherent in the database structure, but have been introduced out of considerations of efficiency in implementation. In future versions, some of these restrictions may be relaxed.

TECHNICALLY:

Today the formatter is a temporary version written by Don Hopkins in Forth, because it made it easy to implement. Unfortunately it doesn't handle tildes and names with embedded blanks too well... So we had to compensate by using a dot-tilde command, followed by a space, then the button name, terminated by a tilde, so buttons appear as .~ button~ in the storyboard.

TO BE CONTINUED... the markup language markup language Describes the markup language used to describe the article. The storyboard contains all the information necessary to display an article. The author has to use a markup language to specify all that information.

The command syntax is: <whitespace> .command<whitespace>[arguments]

Whitespace consists of blanks, newlines, and/or tabs.

There are four types of commands:
     - the field commands
        To separate title, synonyms, contents, notes
     - the component commands
        To separate text, picture, video, sound
     - the formatting commands
        To specify margin sizes, fonts, paragraphs
     - the link commands
        To indicate links to other articles
All the tools Catherine had or would have liked to have while building this database by hand..

1- a quiet room (thanks for Mildred's room...)

2- multiple views In some aspects, building this database reminds me of the 3 dimensional mechnical drawing I had to do at the engineering school...

3- and more... A SUIVRE

4- and for Don ... A giant bean bag chair! associated files The full name used to refer to a picture or a graphic target

A picture is generally a bitmap or a postcript file, etc... A graphic target could be a bitmap, a rectangle or a shape, but anyway those objects don't have a simple name to refer to them.

For this reason we ask the author of a database to give a name to those objects. Therefore a picture has a picture name, and a target has a target name. The author creates .pn0 (for picture names) and .tn0 (for target names) files to create the link between the name, the class of the object, and the data necessary to display it. See the articles on picture name file format and target name file format .

Today, because of the Forth formatter , a picture or target name must end by a new line.

For example, to include a picture in a storyboard you have to say:
.picture name of a picture (newline)

For an example, look at the storyboard "spacetel/spacetel.st0" in the space telescope database. picture files Describes the format of the .pn0 file. For each picture, the picture file should include:

target name (new line)
target class (new line)
body (any number of non-blank lines)

A picture file can contain several picture descriptions in the above format, separated from each other by blank lines.

The class name determines what type of object the picture is (eg. A bitmap, a PostScript file, etc...). It also tells what information is available in the body and how to read it.

The picture name can be any ascii string, enclosed in double quotes. It can include blanks or any punctuation (to include double quotes in a name, use two double quotes for each one). The name should be on one line. Remember, it is the name that is used in the storyboard.

The body contains all the information necessary to handle the picture, or a pointer to the file where the information is.

The .pn0 file can be anywhere under the root directory of the database. The author can for example choose to put it "near" the associated storyboard, or in a special directory where all the .pn0 files are stored. It is the role of the master-index builder to find them...

See for example : spacetel/main.image.pn0 or fosexplo/fos.pn0 organization of the software The parts of the HyperTIES system. This stuff lives in the directory "ties".
Master index builder
Builds the master index by looking at all of the storyboard, picture, and target files in a database.
make-index.c
Storyboard Interpreter
Reads in and parses storyboard files. fmt.f
Formatter
Figures out where to put everything on the page.
fmt.c
Index manager
Maps names of objects and storyboards to parts of the file system.
entry.c entry.h index.c index.h master-index.c master-index.h object.c object.h primitives.c primitives.h tree.c tree.h
C to PostScript interface
Handles the layout of text, pictures and targets.
fmt.cps
PostScript objects and handlers
Builds display lists, creates objects, sends messages to objects. fmt.ps win.ps stamp.ps target.ps
Random PostScript utilities
textcan.ps term.ps hookup.ps
standard 3 letter file extensions Describe the standard names used for all the database files.

Since a Hyperties database will consist of several types of component files, there will be a set of standard 3-letter extensions used to identify file types to the system. These extensions will identify the nature of the contents of a file, its system-specificity, and a general version number, to permit some evolution of the internal file formats without "orphaning" existing databases. For example, the initial portable storyboard files will have the extension ".st0", and a later version of the (non-portable) PS/2 display file may be ".ps3".

TODAY: the standards are:

st0 for the storyboard

pn0 for the picture names

tn0 for the target names storyboard storyboards The text file describing an article, written by the author. The storyboard files are pure text descriptions of the individual articles (nodes in the hypertext network) of a Hyperties database. These files are broken into sections, containing the title , synonyms , description , content , and notes (an optional collection of textual remarks maintained by the author). The content (and possibly the description) may contain references to other documents, which are simply the titles or synonyms of those documents, embedded in the text (or connected to a graphic), and marked by the author. Since the storyboard is a pure text document, it uses a special markup language to indicate page layout, font types, and to specify the inclusion of graphics. synonyms Alternate identifiers by which the document may be referenced

The synonyms are alternate identifiers by which the document may be referenced. (see how to make a link )

The synonyms are specified by the author in the storyboard. They follow (one per line) the command ".synonym", (or ".synonyms", ".SYNONYM", or ".SYNONYMS".)

A synonym is a string ended by a newline (it can include blanks, punctuation...) Table of Contents !home !topics A list of all topics covered by this database on the Sun version of Hyperties. Table of topics of the Hyperties Documentation
Building User Interfaces in NeWS
Documentation Overview
Version concerned
Why a new version again
List of Demos

Functionality
        - browser
                - article
                - page
                - title
                - synonym
                - description
                - content
                - setting the style of the browser
        - authoring
                - author - overview
                - the markup language
                - how to make a link
                - the home article (or introduction article)
                - the table of topics article
                - the index article
                - Needed tools for an author
Data Structures
        - overview of the data structure
        - storyboard
        - article's associated files
                - picture name file format
                    - list of available stamp classes
                - target name file format
                    - list of available target classes
        - master index
        - standard 3 letter file extensions

Technical aspects
        - structure for portability
        - the hyperties engine
        - the window system
        - NeWS
        - language(s) used
        - software modules
        - list of NeWS classes
Compiler
        - master index builder

Projects to come :
        - functionality
                - more touchable graphic possibilities
                - multiple windows strategies
        - technical projects
                - article style descriptions
                - more formatting capabilities
                - the X version
                - the building of preformatted display files
title titles The name of an article, given by the author.

The title identifies the article. It appears at the top left corner of each page when the article is displayed.

The title of an article is specified by the author in the storyboard . It follows the command ".title" or ".TITLE".

The title of an article is also used to make reference to an article. (see how to make a link ). target files Describes the format of the .tn0 file. For each target, the target file should include:

target name a (new line)
target class (new line)
body (any number of non-blank lines)

A target file can contain several target descriptions in the above format, separated from each other by blank lines.

The class name determines what type of object the target is. It also tells what information is available in the body and how to read it.

The target name can be any ascii string, enclosed in double quotes. It can include blanks or any punctuation (to embed double quotes, use two double quotes for each one). The name should be on one line. Remember, it is the name that is used in the storyboard.

The body contains all the information to the data necessary to handle the target, or a pointer to the file where the information is.

The .tn0 file can be anywhere under the root directory of the database. The author can for example choose to put it "near" the associated storyboard, or in a special directory where all the .tn0 files are stored. It is the role of the master index builder to find them...

This documentation concerns the SUN version written for the NeWS window system .

We try to keep it up to date, and to give an indication of what the next development will be. Gives the reasons why we restructured Hyperties and changed the data structure. Hyperties has been in use for some time as a pure hypertext system running under MS-DOS. The original Hyperties is highly specialized to this environment and to a particular set of capabilities and interface features. As a result, the system architecture is "closed" and difficult to extend. There have been ongoing efforts to explore a variety of extended capabilities: large, bitmapped displays and multiple windows (on the SUN workstation); alternate input devices (touchscreen); graphics and other media; global textual search; and numerous possible interface variations. From these efforts have sprung a number of divergent Hyperties systems, each customized for a particular investigative task, but based on the original Hyperties architecture. A more modular and extensible Hyperties architecture is proposed which, it is hoped, will facilitate future research by providing an open framework for experimentation and revision, will provide for maximal reuse of software, and will ultimately allow current work to be integrated into one system. Blink Eyes that wink and blink. 2 blink-open 3 blink-close Debug [Rect width 480 height 20] command-text exec! command-exec
[Rect width 480 height 20] command-text exec! command-exec
[Rect width 480 height 20] command-text exec! command-exec Some example window managment menus.

It had been a long night of caffeine abuse on a Sun workstation, and another can of coke was empty... I pointed the mouse at an available shell window, and typed "cat > /dev/null"... After pushing the can through the screen and into the window, I typed ^D. It was gone.

At this point, I realized that the glass had never been quite so permeable before. Wondering how the desktop would feel, I stuck my hand through the glass to find out.

The root grey background felt rough and bumpy, like screen you use to keep bugs out when you have windows open.

I inserted my fingers into a shell window and wiggled them around in the Unix. I noticed the warm, steady throbbing of the Unix virtual machine. I could feel a huge heap of Unix utilities, each with a unique bouquet of switches and knobs and frobs that makes it hard to pick up.

Most comforting of all was my nice, soft, fur lined Emacs. It fit like a glove. It's a glove that lets my hands do to files what superman's hands do to lumps to coal.

Next, I ran my fingers over the rough, jagged lines of the graphs in the system performance monitor window, pricking my finger on the sudden peak in CPU time brought about by my intrusion into this micro-world.

The unexpected pain caused a sudden context switch, and I abruptly found myself slumped in a chair, in front of a keyboard, with my face pressed up against a screen of solid glass. Wiping the nose prints off of the screen, I wondered if I had dozed off or something. According to the perfmon window, though, that was the most CPU intensive dream I'd ever had.

-Don Hopkins list of demos demos A bunch of nifty demos, showing some of the capabilities of NeWS Forth TIES. Check out all these nifty demos!

- Building User Interfaces in NeWS
- Founders
- Miscellaneous
- Sun
- Spin
- Hacking
- Scroll
- Pie Menu
- Font Menu
- Pie Demo
- Pie Examples
- Blink
- Debug
Pie Menu The NeWS root menu, in pie menu form. The NeWS rootmenu:
rootmenu.demos rootmenu.applications rootmenu.exit rootmenu.repair rootmenu.user rootmenu.sunview1 rootmenu.allwindows rootmenu.rlogin rootmenu.center rootmenu.cursor rootmenu.label Miscellaneous Miscellaneous things that pop up at you! Miscellaneous Stuff
miscellaneous.table miscellaneous.bunny miscellaneous.top miscellaneous.widget miscellaneous.violin miscellaneous.planet miscellaneous.puzzle This link leads nowhere! You are NowHere! The Pie Menu Demonstration Pie Demo A description of the advantages to pie menus, with some example menus to play with.
  How to Choose with Pie Menus

Don Hopkins
University of Maryland
Human Computer Interaction Lab

Jack Callahan
University of Maryland
Heterogeneous Systems Lab

                      

David. forth Interactive text window connected to Forth! [Rect width 20 height 550] text-scroller [Rect width 490 height 550] forth-text outline The outline of a talk about building user interfaces in NeWS. The outline of a talk about building user interfaces in NeWS.

=> The NeWS Interactive Programming Environment
=> The HyperTIES hypermedia browser
=> The UniPress Emacs Text Editor
=> Pie Menu Demonstration
=> NeWS Hacks
news talk newstalk !home Visuals for a talk about building user interfaces in NeWS.

A MenuTarget is a target that pops up a menu when you click it with the right mouse button.

Today all the information is in a PostScript form but we will later develop additional classes easier to author.

Turn the page to see an example of how to use a MenuTarget!

A PopupTarget is an unconstrained shape defined by an outline. When touched by the mouse cursor, the shape pops up. The body includes an argument list and an initialization function. The argument list specifies the the X, Y of the translation vector, the expansion ratio, and the raster image for the popup. The initialization function defines /ItemPath, the stencil of the target, as a NeWS function that creates a path. It can also define /HoleColor, the color of the hole left when the target pops up. HoleColor, which is a NeWS color object, defalts to 25% gray.

Today all the information is in a PostScript form but we will later develop additional classes easier to author, and authoring tools to create objects interactively.

Turn the page to see an example of how to use a PopupTarget!

Objects of the Stamp class and its subclasses are used as "stamp pads" to put down pictures and targets on the page. Stamp pads for pictures are described in the picture files , and target stamp pads are described in target files .

Stamp  Picture  UnitPicture  ScaledRaster  Raster  TargetStamp   Target A description of the Target class. List of Available Target Classes Target Classes targets Classes of objects used as touchable targets. Describe the generic target class here!

Target  MenuTarget  PageTrackerTarget  PopupTarget  ScrollbarTarget  SliderTarget  TextEditTarget  TextCanvasTarget  AnimatedTarget   TargetStamp A description of the TargetStamp class. TextCanvasTarget A description of the TextCanvasTarget class. TextEditTarget A description of the TextEditTarget class. TIESWindow A description of the TIESWindow class. TTY A description of the TTY class. UnitPicture A description of the UnitPicture class. Window Classes A list of the classes of windows used by NeWS HyperTIES for an article's contents, its definition, the control panel, and the interactive Forth system. NeWS Forth HyperTIES maintains several piles of pages on the screen, each displayed in a windows of a particular class, as well as a TTY window for interacting with the forth system.

The page display windows are all based on class TIESWindow . Windows of class TIESContentsWindow are used to display the contents of a storyboard. Windows of class TIESDefinitionWindow are used to display definitions of referenced articles. Class TIESControlWindow is used for the control panel. component commands The commands marking the different components of the content or description of an article.

These are the commands marking the different components (pictures, text, sound, etc.) of the content or description of an article.

A media component begins after a component command and ends with the next component command or field command. The available commands are:
.text or .text
Begins a text component. In fact this command is the default component command. Everything which is not a command or its argument is considered text.

.picture or .PICTURE <name of the picture>
Begins a picture component. It's followed by an argument which is the name of the picture. (see picture name file format , and list of available stamp classes )

PROJECTS: other media components will be created if the hardware is available (sound, video...) the home article An ordinary article which has "!home" as a synonym. The home article is accessed when the browser starts, and when the HOME option of the control panel is selected. the index article The list of articles in the database The index article consists of an alphabetical list of all the articles of the database.

It is the article whose title or synomym is "!index". It is accessed when selecting the INDEX option of the control panel.

This article is created automatically by the ~master index builder~ which creates or updates the storyboard index.st0 the table of topics article This article is accessed by the option TOPICS of the control panel. It is an ordinary article (created entirely by the author) which must have "!topics" as a synomym. !index AnimatedTarget Class
Article title
author - overview
authoring: the home article
authoring: the index article
Authoring: the markup language
authoring: the table of topics article
Blinking Eyes
Building User Interfaces in NeWS
data structure
Debug panel
Documentation overview
examples of database organisation
Faint Object Camera - exploded view
Faint Object Camera
Faint Object Spectrograph - Exploded view
Faint Object Spectrograph
Fine Guidance Sensors
Font Menu
formatter
Forth Interaction
Goddard Space Flight Center
High Resolution Spectrograph - exploded view
High Resolution Spectrograph
High Speed Photometer - exploded view
High Speed Photometer
how to make a link
Hubble Space Telescope - Main View
List of NeWS Classes
List of Stamp Classes
List of Target Classes
List of Window Classes
master index builder (make-index)
Master Index
MenuTarget Class
Miscellaneous popups
Needed tools for an author
NeWS Extensions to PostScript
NeWS Forth TIES PostScript Demos
NeWS Hacks
NeWS Talk Outline
NeWS
NoWhere
Optical Telescope Assembly - diagram
Optical Telescope Assembly
PageTrackerTarget Class
Participating Organizations
picture and target names
Picture Class
picture name file format
Pie Examples
Pie Menu Demonstration
PopupTarget Class
Project Responsibilities
Raster Class
Root Pie Menu
ScaledRaster Class
Scientific Instruments
Scroll Bar Madness
ScrollbarTarget Class
SliderTarget Class
Software Modules
Space Telescope Science Institute
Spin the Earth
Spinning Earths
Stamp Class
standard 3 letter extensions
Stop the Earth
Sun Workstation
Support Systems Module - Exploded View
Support Systems Module
synonym
Table of Topics
Target Class
target name file format
TargetStamp Class
TextCanvasTarget Class
TextEditTarget Class
The article content
The article description
the field commands
the formatting commands
The Founders
The HyperTIES hypermedia browser
The media component commands
The NeWS Interactive Programming Environment
The Object Oriented Programming Package
The PostScript Programming Language
The Space Telescope in Orbit
the storyboard
The UniPress Emacs Text Editor
The X11/NeWS Merge
Through the Hacking Glass
ties/global directory
TIESContentsWindow Class
TIESControlWindow Class
TIESDefinitionWindow Class
TIESWindow Class
TTY Class
UnitPicture Class
Version concerned
Why a new version again
Why the Hubble Space Telescope?
Wide Field/Planetary Camera - exploded view
Wide Field/Planetary Camera
link command link commands Describes how to specify a link in the content of an article The command syntax is: <white space>.~<white space><reference>~

(Generally a space, followed by a dot, directly followed by a tilde and a space, then the text of the button terminated by another tilde.)
For example, .~ button~ As usual the text of the button should be the article title or a synonym of an article title. The effect of this link is a jump to the beginning of the article whose title is given between the tildes.

IN THE NEAR FUTURE:
We will go back the the use of the tildes (e.g. ~button~), which are easier to use and don't disturb the reading of the storyboard so much. We now use the .~ command to simplify the job of the formatter .

IN THE DISTANT FUTURE:
We could provide typed links by providing different link commands. field commands A list and description of the field commands of a storyboard ( .title, .synonym, etc...) The field commands separate the main fields of a storyboard . This is the highest level in the hierarchy of commands.

The available field commands are:
.title or .TITLE
Indicate the beginning of the title . The title follows one of the above commands and ends in a newline

.synonyms, .SYNONYM, or .SYNONYMS
Indicates the beginning of the synonyms . The synonyms follow one of the above commands, one per line until the next field command or the end of the file.

.content, .contents, .CONTENT, or .CONTENTS
Indicates the beginning of the content of the article. The content is everything between one of the above commands and the next field command or the end of the file.

.note, .notes, .NOTE or .NOTES
Indicates the beginning of the notes about an article. The notes start after one of the above commands and cause the rest of the file to be ignored.

PROJECTS TO COME: We plan to add other fields like topic, keywords etc.. formatting commands The commands used to specify how the media components like text and pictures should be presented. Without any formatting commands, the text and pictures will be glued together. Multiple white spaces are reduced to a single blank.

1- text formatting commands:

.para or .PARA
Paragraph: equivalent to two newlines and indentation of xxx characters for the first line of the paragraph

.nl
Newline

.quote <a word>
The word argument is taken literally, ignoring command or other special characters in it. For example to show the command .nl, the author has to write .quote .nl

.quote-line <a line>
Same as quote, but takes the whole line as its argument.

.spaces <number of spaces>
Insert N spaces

.rem
Remark. The rest of the line is ignored. Used to put comments in a storyboard

PROJECTS:
- a blank line in the storyboard will be equivalent to a newline
- .table-on/off will be used to turn-off or turn on the formatting. When the formatting is turned off, the text is displayed exactly as typed. make-index program master index builder A utility program of the compiler which creates the master-index and the index storyboard.

Syntax:      make-index <directory> [ other directories]

make-index scans the directories given as arguments (and, recursively, their subdirectories) for storyboards and associated files. It uses the standard 3 letter extensions of those files to perform its search with the UNIX find command. Today the directory ties/global contains all the defaults storyboards and associated files necessary to run any database, including the control panel description.

You will usually run make index with 2 arguments: your database root directory and global. (eg. make-index doc global)

Make-index also creates or updates the index.st0 (the storyboard of the index article). It builds the article which consists of the alphabetical list of article titles and is accessed with the INDEX option of the control panel. What to do to create a new database.

An Hyperties database is a set of articles. The main thing to do is to write a storyboard for each article. You are free to organize your files any way you want under a root directory (see examples of database organisation ). The root directory name is what is used to invoke the browser on the database.

Of course, if you include graphics in your database, you will also have to include the graphic files and associated files in your database directory to resolve the picture and target names used in the storyboards.

Today there is still no authoring tools available. You have to do everything using your favorite text editor. While writing this documentation database, suggestions have been made about the ~needed tools for an author~.

When the database is ready (or to try it) follow the steps...
1- Build the ~. master index~. For that you have to invoke the make-index program from the ties directory (which includes all the executables). to do: will describe the organisation of NEWDB and DOC todo.. Directory containing all the defaults setup _; scale to fit brillig in bbox of current path pathbbox points2rect 4 2 roll translate 2 copy div % w h w/h /brillig_dimensions load aload pop % w h w/h bx by bw bh div 3 1 roll pop pop % w h w/h bw/bh le { % this is wrong, but I don't understand why 0 exch 2 div translate % w h w/h /brillig_dimensions load 2 get div % w h w/h/bw dup scale % w h w/h/bw } { 1 index 2 div 1 index 2 div translate % w h bw/bh /brillig_dimensions load 3 get div % w h bw/bh/bh dup scale pop % w h /brillig_dimensions load 2 get 2 div neg 0 translate % w h } ifelse } def end % userdict { { % 0 0 1 1 rectpath % scale_to_fit 0 .5 translate 1 380 div 1 200 div scale newpath 1 setlinequality 4 setlinewidth 1 setlinecap 0 setgray lig } dlist } 330 80 ]]> - mark exch { hookfile exch write } errored cleartomark } def /InsertValueCallback { % string => - mark exch { hookfile exch writestring } errored cleartomark } def hookproc type /processtype eq { hookproc killprocess /hookproc { { hookfile bytesavailable dup 0 eq { pop [ hookfile 1 string readstring not {exit} if ] } { string hookfile exch readstring not {exit} if 10 dict begin /s exch def /newlines 0 def s {10 eq {/newlines newlines 1 add def} if} forall /a newlines 1 add array def 0 1 newlines 1 sub { pause /i exch def s (\n) search pop /pre exch def pop /s exch def a i pre put } for a newlines s put a } ifelse true writeatcaret } loop [()(*** EOF ***)()] true writeatcaret } fork store } if } def } ]]> controls control panel FIRST first-button         BACK PAGE back-button         NEXT PAGE next-button         LAST last-button

RETURN return-button     TOPICS topics-button     INDEX index-button     HOME home-button     SHOW show-button     QUIT quit-button     REFRESH refresh-button      Characteristics and distinctions The characteristics and distinctions of pie menus. Pie menus are defined, and their their relationship with direction and distance is described.

==> Definition Title !home The title page of the database.