\begindata{text,728192}
\textdsversion{12}
\template{default}
\center{

\bold{Installation Notes for the AUIS-63L0-WP Package

}
}

\bold{FORWARD}


This is the first of several planned versions of "packages" of the 
\bold{Andrew User Interface System} (\bold{\italic{AUIS}}).  AUIS can be 
difficult to describe fully since it encompasses such a large variety of 
applications and uses.  In an effort to break this into something more 
manageable, both in size and scope, I have created this particular package 
which is aimed principally at people interested in \bold{WORD PROCESSING}.


Please understand that a full AUIS distributed system would require close 
to 40 MB of space and consists of hundreds of distinct functional pieces. 
 Few make full use of all this functionality and it certainly is daunting 
for the novice.  However, providing a restricted set of AUIS has drawbacks 
because thousands of files are missing.  This will be most apparent in the 
help text which will refer to some files which you will not have.  This is 
the price I have chosen to pay for a simpler AUIS.


Do not mix versions of AUIS packages.  Always use packages at the same 
LEVEL (i.e. L0 with L0).  Mixing LEVELS can result in surprising and 
undesirable behavior.  Watch for a series of articles on AUIS to appear in 
the Linux Journal beginning sometime the summer of 1994.


\flushright{Terry Gliedt	\


tpg@mr.net	\


}

\bold{INTRODUCTION}


The Andrew User Interface System is an integrated set of tools that allow 
you to create, use, and mail documents and applications containing 
typographically formatted text and embedded objects.  AUIS has three 
principal components:


\indent{The \bold{Andrew User Environment} (\bold{\italic{AUE}}) is an 
integrated set of applications beginning with a 'generic object' editor 
(\italic{ez}), a help system, a system monitoring tool (\italic{console}), 
an editor-based shell interface (\italic{typescript}), and support for 
printing multi-media documents. \



The \bold{Andrew Toolkit} (\bold{\italic{ATK}}) is a portable 
user-interface toolkit.  It provides a dynamically-loadable, 
object-oriented environment wherein objects can be embedded in one-another. 
Thus, one could edit text that contains not only fonts and styles, but also 
embedded raster images, spreadsheets, drawing editors, equations, simple 
animations, etc. These embedded objects could themselves contain other 
objects, including text. ATK is an open system so programmers can create 
new objects that can be embedded as easily as those system-defined objects. 


The \bold{Andrew Message System} (\bold{\italic{AMS}}) provides a 
multi-media interface to mail and bulletin-boards.  AMS supports several 
mail management strategies and implements many advanced  features including 
authentication, return receipts, automatic sorting of mail, vote collection 
and tabulation, enclosures, audit trails of related messages, and 
subscription management. It also provides a variety of interfaces that 
support ttys and low-function personal computers in addition to the 
high-function workstations. }\



\{History: In 1982 Carnegie Mellon and IBM entered into a joint venture and 
formed the Information Technology Center to design a very powerful, 
advanced function workstation and distributed computing environment on 
campus.    This environment is known as the Andrew System, named for the 
university's two major benefactors, Andrew Carnegie and Andrew Mellon.  In 
1992, the School of Computer Science formed the Andrew Consortium to 
extend, support and distribute the Andrew User Interface System  (AUIS).\}



\bold{INSTALLATION}


This packaged is distributed as a single tar file of approximately 1.4 MB 
(one diskette!) which will expand to approximately 4.5 MB of disk space. 
 To install this package, do the following as root:


\indent{cd /

tar xzf [path]/auis63L0-wp.tgz

}
This will create a hierarchy of files under \italic{/usr/andrew}.  None of 
these files require root authority.  A set of binaries is distributed in 
\italic{/usr/andrew/bin}.  Add this path to your PATH so they can be 
executed:


\indent{setenv PATH $\{PATH\}:/usr/andrew/bin; rehash	# For csh/tcsh users

export PATH=$\{PATH\}:/usr/andrew/bin		# For bash/ksh users

}
AUIS is highly tailorable for your personal needs and preferences.  Some 
might say there is too much.  To get you started, I've done a great deal 
for you in this area.  Create a file called "\bold{preferences}" in your 
home directory for AUIS:


\indent{cp /usr/andrew/sample.preferences $HOME/preferences

}
This sample \italic{preferences} is aimed at folks with color displays.  If 
your system only supports monochrome, you'll want to remove the color 
settings in "\italic{preferences}" right away.  Edit your 
\italic{preferences} file and follow the comments.



\bold{YOUR FIRST AUIS SESSION}


AUIS requires that you be running the X Window System.  AUIS comes with a 
massive amount of help text.  Probably your first xterm command should be 
"\italic{\bold{auishelp}}" and begin with "\bold{A Guided Tour of Andrew}".


Your principle tool for word processing will be an editor named 
"\bold{ez}".  You might try this for your first practice session.


\indent{cp /usr/andrew/README.ez /tmp

chmod +w /tmp/README.ez

ez /tmp/README.ez

}
When you create your own new documents, use any of these extensions:

	.d  .doc  .ez  .letter  .memo  \


These extensions will default to use a style you'll find useful for word 
processing.  If the file has already been created by ez, then the data 
itself will determine the style to be used and you have nothing to do.



\bold{KEY BINDINGS}


As part of the customization provided for you, I have defined a number of 
F-key bindings to make word processing a bit easier:


\indent{F1	Copy	(After selecting an area, copy it)

F2	Paste	(Put copied data at cursor)

F3	Cut	(Remove selected data)

F4	Cycle-Copy-Buffer	(AUIS remembers previous copied data)

F5	Show selected text in an \italic{italics} font

F6	Show selected text in a \bold{bold} font

F7	Plainer selected area (Remove one level of styles)

F8	Plainest selected area (Remove all levels of styles)

}

\bold{CHANGELOG}


Release auis62L1-wp has the following changes:


\indent{- Now based on AUIS 6.2.1 - which has only fixes to 6.2.


- The AUIS help program can be invoked from the File menu.  Note this is 
not context sensitive help - just a means to invoke /usr/andrew/bin/help.


- Added auishelp shell


- Added support for html


- Added support for equations (eq)

}
Release auis62L2-wp has the following changes:


\indent{- Now based on AUIS 6.2.2 - which has only fixes to 6.2.


- Removed various unused pieces


- Added a filter on the Misc menu to "flow" text together


- Added a simple spreadsheet, table


- Stripped the binaries (thanks to mitchum.dsouza@mrc-apu.cam.ac.uk)


- This package now fits in one 3.5 inch diskette!

}
Release auis63L0-wp has the following changes:


\indent{- Now based on AUIS 6.3 - which has only fixes to 6.2.


- Corrected atkprint and atkpreview so equations will work



}
\bold{SOME THINGS YOU MIGHT LIKE TO KNOW}


\description{This release was built on Slackware 1.2.0.


When you enter the "\italic{ls}" command in a "\italic{\bold{typescript}}", 
you might see something like "[01;34mMail[0m/".  This is a result of the 
"colorful" version of ls adding escape sequences to its output.  Typescript 
does not support these sequences.  You can avoid this by setting an alias 
for \italic{ls} to \italic{/bin/ls}  (e.g. \italic{alias ls '/bin/ls -F}').


\italic{Typescript} file-completion is almost set for you. 
 \italic{Typescript} will attempt to complete a filename when you press 
Tab.  To enable this, do the following (or equivalent in your shell).  In 
\italic{csh}, include the following in your $HOME/.cshrc:


\example{if ("$?TERM") then

  switch ("$TERM")

    case "wm":

      alias cd 'cd \\!*; echo $cwd'

      alias pushd 'pushd \\!*; echo $cwd'

      alias popd 'popd \\!*; echo $cwd'

      breaksw

    default:

    breaksw

  endsw

endif

}
\italic{Typescript} is *\bold{not}* \italic{xterm}.  You cannot use 
\italic{vi} or \italic{telnet} directly from it, but you can make a little 
shell script like this version of \bold{/usr/local/bin/telnet}:


\example{#!/bin/csh -f

# Get all - options and pass these to xterm

set xopt = ""

while (.$1 =~ .-*)

  set xopt = "$xopt $1 $2"

  shift

  shift

end

if ("$TERM" == "wm") then

   exec xterm -sb -title "$1" $xopt -e /bin/telnet $1 &

else

   exec /bin/telnet $xopt $1

endif}


Use \italic{pipescript} as you would use more.  It does not clutter up your 
\italic{xterm} window, has no limit of data it can hold and works with all 
the other AUIS components.  Try something like "\bold{tar tzvf 
[path]/auis63L?-wp.tgz | pipescript}".


In Slackware 1.2.0 the backspace key may not behave as you would expect. 
This can be corrected with a \italic{xmodmap} entry  "keycode 22 = 
BackSpace" in your \bold{$HOME/.xmodmaprc} file and then invoking 
"\bold{xmodmap $HOME/.xmodmaprc}" in your \italic{.xinitrc} file.  You can 
also edit "\bold{/usr/andrew/lib/global.atkinit"} and change the key 
bindings.  Look for the word "\italic{Remap}" and follow the comments.


The \italic{ez} popup menus have been reduced to just four menus, rather 
than the 15 that would normally be there.  That many popups just get in the 
way.  Everything is available from the menubar, however.


Users with some display adapters like the ATI GUP+ may not be able to see 
the mouse cursor in some cases.  These users need to add '\bold{Option 
"sw_cursor"}' in their Xconfig file.


The preference "\italic{print.printer}" is obsolete and will not work with 
this release.


This package has been set up to use \italic{\bold{ghostview}} to preview 
your output.  It is configured to use a shell found in 
\italic{/usr/andrew/etc/atkpreview}.  You could either modify this shell or 
change the command used to preview with a preference entry something like 
"*.previewcommand: yourpath/atkpreview /tmp/%s.n".  Look for this entry in 
your \italic{preferences}.


Yes, \italic{\bold{atkprint}} and \italic{\bold{atkpreview}} are written in 
C-shell.  That is a requirement for now until someone else rewrites them in 
\italic{bash} and sends them to me. \



The normal command for help in AUIS is "\italic{\bold{help}}" (found in 
/usr/andrew/bin/help) which conflicts with the \italic{bash} command of the 
same name.  To assist with this, I have provided a shell 
"\italic{\bold{auishelp}}" which will simply invoke the correct help.  You 
can also invoke this help by selecting "\bold{AUIS Help}" on the 
"\bold{File}" menu.


This package has been set up to use \italic{\bold{groff}} and 
\italic{\bold{ghostscript}} to generate a PostScript stream for the printer 
named $PRINTER.  It is configured to use a shell found in 
\italic{/usr/andrew/etc/atkprint}.  You could either modify this shell or 
change the command used to print with a preference entry something like 
"*.formatcommand: yourpath/atkprint /tmp/%s.n |" (yes, this ends with a 
pipe symbol).  More detail can be found by entering "\bold{auishelp 
preferences}" and searching for "\italic{formatcommand}", 
"\italic{previewcommand}", or "\italic{printcommand}".  Look for these same 
entries in your \italic{preferences}.


Sometimes the fonts look rather ugly.  This is because AUIS is asking the 
X-server to scale the fonts dynamically and sometimes this does not work 
out very well.  You can control whether AUIS asks for scaled fonts or not 
with the preferences entry: "*.ScaleXFonts". If you do not scale fonts, 
then successive calls to "Bigger" (for instance) may not result in a font 
that you can SEE is different. When it prints, however, it will have the 
larger font.  This has been left to default so the fonts are scaled. 
 If/when we get better scalable fonts (like Adobe fonts), this will no 
longer be an issue.


This package doesn't do a very good job for our non-USA friends.  I'd 
appreciate some guidance here.  What can I do to make AUIS better for you 
folks?  This is a solicitation for notes/files to include in the next 
release,  not for more questions. :-)


You will need to have the C-shell (/bin/csh) installed to use all of this 
package.  This is most likely just a symbolic link to /bin/tcsh  (e.g. ln 
-sf /bin/tcsh /bin/csh).


Check Spelling will work with GNU Ispell, version 4.0, but not with 
International Ispell Version 3.0.09 (beta), 01/10/92 Copyright (c), 1983, 
by Pace Willisson. It should.


If you print/preview equations, you should modify 
/usr/andrew/etc/\{atkprint,atkpreview\} so that geqn and gtbl are invoked. 
See the comments in the shells for more details.


}

\bold{TOWARDS A MORE COLORFUL AUIS}


Here are some ideas for colors.  You may not agree and that is just fine. 
 The intent of these lists is to give you some ideas of possible useful 
color names rather than have you spend hours and hours looking at colors.


These \italic{\bold{foreground}} colors work pretty well: Black, White, 
WhiteSmoke, Bisque, Ivory


These \italic{\bold{background}} colors that go well with a 
"\bold{whitish}" foreground:


\description{\indent{Red-ish: IndianRed3, IndianRed4, VioletRed3, 
VioletRed4, FireBrick, FireBrick3, FireBrick4, Red4, \



Brown-ish: Brown, Brown3, Sienna, Sienna3, GoldenRod4, Salmon4, Gold4, 
DarkOrange4, Coral4, Chocolate3, BurlyWood4


Yellow-ish: DarkGoldenRod, DarkGoldenRod4


Green-ish: ForestGreen, SeaGreen, PaleGreen4, SpringGreen4, AquaMarine4, 
DarkSlateGray4


Blue-ish: DarkSlateBlue, Turquoise4, CadetBlue, SlateBlue3, SlateBlue4, 
RoyalBlue4, DodgerBlue4, SteelBlue, SteelBlue4, SkyBlue4, LightSkyBlue4, 
LightBlue4, CadetBlue4, PaleTurquoise4, DeepSkyBlue4, Cyan4


Violet-ish: Maroon, Maroon4, DarkViolet, DeepPink4, Pink4, Thistle4, 
HotPink4, Plum4, Orchid4, PaleVioletRed


Gray-ish: Wheat4, SlateGray4, RosyBrown4

}}
These \italic{\bold{background}} colors that go well with a \bold{black} 
foreground:


\description{\indent{Brown-ish: Tan, BurlyWood, Sienna2, SandyBrown, 
DarkSalmon, Wheat, LightSalmon2, Salmon1, Salmon2


Yellow-ish: GoldenRod2, Khaki, LightGoldenRod


Green-ish: AquaMarine, MediumTurquoise, PaleGreen3, DarkSeaGreen2, 
DarkSeaGreen3, DarkOliveGreen3, DarkKhaki


Blue-ish: CornFlowerBlue, DeepBlueSky, SkyBlue, LightSkyBlue, CadetBlue3, 
PowderBlue, SkyBlue2, DeepSkyBlue2, Cyan3, PaleTurquoise, PaleTurquoise3, 
Turquoise3, Azure2


Violet-ish: RosyBrown2, Plum, Thistle, Thistle2, Thistle3, MediumPurple1, 
LightCoral, LightPink2, Pink2, Plum2, Orchid2


Gray-ish: DarkSlateGray3

}}

\bold{Example1}


Here is one person's selection for colors. To try this, remove all 
references in your \italic{$HOME/preferences} file to color and copy these 
into the file. \



\indent{EZ.BackgroundColor: DeepSkyBlue4

Typescript.BackgroundColor: SlateGray4

*.PopupForegroundColor: WhiteSmoke

*.ForegroundColor: WhiteSmoke

*.DialogBackground: Gray50

*.cursorforegroundcolor: FireBrick

*.MenubarCardBackgroundColor: SkyBlue4

*.MenubarGrayItemColor: PowderBlue

*.PopupBackgroundColor: SkyBlue4

*.ScrollBackground: VioletRed4

*.BackgroundColor: LightSkyBlue4

}
\bold{Example2}


Here is another selection for colors.  To try this, remove all references 
in your \italic{$HOME/preferences} file to color and copy these into the 
file. \



\indent{EZ.BackgroundColor: SlateGray

Typescript.BackgroundColor: SkyBlue4

*.MenubarForegroundColor: WhiteSmoke

*.MenubarItemColor: WhiteSmoke

*.PopupForegroundColor: WhiteSmoke

*.ForegroundColor: WhiteSmoke

*.DialogBackground: Gray50

*.cursorforegroundcolor: FireBrick

*.MenubarBackgroundColor: LightSkyBlue4

*.MessageLineBackgroundColor: LightSkyBlue4

*.BackgroundColor: LightBlue4

*.MenubarCardBackgroundColor: CadetBlue4

*.PopupBackgroundColor: CadetBlue4

*.MenubarGrayItemColor: Cyan

*.ScrollBackground: Cyan4

}
\enddata{text,728192}
