B1171 90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 90061 HP Visual User Environment 3.0 Users Guide Jul92

B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 user guide pdf -FilePursuit

B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92

User Manual: B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92

Open the PDF directly: View PDF .
Page Count: 686

Download
Open PDF In Browser	View PDF

HP Visual User Environment 3.0

User's Guide

HP Visual User Environment 3.0

User's Guide

Notice
The information contained in this document is subject to change without notice.
HEWLETI-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this material.

Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be
obtained from your local Sales and Service Office.

Printing History
The printing date will change when a new edition is printed. Minor changes may be made at reprint without
changing the printing date. The manual part number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or document product changes. To ensure that
you receive these updates or new editions, see your HP sales representative for details.

July 1992 ... First Edition ... B1171·90061 (Rev. AI

Hewlett-Packard Company
User Interface Technology Division
1000 NE Circle Boulevard
Corvallis, Oregon 97330 USA

Introduction

HP VUE is shorthand for Hewlett-Packard Visual User Environment.
Assuming you already know what Hewlett-Packard is, that leaves "Visual User
Environment" to be explained.
HP VUE is an
environment and a set
of powerful
applications

HP VUE creates an environment for interacting with your workstation. The
environment it provides is called a "visual" or "graphical" environment
because it provides things you can see on the display that guide you through
performing tasks. HP VUE also includes a set of applications that make it
easier to interact with your workstation and extend its functionality.

HP VUE is an
alternative to
commands

Computers understand commands, and commands often have complex rules
and syntax. In the absence of HP VUE, you must learn the commands and
type them in exactly the right way to accomplish a task. When you are
running HP VUE, you can issue commands to the computer without having to
learn the commands.

HP VUE provides
controls you can
maniputate

In HP VUE, commands are represented by controls drawn on the display

that look much like buttons on an instrument panel. You use the mouse or
keyboard to "push" the buttons. Since you must be able to find all these
controls, the designers also fashioned a number of standard control containers
such as menus and dialog boxes.

iii

HP VUE uses many different types of controls.

HP VUE extends the
functionality of your
computer

In addition to making it easier to get things done, HP VUE extends your

computer's capabilities. For example, in an ordinary command-driven
environment, you have one command line. With HP VUE's windows, you can
have many applications running at once.
HP VUE also extends some physical limits of the computer. For example,
most systems have only one physical display. HP VUE makes the most of
that display by providing multiple workspaces. Each workspace occupies the
entire screen, and you can switch from one to another.

HP VUE is part of your
workstation's open
system

HP VUE is one component in a layered, open system. An open system can be
adapted and extended to meet your needs. Since the building blocks of HP

HP VUE includes a set
of applications

In addition to providing you with an environment that provides windows,
workspaces, and easy-to-use controls, HP VUE includes a set of applications

VUE use industry standards, you can easily integrate other applications into
it, providing a way to start the application in its own window without having
to type a command.

that help you use and customize your workstation. For example, Text Editor
and Icon Editor provide an easy way to edit text files and create your own
icons; Style Manager is an application for setting your own personal color
scheme, fonts, and other aspects of the appearance and behavior of your
system.

HP VUE is flexible

There are two fonns of HP VUE.
Depending on your system and your needs, you can run:
• HP VUE sessions. These provide all the features of HP VUE .
• HP VUE Lite sessions. These are scaled-down versions of HP VUE that run
run faster and require less memory.
You choose which type of session you want at the login screen.

In This Book

This book explains how to use and configure the HP Visual User
Environment, version 3.0.
Before using this book, you should examine the HP VUE Quick Start Guide.
It gives you an overview of the product and a brief introduction to its major

components.
This book is divided into two parts:
Part 1: Using HP VUE Chapters 1 through 10 explain how to use HP VUE
to perform common tasks such as logging in and out,
manipulating and editing files, and customizing your
workstation.
Part 2:
Configuring HP VUE

Getting Help

Chapters 11 through 29 cover advanced tasks in
customizing the appearance and behavior of HP
VUE. Many of the tasks involve editing configuration
files; some require you to log in as superuser
("root").

Most of the information in this book is also available as online help. You can
get help on a particular HP VUE application (for example, Style Manager)
using its Help menu.
To browse all of the HP VUE online help:
1. Choose the Help control in the Front Panel (the icon with the books and

question mark). This opens Help Manager, which lists all of the online help
installed on your system.
2. Find the underlined title "HP Visual User Environment, Version 3.0."
Choose this title to list all of the HP VUE online help.
3. Each underlined title represents a help volume for an HP VUE application

or general subject area. Choose any of the underlined titles to display the
, online help.
For more information about getting online help and using help windows, refer
to Chapter 4, "Getting Help."

Contents

Part 'I. Using HP VUE
1. Introducing Your Workstation '
Your:Workstation Environment
Choosing an environment . .
Intro<1ucing HPYU;E'
'
,
Introaucingthe.;conson~ environment·
Summary of Featu.res' ",; ~ " . .•
Information ~AQowt Your W6rks1{~tion

1-3
1-4
f-5

F·7
1-8
1-9

To find a topic by keyword . . . . . .
10 change the topic display colors . . . .
Browsing Help on Your System . . . . .
To open a help volume using Help Manager .
Displaying a Man Page . .
To display a man page
Printing Help Topics . . .
To print help topics . .
To choose a printer for yourself . . . . . .
To choose a printer for all users .
Accessing a Help Server . . . .
To configure access to a help server . . . .

5. Managing Files and Using the Desktop
IntroduC,ing the Desktop '. . .
'rhe Hierarcllical File~ System'
Eile Ownerships,and'Security' . . .
Basic File Management Skills· . l'
To s~lecta' 'Single rfile ordiIiectory
Ts:select'. multi ple'::flles .and. dir~ctbries
To.reJ:l;a~~':fi fil~~5)rdi:r~ctory ..' ;. ;f'<.
i"fT0',g~i .help !~n.a P'I!leiot'~iret·t~~~ !0'5~
, ., To ~open a"file ,01' di·reetory:·
ToAr~1P~ftleb or'~iFecto:r;y
'jnTor:dlspJ~t a.p.ofH1P menu ....
. Ma]):i p1i~~ting'Fjl~s!~n;9 Dire~t9rle.~.
..T0\·treate~ 'n~w'~e prd1Xectory
T0ni0ve"cL file·orIDreetory
..
TQtt?py.afil~: . ~ :~l.. .~. . . . . . .
.'r~;Rc,~ea~·e?·a ·~ypx~~ilc.:link k~"
J

5""4
i~'-5

·. ;...... k

.....,

.•... . . : ..

i '

.,..

•

To ch~ltg;e !th~·o-#n~r ~f,
t ' d . . t' t l ' an;;;.
. d "1'ogQu
" "t'
;11~!7::,j
L:~ r~Il' s,ys .em'" WI •. escr,Ip ~,~.
a
.... 'tq'~qp;,:a4i:ffereRt,,~;setvei,.! ';:rf;i;~j'i,,> .~' •.•.
1~'''~

Og1;

~~~~f~h~()gi;Q.' Manag~:r ]Jat~a~~s,.~r;~d:nihistr~tioll
1q;;cljs~1;CljY! ~Dgin~~~,:~~ 7\ ~ '. ~
!

••••

\,to .r~tea~,LqgiIl. ;Ma~ager; C,?Ilti~~J1'a~ion ~les ...•.

,1Logih'Y~Ila.ge~ tPQIlfigttrati8n~~1~~;:(tnd Concepts
';;;The:defa1l1t LpgiIl.Manager !d:m:figuf.atjon i • ; . '
L6ginM;an~ger Files . ~'. ,~
t;' • i.- •• • .•.. '
How Login Manager starts 'an HP.YUE session
!'.

.. :

•

Special;'C,?Il'figllr~ti9~s

'. '. . . > ' < "
COlrftgu:r~~g;Cltat~cter~Display :Con~oles.. '. . .; . ' . "
C?ir~~re a shafac~er-'disI>}ay,~oIlsolei~ n~ bit~a,l?

t?'

},. (di~plC1fi~I>resent ;:'. ......:: '.;:;~ ..;.~. '<7 J"
'~'ro \~9nJig~re q,; Gltatracter'-displaY'i9pnsole ,if· a'])itul~P;:';,
. :ai8play~xist~
,
'~"~
",'
CO~~~1l~i.Ilg;~-rer;m,lna18: " ".,r:,.,'::";'. " " , • • • •
"Tdb?irfig#r.e"te!lIl:inals",that' su:rpor~ rXDMCP .
To:; liIriif acc7:sspy, Xj:termJih;'I'o~cquItS0f~bench

; ':."

:,"

;

;;CdIlfiguriIl.g;A1!dioDeyices(HP-U~(jIl.lOT)

•

.. O.'~
,+0 ,~yart th~ ;NCS10cal Location Broker Daem0nat boot

'.,' ,1~~e. ..~. '. ...~;;, .' "'. ;

;'. To ;~tart ;the
\:~

audioseI'v~r

. • '.":,

•

13-13
13-14
13-14
13-15
13-17
13-17
13-18
13~i9
13,19'

J,3-20

13~~)

; 13;21

13-22
,13:-23"
13-24

To use a shell environment file with' .vuep rofile ,
15. Administering UP VUE Sessions
How Session Manager Works
Types of HP VUE sessions . .
Location of Session Data . . . .
How Session Manager chooses the session to use . .
The First HP VUE Session . . . . .
Customizing Sessions . . . . . . , . . . . . . .
To create a cttstomizedfirst session . . . . . .
To execute additional commands atsession startup
To use a different window manager
To create a display-dependent session . . . . .
'I'D customiz~the'fail-safe session .
Re~t9ring' RemoteApplications. ' : . . .

14-11
15-3
15-3
15-3
15-5
15-6
15-7
15-7
15-8
15-9
15-9
15,.ln
15~11

,l:~_gr

}:6-9':
16~9

, :16~9
1~:!16

16J rO'
It>":!!
,\;11116":'1'1
,'(,]t~~ir

. 16':12'

;t;;'126/t

Yf'~tl~l~(.

'disiplay ~nj'co~,in'.ar, .• FfontPane('cOItt~cil'. . .
10 associate an icon 'w1than~;appii6ationwindow ..
T9 use File Managet as, an icon browser
'
Itonl)esign, Recommendations
..
Color Usage.. . .~', . . . . .
..
Icon Size R~commendq#bn~.
.,~

. .

17. Customizing the Front Panel ,
Modifying the Front Panel: An Introduction . . . . .
To" create a personal Workspace ManagerconfiguratioIi
file ('vuewmrc') . . . . . . . . . .
How the Front Panel definition is organized. . . . .
Modifying the Top. or Bottom Row . . . . . . . . .
To adSl or delete,a control...from the top or bottom row
To modify a control in the top or bottom row.
,~xaInple:. tdding' a ~?ntro~to the hbttom' row
Creating' and ~o~ifying?1:l,bpa~els '. '.. . ": . .
System ·s~bpanelcoI\~guI:(ition:fi,les, . ': ' ..•'. . .
To,~dit a system- wid~BU hp~nel \~gnfiguration. file
To createaper~bnal subip(i:uel ~op,figuration file .
To add 0~ remove a control from an existing subipanel
To ada a new sllbpan~l;. ','. '.'
~
.....
" lIefiningF+o~t P,a:iiel,.9dnt:ti()~$.
. .. . ,
. To,~;eate)t.ipll:sp'bll,t:t?n 'fqrant(ipplic~tion
TO,cr;eate "a, push'b:~ttona~ddf()p' zon~. .
Tpcrea,te acontrol.thatmbhitorsa file. .
"'To. c~ea~eaone':instanc~'!(toggl~) control '~
To~~teate"a cU,ent.~indow 'control . ,~ c', ,', •
sTp:~niIn?te a butt~Jl ; L , . '.:,. , " : . " : .~
E)C~pl~:/q~~a6Jlg a: dr~I,>.zoJlr to~s~~rt a ,JermiJlal
'Gen~!aa..Front P~ne~eO~n!!'g~ratiph.\, ,.'
. ':
f4B '~lta9&e,t~~7:tump€lF,;?f, ~0x~s~ac~~
'.1 5:'1;# 'coIl;~gur~}lie:" ~p~ceYjsw~tt~r{.
,

'~F? ~~" ~kal~i~d"ei;~~~ Er:ofi'i'~>' p~~¥ lo~~~iQIl;
to"nl.C, U:~,91;;[J,e;r:,xes:;.~ .::t,.

Sf.

·1,

',,1,'

t •. " .. _

'ate~a,n 'efi~iteiYti tleWL fr9rit:pa;n~1:~
. . ' d ::. ":i:"
",.' ....... : : ".
~ Ea.:~llt raJ}.,~l

. A,Q. erillg:i t '
t~\ TS, i;nc!ha~*aJ
0::z;~x:a~ple:
;:It

i"\ ..

.
17·3
17-4
17-7
17-7
17-9
17,,9
17-11

.
.
.

17~'1}

17-12
17-.13
17-14)
17.-14'
17-16
H7716
17-17 '
17-18
17-19
17-20
17-21
17':22,
1J':214
,

1.7~2~

:i7r~25;'
17-'2EL,

, i1~26 '

)7-'2~'
:(17i 29
1: Ii;;

'i71~9,
i '7~$o;,~;4i
'<;;>,\l

BACKGROUND_ TILE field
CLIENT _GEOMETRY field
CLIENT _NAME field. .
DROP _ANIMATION field
DROP _ACTION field
HELP _STRING field
IMAGE field . . . . . . . . . . .
LABEL field . . . . . . . . . .
LAYOUT_POLICY field.
M 0 NITO R_FILE field .
PUSH_ACTION field . .
PUSH_ANIMATION field
PUSH_RECALL· field
TYPE field . . . . . . . . . . . .

17-34
17-35
17-35
17-36
17-37
17-37
17-38
17-38
17-38
17-39
17-40
17-40
17-41
17-42

.18. Terminal, Mail~r, Editor, and Printer Configuration
Ohanging the De~ault T~rJUiIlal, Editor, and Mailer
Tocha:uge the4efault TermiIl(;iLEmu:Iator .
To change·th~ defauJt.e,ditGr
To>cfienge'fhe.Aefau}t·' ro ailer ..

18.:3
l8-'4
18-4
~8-5

'C~stotrii~,~p.g. P'T~Ilt~Ilg .' . .• ,."" ..'
.. '. ..... .' ,7. • . . . . " .
:fa
~e0tlie 'p~in~er,.q~9P. ZOJ;lg ahd. File Man(}ger.fdnt
a,.ifd" c'

' , .. " :

".y.

'.:

•

it~")b~)ih~ t~·~~~t~t:;~2~.~.h·bdtt·9~·

:fa €~~' .. 'li[te;~;cp};lttT!6 . ; . . .'"d

1e;I.Pri};l1tetssubp arie

18+'6
'{'

. ..

TO:~i;ctT!e:ate,a,.;pe~~oIl~&ifp·:printef';Q.le:<. . . . . '. . . . .

1'qad~"aJlothe{'piinter control :to.tlie ~dnters 8ubpanel
~:xaz[npl~;Adaing ,Qrptinter,eontrol to the Pri1}ters
i.H,l1b~aIleJ. . . . . . . . . .
:
1'0 . pr~Vliq~;~e- ty;pe de~~Ilde~t~rintinp . ,',
.E:xa,.~pl~: pToji ~ing;file7 typ·~ ;~epen~::n,t print,iJi,gi;f.
Top;c;
'~re Help/M
r{irdIl~ing: vI.'
.,'

.> :

','.

<:j}<; ~t

t9~3,t(

':''i9:-4'

19~~0

,,*j~19-~:r

d§'i:q .
•,)1
ij'?,19-9

21. More About Actions
21-3
Creating Actions Manually . . . . . . .
To create an action manually . . . . . . .
21-3
Example: creating a COMMAND action . .
21-4
•
21-6
Example: creating a MAP action ,'c. "
Building the Executi()n String for a COMMAND Action.
21-7
To create an action, that uses no data . . . . . . .
21-7
To create ariaction that acceptsadroPI>edfile
21-8
To create an action that prompts'f()ra file argument..
21-8
Tocreateanadion that. accepts a, dropped file or
prompts for one . . . . . '. . . . . . .
Tous~ the~()st:ftle.f()tlllat in acor,nn}mand line . .
To pr~~pt "{orela D..~n+ftle argument'! '" ~, ' i " • • •
1'.I'0 pr()vid~'. Bc~ell~apabili~iesi iD."an~c~i0n.·",' ','" • .
';··TC;1Z(ipfQy;hilealffe['ellt:B.douqle+di.~k,.a;fi9. drOP.1;Lunction for an
t
yi"\

?j:.!

Customizing HP VUE Lite

23.

Administering HP VUE Lite Sessions . . . . . .
23-3
To make HP VUE Lite the only session available
23-3
To customize HP VUE Lite session startup . . .
23-4
To start clients in different workspaces . . . . .
,23-4
To set resources for the first HP· VUE Lite session
23:.5
To set resources during an HP VUE Lite session.
23-5
How HP VUE Lite sessions are started. . . . .
23-'6
Customizing 8P. VUE Lite Terminal Emulators . . ".;
23-7
To use a different terminal emulator inHP VUE Lite
23-7
To customize the remote ,terminal buttons .... . . .
23-8
Toaddacontrol.to the Terminals subpanel . . . . . .
23-8
To create a personal Terminals BUbpanelconfiguratibn
file. . . . . . . '. ". . . . . .' ..; . . . . . .
ExaIllple: A:d.diii~;(tterminal to ,the 11~,rfuinalssubp:anel
Adding: App1i<;ati~p-~;~an&\Vtilitie~tpi¥f ViUE Lite ",
',T6:assigl};,(tiL,app;Licatiori,to the1:I;p,VUE ,Lii~ Tools
.\
. "control'. ,~i~;:F'~{\;'i~ , , 1 " '~" '.
0i:To\C:)d.d'a~j. '
. n~?'~lle'1,;'PeJs ;e~~paIl~I "

1:~~ea~~f:'~t

Q~l$~ s~~p~¥~l~l~.'J'

,ii'

..... "

'; i ' ,il~:. , ' " ,.",,¥:(tti,pn ':~O:t~~l?i. . .1\S'subBian~l •.
r;p.;'CI:~
(?jll~l}; '~p/ V;UJ;".Lit~t': , ) '
tC;>'~f.kJl'~iAS ... 'i...;Wid~, 'iatt~orr'~il};i:HPtV.UE Lite with
:,{J~~aAieJ\.ct19nl.N~, ,.:,,~ '..c.' '~i'\
.
To'ru~'anr ~~tioiL;from; t'he 'command line
{'

,.,:"

, .: t

;/,,}~"

, '.,'

C~st()mizi~gwor~spa:~eMana.ger . •

Work$paceM9!l};alg~~ CiQnfigui~tiollFil€l.
f;Tq,edi}'Nu;~:WJJ?-~C(tT.t'~~ . .
~ '.:,.' . :
To;inl:l11d~ oitli~r;::~~~lhl . YU€l.wm1;9:'

qustQm,i~i~g'
k,~~~c~s~",/;,;::"
)
\fl;Tq,tClliifit!Jli..
.'~olt1FQ:f1~,'w
To ;Ill~~~:a . i,~R:' b~c¥diFoP: ..' .)
!J,TQi~liSJi1at;.~!te··f90~ '~irr~Qw' il};' ',.. ,woxllsp:ace'
';Cust9',>YVindoYl,i . . . ponents".·~,:, /'
T(f:s;pe~i~Y(:\Vip:~9w+fram~~om,DOP-€l~~S.,.
.TIll" setr,'Rtont Ranel' d~Acoi'atidn~ ..'~ "~.
"To set 'suhpanel"de~r'atibnsY .
.~
. "rd';, manuarl~; setwlnd:ciw'ftarn~,,~tilori!' , .;

R,'

:,!,.", ',',

l' :" .;\f'><~:>

"',,

:>,t.'

"j"

.\~ .~:;

;:::>'

•

,c)

*2.4-3
24:;3,;
24-4
.P24::i6,.!
24,.~

.'{Y'2kt~7'd
"';>24'.;:8.,

..
i';

24~\LO ,
2~~11/
·.24-13:f

.,24~;lt~/···

'\~24~t4

"~~·o~':.~P~~~t.~~ce,,

wQ:rk§pac~ ~ManagerX~'enus. '
" ,WotkSP&¢~;~~~·ag~i~m~:n.usynt·ax:

'J:'?:us~

&; Sust9tri:wd~kspae~ID-ellu \
TOllse.'.a'tUJs~.qm,~in(l0-wU\€nUJ';' .
'CustoPllzipg :Qutt'ollBin"dings .' " .
Bu;tton"biJldlngy,syntax
. .. .:
To cteate'aA:ustotri :\buttbn hiRdbig set'
Customizing Key,Bitldings' . . . ; . .
KeyboarH'"biridlng,sYIltax. .' "~ .' . :
To create a c'ustoinkey'bindingset
Switcliing between default and custom behavior .
Refere:nce:WQrkspace: Manager
. ., ,

Using Resources
Setting;"Personal:Itesource~for ·a~ Ap~lica~ion

, 'TQch~l1gef~soi~c,~s 'Wiith' Styl~ :rwallager:r~;
::T().'~et . ~es9~rc~.~.'usiIl~' tp~;.E~iiRe~purc~~.ac:~ton
TQrcre~te a:.·bac~.~P resourc'e, :q~~ , ' "~' .; "..
~1:o!ad9~;re~~tEtse~us!.~g .4xdb . ~ ~'... ' ..... ~ ,
"TQ' :replace "~ur;rellt:;fesources l1sing xr4.b'
':7'J:'o~eleted~s()Jlft:es: .•. . . ~;~"
~$!ett~ng Sysi'~m~~ide:;*es~Jl'rces .'.' ';".'
, :1:ose~; 'sys:!~so1:i:rces;for;fitst §~ssi97U
T-1 se( sys.res)~ie::for' V.UE,Lite
'
Refere~ce': Y.ltesg1irc~$

S'yntax ofresol:lrc~speiificaf,funs . ' .
'!Iow'~lie~:~s' g~t"f'~sou:r;<:~s, "
SCQp;e :~Qf resq~rc~~'
.

" '~yst~~~~~Ollrc€,files
Pecrs6naCresou'uc.e 'files
ITh~··..:ItES.oiIR,€E;MAN.AGE~::.~:oI>e,rt~
g1>~cifyi~~t r~sollI'<;es, r~ a mU\and, ~ille;..
R
r"es'\~;d:~~che~l ;die:n.ts

3'fg

26. Font, Color, and Application Resources
Managing Fonts . . . . . . . . .
To set HP VUE font resources
To list available fonts . . . . . . . ,
To specify fonts on the command line
The X Logical Font Description (xlfd)
Managing Colors
. . . . . . .
To, set palettes .. . . . . . . " . .
Color sets '"
,. , ,.
To set the tolorH se resource
To set pixmap shadows ~ ,
To .,set the foregroun"d cgloJ;.
To use dyhamicJcolor
':['0 compute number, of colors a palette uses .
To limit the·;numher of.co\()rs """. '
. ~Q: map?olorst,o $.<;reel;l,!ele"rriel1~~.,'
'; +}iP'W c?lots l1!rces«.~,:'

26-3
26-3
26-5
26-6
26-7
26-9
26-10
26-11
26-12
26-13
26-14
26-15
26~16

'2~-17

2~-l7
26-19

28-21

S~yh:~'JVranagel) Ites9qrc~s
.,File 'Mariagerpi:ResO,nrces.;
'~~>}¥,~, <~ ,j.;~; "'. t~tfi
:/'. ';'.' ,~; J,\b' \;: <,~,:

. ;~7 ~.:l~ «ori~~~g1i~1t1~
"ri,l~set~;~~"

,;,,~, \f£;

~ }Z~?,

~Lt,~ '>~' fi~~~; ~~~

•

Reference
Supported Languages
Locali 4.edJc:on S~arch.· Path .
Font Locations. '. . '.' .(.. . . .
28. For Previous HP·VUE2·~Ol QrXll Users
New Locations for,· HPVUE' Configuration Files
Session Management (HPVUE2.01 to HP VUE 3.0)
Display-dependent and display-:independent sessions,
The firstHP VUE 3.0 session (HP VUE2.0l to HPVUE

3:0)'. '. ' . . . . '. . . . ' . . . . . . . . . . . .
To create a display-independent session . . . . . . .
MQving an HP'VUE 2.01 FrontPane,J to. HP VU~ 3.0 . .
What 'happens t9 your' HP VUE2.0l Front Panel when
yom log into HP VUE 3.0, , . . . . . . " , ' .
T08witchJ:romthe HP . VUE 2~01 Front Panel to the HP
~iVUE 3.0,~.Fr0nt ·P~nel..
' .... .' .' . . .~.. '" ... ~
T6c,()n~~rt·, the 'syntax. of ¥01lf HPVUE f.Ol Front P~nel
to HP VUES.O,
. . . ~. . . . . . '.
Accessing applications (HP'VUEj.2.01·tb HJ:> VUE3:0). .
How: IfP '~UE.3J)~provides;4isplay access f9r remote
. : ap'pli~ati~):ns,. . . .:':~; ", .. . . . . . ;"
. .'
To display HP.¥UE3.0 tool~i;frotnthe HI' VUE 2.01
FrontP(1nel .,',:, , . • ..•. . '~" '. :. ~ . . .~ . . , "; . . .
To display lIP!¥VE 2.01 tool~ "from the' HP VUE 3.0
to,olboxes~ :. '".; " " " . . ,.: . . . , . . , .;
Tq,tn0ve thetH~ VUEj 2.01loca:l~a,p,p~i.to the.,Gene!~l
, .':roolbox. ..:'. ."
. . . ', . '.. .;' ...:. ,.:~:.
\Io lU();ye,:.~P~UE' 2.qt rem~te'acti~n:? to the: ~ etw~rk ".
",~: ~9Q!bQ~(;,. ' .." " , >•..~ .~ .• ';/:'~':;";' ;'i~'" ;. '.,~. • . ' '~. >,',
~i~et!fti~~~d AiVUE :3 '?2.' . ,~" .
, i~1:i~t,:pallP,,~ns:,;t@HPVtJE< f·Q.~3 a;cti8n~ > '." • .' /: :<, 'i" ' . )
T~.c%~¥€rt'If~'~~JUE ~.l)151~tfllh~sefil~s"'t~~ ~P.;VNE;~fo' ,','
KV'~yht~t';

'i+'

,.15

:::';,;5,: '~:,,'; ..~;f,;';V'

"j~erta1n~~P:fyU;Ef:~2tyQ~h B3J~kd~.~p.~~re RepiRced ,.

).{[oMi~g,f;ff?mz~.1.l'~FQ;~B;~yEJ&?;~'d, »~1rL~;

•

T0:'lise y~ufIA~.tL:~~~iFl()~1heht,t~fiabLes); . ' " .~ ... '
s\Tomte
Pia'. ;~;;i;;'l;'."
Xl•.l;i;l',esollite
". ""into
HSE?fZ.~rU~' ,
j."
" ," ' .
:Z'~.,j:;!;£:' .' .'
....•;

28-3
28-4
28-4
28-4
28-5
28-6
28-6

28-8..\
28-9

28-9
28-1C{
28';.10

28 ..11;'
"28,,,.11
28-1p. ;,
\2a,~13

29. Troubleshooting
IfHP VUE (Login Manager) Doesn't Start
Files that monitor errors .
. . . . .
Trou bleshooting utilities
Monitorlngerrons
Diagnosing common errors
Action and filetypeertors
,If the Broa.dcast: Message Server Fails to Start

Glossary'
. Index

29-3
29-4
29:'5
29.,§
29:;5 .
29-0
29-7

Contents

·Part 1

Introducing Your Workstation

Your HP workstation uses the HP-UX operating system and the HP Visual User
Environment (HP VUE). HP-UX is a versatile operating system that you can
use to run application programs and perform a variety of tasks. HP VUE is a
powerful graphical environment for HP-UX that simplifies many of your daily
activities.
Installing your
workstation

If you have not installed your hardware or started your workstation, please

refer to:
• Your workstation's Installation Guide .
• Your workstation's Owner's Guide.

1-2

Your Workstation Environment

Once your workstation is installed and running, it will display one of two
ways to log in.
Workstations running
HP VUE

If your workstation is running HP VUE, you will see the HP VUE login screen:

Workstations not
running HP VUE

If HP VUE is not running, you will see the system console login prompt:

Console login:

1-3

Introducing Your Workstation
Your Workstation Environment

Choosing an environment
We recommend that you use HP VUE on your workstation whenever possible.
The powerful features of HP VUE make it easier to learn to use your
workstation and extend its functionality. HP VUE is also very flexible.
Choosing HP VUE

You will want to use HP VUE if you:
• Want an easy-to-use interface. You'll still be able to type commands if you
choose to do work that way.
• Want to run more than one application at a time. You can run applications
that create their own windows and applications that must be run in a
terminal.
• Want to run the applications that are part of HP VUE. For example, HP
VUE's Text Editor application provides an easy way to edit files. Its Help
Manager lets you access extensive online information.

Choosing a console

You will want to use a single system console if you:
• Want to run a single application that uses the entire display, such as
Starbase Graphics or a CAD application.
• Want to use the XII Window System without HP VUE.

If HP VUE does not start
automatically

Under certain conditions, such as after a system update, or after a new
workstation is added to a diskless cluster, HP VUE may not be configured
to run automatically, and you will see a system console when you boot
your system. If HP VUE is not running and you want to turn it on, read
Chapter 11 for instructions.

Turning HP VUE off

If you need to totally disable HP VUE, see "Stopping HP VUE" in Chapter 11

for instructions.

1-4

Introducing Your Workstation
Your Workstation Environment

Introducing HP VUE
HP VUE is a powerful graphical environment and a set of applications for
interacting with your computer.

Features of HP VUE

HP VUE includes these features:
• Windows and workspaces. Windows are containers on the screen for
applications; they let you run more than one application at a time.
Workspaces provide a way to make a single display seem like several
displays. Each workspace occupies the entire display, and you switch from
one workspace to another using a control. It's as though your display had
several layers that you can shuffle.
• Icon-based file management. Files are represented by icons that can be
selected and moved on the display.
• Front Panel and toolboxes for easy access to applications.
• Extensive online help.
• Session management. HP VUE remembers which applications were running
when you logged out and restarts them the next time you log in.
1-5

Introducing Your Workstation
Your Workstation Environment

• Easy customization for colors, fonts, window behavior, and other aspects of
the appearance and behavior of your workstation.
• Easy-to-use Text Editor and Icon Editor.
• Multi-media application for annotating files.
There are two forms of
HPVUE

Regular HP VUE sessions provide all the functionality of HP VUE.
Some models and configurations of HP workstations may not give satisfactory
performance when running HP VUE. If you wish to exchange some HP VUE
features for enhanced performance, you can use HP VUE Lite by selecting it
from the Options menu on the HP VUE login screen.
HP VUE Lite is a subset of HP VUE. It features enhanced system performance
by omitting full icon-based file management, full session management, and file
annotation.

Entering commands

While HP VUE provides an easy way to work with files and applications
using icons, you will encounter tasks that require you to enter commands
manually using a command line. Command lines are provided by HP VUE's
Terminal Emulator application. See Chapter 8 to learn how to use a Terminal
Emulator. For information about commands, see the Using HP-UX manual or
the "HP-UX 9. * Operating System Help" in the online HP Help.

There are additional
login options

You can use the Options menu on the HP VUE login screen to suspend HP
VUE in order to run a special program or to perform certain configuration
tasks. The Options menu also accesses sessions in other languages.

learning about HP VUE

This manual covers how to use and configure HP VUE.
You can also use HP Help to access online help about HP VUE. To learn more
about HP Help, see Chapter 4 in this manual.

1-6

Introducing Your Workstation
Your Workstation Environment

Introducing the console environment
The console provides a conunand-line interface for running special
applications and performing certain system administration functions.

$ ls

Learning About System
Commands

UTD. cv

OSSD. fc

anna
de,.;
ellen
kreta
patti

jodi
jim
richard

The Using HP-UXmanual explains basic HP-UX conunands that you can use
in the System Console.
If you use the console to run the XII Windows System, you can also use HP

Help to get information online. The "HP-UX 9. * Operating System Help"
contains extensive information about HP-UX conunands.

1-7

Summary of Features

Feature

HPVUE

HP VUE Lite

Single
Console

Windows

yes

Workspaces

yes

File management using icons

yes

Front Panel containing controls for common tasks

yes

Toolboxes containing applications

yes

Text editor

HP VUE Text Editor or vi

Icon editor

yes

Session management

yes

partial

Applications for customizing your workstation

yes

Command line

yes

Mailer

yes

1-8

Information About Your Workstation

Manuals

To learn more about your workstation, continue reading this manual or the
Using HP-UX manual. These other manuals may also be useful:
• If you need help with system hardware installation, see the Installation
Guide and Owner's Guide, for your system.
• If you have not yet installed your HP-UX system, see Installing and
Updating HP-UXfor your version of HP-UX.

• For administration information, see the System Administration Tasks
Manual.

• For troubleshooting HP-UX, see Solving HP-UX Problems.
Online Help

If you are using HP VUE or the X Window System, you can use the HP Help

System to access information about HP-UX and HP VUE.
The topic "Finding HP-UX information" in "HP-UX 9. * Operating
System Help" provides a database of all the documentation published by
Hewlett-Packard pertaining to HP-UX workstations.

1-9

Introducing Your Workstation

Information About Your Workstation

Starting an HP VUE Session

An HP VUE session is the time between logging in and logging out.
The login screen, created by the HP VUE Login Manager, is your gateway to
HP VUE. It provides a place for you to type your login name and password.
The Options menu on the login screen provides a way to choose what will
happen after you log in. In addition to running an HP VUE session, you can
choose to run several alternative types of sessions, such as HP VUE Lite, or a
failsafe session. You can also select the language for your session.

The Options menu lists your login options.

2-2

Starting and Ending an HP VUE Session

An HP VUE session starts when you log in. The HP VUE Session Manager
takes over after Login Manager recognizes your login and password.
Session Manager provides the ability to "manage" sessions-to remember the
state of your most recent session and return you there the next time you log
in.
Session Manager saves and restores:
• The appearance and behavior
mouse settings.

settings~for

example, fonts, colors, and

• The window applications that were running-for example, your File
Manager and Text Editor windows. Certain types of applications can't be
saved and restored by session manager. For example, if you start the vi
editor from a comand line in a Terminal Emulator, Session Manager cannot
restore your editing session.
See Also

• "To run an HP VUE Lite session" covers starting an HP VUE Lite session.

To log into an HP VUE session
1. Select the Name box and type your login name. Press (Return) or choose

OK.
2. Type your password. Press

[Return)

or choose OK.

If Login Manager does not recognize your name or password, choose Clear

and start over.
If your previous session was an HP VUE lite session, then you must select HP

VUE Session from the login screen Options menu before logging in.
Once you've logged in, Session Manager starts a session:
• If this is the first time you've logged in, you'll get a new session.

2-3

Starting an HP VUE Session
Starting and Ending an HP VUE Session

• If you've logged in before, your previous session will be restored.
• If this is the first time you've logged into HP VUE 3.0, but you previously

used HP VUE 2.01 on this system, your previous HP VUE 2.01 session will
be restored.

NOTE
Your system. administatormay,haveconfigured to lJSe only HP VUE Lite sessions. If this the case,
logging in will automatically useHP VUE Lite.

To log out
• Choose the logout control on the Front Panel.

Use the log out control CD to end the session.

• Or, choose Log out from the workspace menu.

When you log out of a regular HP VUE session, Session Manager saves
information about your current session so that it can be restored the next
time you log in.

2-4

Starting an HP VUE Session
Starting and Ending an HP VUE Session

Cancelling a Session

Cancelling a sesson ends the session without saving any session information.
It also provides a way to log out if, for some reason, the Front Panel and
Workspace Menu are not working properly.
To cancel a session, you must stop the X server. In HP-UX systems, use
for PC-10 1 keyboards).

(Shift)

( Ctrl ) (Reset) (( Shift) ( Ctrl) (Pause)

To change your password
1. Display the Personal Toolbox by choosing the Tools control in the Front
Panel.
2. Double-click ChangePassword. This displays a window with a prompt for
your old password.
3. Supply your current password and press (Return ).
4. In response to prompts, enter your new password twice.

To use a session in a different language
1. Select the language using the menu displayed from Language in the
Options menu on the Login Screen
2. Log in.
The default language for your system is set by your system administrator.
The Options menu lets you access other languages. Choosing a language in
the Options menu sets the LANG environment variable for your session. The
default language is restored at the end of the session.
See Also

Chapter 27 covers localizing HP VUE sessions.

2-5

Starting Other Types of HP VUE Sessions

In addition to the regular HP VUE session, HP VUE provides these additional
types of sessions:
• HP VUE Lite is a scaled-down version of HP VUE. It is useful for
limited-memory system, or in situations where you do not need all the
functionality of regular HP VUE.
• A failsafe session provides a Terminal Emulator and Window Manager. It
is useful for performing configuration tasks before logging into another HP
VUE session.
• No Windows mode lets you temporarily leave HP VUE to work in your
system console.

To run an HP VUE Lite session
To log in

1. Select HP VUE Lite from the Options menu. (This is unnecessary if your

previous session was an HP VUE lite session.)
2. Log in.
Login Manager remembers whether your previous session was a regular
session or an HP VUE lite session.

NOTE
Your system may be configured to automatically run anHP VU.E lite session. If this is the case, the HP
VUE session option in the Options menu is inactive.

2-6

Starting an HP VUE Session
Starting Other Types of HP VUE Sessions

Use the Options menu to select HP VUE Lite.
To log out

• Choose the logout button on the Front Panel.

• Or, choose Log out from the Workspace Menu.

Use the log out control
See Also

CD to end the HP VUE Lite session.

• "What's In the Front Panel (HP VUE Lite Session)" in Chapter 3 describes
the Front Panel for HP VUE Lite.
• "Using Tools in HP VUE Lite" in Chapter 6 describes how to run
applications in HP VUE Lite.

2-7

Starting an HP VUE Session
Starting Other Types of HP VUE Sessions

To log into and out of a fail-safe session
To log in

1. Select Fail-safe from the Options menu.

2. Log in.
To log out

• Execute the exit command in the Terminal Emulator.
A fail-safe session is a simple session that starts the Workspace Manager
and a single terminal window. It is useful when you need access to a single
Terminal Emulator window to execute several commands before logging into
an HP VUE session.

See Also

"To customize the fail-safe session" in Chapter 15.

2-8

Starting an HP VUE Session
Starting Other Types of HP VUE Sessions

To suspend HP VUE using No Windows mode

NOlE
Certain types of configurations (for example, X-terminals) do not provide a No Windows mode option.

To enter No Windows
mode

1. Choose No Windows from the Options menu. The login screen disappears

and is replaced by a console prompt.
2. Supply your login and password as prompted .

To leave No Window
mode

• Execute exit from a prompt.
No Windows mode is not an HP VUE session. When your system is in No
Windows mode, HP VUE is suspended. You log in using your operating
system mechanism, rather than Login Manager, and there are no windows
because the X server is not running.

2-9

Using a Home Session

Ordinarily, HP VUE saves session information when you log out and uses
that information to start your next session. If you start or stop applications
during your your session, or use Style Manager to change the appearance
and behavior of your system, changes you make are reflected in your next
session. This type of session is called a current session.
HP VUE also provides a home session. A home session is a session that
you explicitly save. It's like taking a snapshot of your current session at
some point in time. Once you've saved a home session, you can specify that
logging in always restores that session instead of the current session.
See Also

"How Session Manager Works" in Chapter 15 describes how Session
Manager manages the current and home session.

To save a home session
• Choose the Style Manager button in the Front Panel.
• Choose the Startup button in Style Manager to display the Startup dialog.
• Choose Set Home Session in the Startup dialog.
• Choose OK in the confirmation dialog.

2-10

Starting an HP VUE Session
Using a Home Session

Choose Set Home Session

CD to save the current state of your session.

To automatically start the horne session at login
1. Choose the Style Mananger button in the Front Panel.
2. Choose the Startup button in Style Manager to display the Startup dialog.
3. Select Return to Horne session.
4. Choose OK.
When you choose Return to Horne session, Session Manager will not save
your session at logout.

2-11

Starting an HP VUE Session
Using a Home Session

To choose between the current and home session for
each session
1. Choose the Style Mananger button in the Front Panel.
2. Choose the Startup button in Style Manager to display the Startup dialog.

3. Select Ask Me at Logout.
4. Choose OK.
You decide what will be your next session-current or home-at logout time.
If you choose the return to the home session, the current session information

is not saved. (You cannot change your mind the next time you log in.)

2-12

Using the Display Lock and Timeout

The display lock lets you prevent other people from using your workstation
when you are away from it without logging out. You can set the appearance
of the locked display.
System timeout automatically turns off the display after a certain amount of
time elapses in which you haven't used the keyboard or mouse. You can set:
• The amount of time until timeout.
• Whether or not to lock the display at timeout.

To lock and unlock the display
To lock the display

• Choose the lock control in the Front Panel.

Choose the lock control
To unlock the display
See Also

•

CD to lock your display.

Type your password.
"To configure who can unlock the display" in Chapter 22 explains how to
configure the lock to let other people unlock your display.

2-13

Starting an HP VUE Session
Using the Display Lock and Timeout

To set the appearance of the locked display
1. Choose the Style Manager control in the Front Panel.

2. Choose the Screen button.
3. Select Full Screen Cover: On or Off.
4. Choose OK.

Set the type of lock cover using buttons CD in the Screen dialog box.

Ordinarily, the screen is fully covered when the display is locked. You can
configure your system to partially cover the locked display.

2-14

Starting an HP VUE Session
Using the Display Lock and Timeout

To configure system timeout
To set timeout time

1. Choose the Style Manager button in the Front Panel.

2. Choose the Style Manager Screen button.
3. Use the slider control to decrease or increase the number of minutes.
4. Choose OK.
To lock at timeout

Your system must be running the R5 X server to use this feature.
1. Choose the Style Manager button in the Front Panel.

2. Choose the Style Manager Screen button.
3. Select Screen Lock on Timeout.
4. Choose OK.

2-15

Starting an HP VUE Session
Using the Display Lock and Timeout

Basic Skills

HP VUE is a graphical user interface that provides workspaces, windows,
menus, controls, and a Front Panel to help you organize and manage your
software applications.
• A workspace is the screen area where you bring the applications needed
for your work, arrange them to suit your preferences, and put them away
when you're done. HP VUE initially comes with six workspaces (four in
an HP VUE Lite session), each giving you a surface on which to put your
applications and tools.
• A window contains a software application and frames it with controls
so you can move it, make it larger or smaller, or put it in additional
workspaces.
• The Front Panel is a window that contains a collection of frequently-used
controls and services all your workspaces.
• Menus and controls help you manage and operate the software application.

3-2

Organizing the Information on Your Display

You can organize application windows by choosing which applications belong
in each workspace. For example, a workspace could contain applications used
for correspondence, such as a mailer and Text Editor. Or, you could choose to
set up your workspaces according to projects.
A window frames the application with controls that:
• Focus the workstation's attention on the application window. When a
window becomes "active," its frame changes color and the application can
receive information from you via the keyboard.
• Move the window to a convenient location on the screen or to another
workspace.
• Make the window bigger or smaller, or tum it into an icon.
• Remove the window from the workspace.

The window frame lets you perform common window tasks.

CD Window menu button.
@ Title bar.
@) Minimize button.

® Maximize button.
® Resize border.
3-3

Basic Skills
Organizing the Information on Your Display

The application decides which parts of the window frame it needs. For
example, Text Editor uses all five, while Front Panel uses none.

To open and close an application window
Opening an application
window

• Choose its button in the Front Panel.
• Or, choose its icon in a toolbox.
• Or, execute the command to start the application.

Closing an application

• With the mouse, choose the application's Exit or Close command (usually
in its File menu). Or, double-click the window menu button.

• With the keyboard, press @D+(E).
Closing an application removes it from all workspaces.
CAUTION

Before closing an application, save your work.

To turn a window into an icon
As you work, your screen can become cluttered with windows. Changing a
few of those windows into window icons tidies up the workspace. Programs
running in window icons continue to run.
Mouse

• Click the window's Minimize button.

3-4

Basic Skills

Organizing the Information on Your Display

Keyboard

1. Press @+space bar to display the window menu.

2. Choose the command:
• Press the down arrow until you reach the command, then press
• Or, press @, the mnemonic shortcut.
Restoring a window

(Enter

To turn the window icon back into a window:
• Double-dick the icon
• Or, choose Restore from the window icon menu.

To move a window or window icon
Mouse

1. Position the pointer:
• For a window, move the pointer over its title bar.
• For a window icon, move the pointer over the icon.
2. Hold down mouse button 1 as you drag it to its new location.

Move a window by dragging it by its title bar.
Keyboard

1. Press @!)+space bar to display the window menu.

2. Press @' the mnemonic shortcut for the Move command.
3. Use the arrow keys to relocate it. (Using (CTRL 1plus an arrow key moves
it to its new location faster.)
4. Press

(Enter

To cancel the move operation, press (Esc].

3-5

Basic Skills
Organizing the Information on Your Display

To resize a window
Mouse

1. Place the pointer on a window frame's side or comer.

2. Hold down mouse button 1 as you drag the window outline to the new
size.

Stretch or shrink a window by dragging its border to a new size.
Keyboard

1. Press

(ED + Space Bar to display the window menu.

2. Press @)' the mnemonic shortcut for the Size command.
3. Use the arrow keys to stretch or shrink the window. (Using (CTRL) plus an
arrow key stretches or shrinks the window faster.)
4. Press [Enter).
To cancel the resize operation, press (Esc).

To change the order of overlapping windows
Windows in a workspace can overlap, just like pieces of paper on a desk.
And, like papers, you can change the stacking order, bringing the one needing
your attention to the top.
3-6

Basic Skills
Organizing the Information on Your Display

Mouse

• To bring a window to the top, click a visible part of the window's frame.
• To bring a concealed window to the top, choose Shuffle Up from the
Workspace menu.

Keyboard

• To cycle through the windows, press @D+(Tab }.
• To bring the bottom window to the top, press @+[ESC).
• To put the top window on the bottom, press @+(Shift)+(ESC).

To display another workspace
Mouse

• Click the workspace's button in the Front Panel.

Display a workspace by choosing its button in the Front Panel.
Keyboard

l. Press Qill)+(Tab) until you reach the Front Panel.

2. Tab to the top row.
3. Use the arrow keys until you reach the button for the workspace you want
to display.
4. Press

(Enter ).

3-7

Basic Skills
Organizing the Information on Your Display

To rename a workspace

Use the Rename Workspace button
Mouse

CD to rename the current workspace.

1. Display the workspace you want to rename.

2. Choose the Rename Workspace button in the Front Panel to open the
Rename Workspace dialog.
3. Edit the Workspace field.
4. Choose OK.
Keyboard

1. Display the workspace you want to rename.

2. Use (Tab 1and the arrow keys until you reach the Rename Workspace
button.
3. Press

(Enter)

to open the Rename Workspace dialog.

4. Tab to the Workspace field and edit its contents.
5. Press

(Enter).

The workspace name can be more than one word .
See Also

• "To change the number of workspaces" in Chapter 17 explains how to add
or remove workspaces.

3-8

Basic Skills
Organizing the Information on Your Display

To put a window in other workspaces
A window can occupy one or more workspaces. The workspaces in which a
window currently resides are highlighted in the Occupy Workspace dialog.
To put a window in all workspaces, choose Occupy All from the window
menu.
Mouse

l. Choose Occupy Workspace from the window menu to open a dialog.

2. Click to select or unselect a workspace in which the window is to reside.
Selected names are highlighted.
3. Choose OK.

Select the workspace(s) the window will occupy from the list of workspace names.
Keyboard

l. Press @!)+space bar to display the window menu.

2. Press the down arrow key until you reach Occupy Workspace, then press
(Enter) to open a dialog.
3. Thb to the Workspaces list.
4. Select the workspace(s) in which the window is to reside:
• Use the arrow keys to move through the list.

3-9

Basic Skills
Organizing the Information on Your Display

• Press the space bar to select or unselect a workspace. Selected names
are highlighted.
5. Tab to OK, and press

(Enter).

Keys used to move around in a workspace
You can use the mouse or the keyboard to move around windows and
workspaces. If you use the keyboard, note the following:

• @ is the same as
• (Enter)

Within a workspace

(Extend char)

is the same as

(Return)

on some keyboards.

Keyes)

Moves to ...

@D+(Tab)

Next window or window icon.

(Shift)+@D+(Tab )

Previous window or window icon.

@D+@

Next window belonging to an application or between the
Front Panel and a subpanel.
Previous window belonging to an application or between
the Front Panel and a subpanel.

Within a window

(Tab)

Next tab group.

(Shift )+(Tab)

Previous tab group.

C!J

Next control in a tab group.

(!)

Previous control in a tab group.
Next menu command.

Within a menu

Previous menu command.

3-10

Using the Front Panel

The Front Panel provides a central location for information and applications
you use frequently. For information on modifying the Front Panel, see
Chapter 17.
HP VUE has two Front Panels- one or regular HP VUE sessions, and another
for HP VUE Lite sessions.
Top-row controls with an arrow at the top have subpanels that extend the
control's functionality.

Use the arrow controls
Getting help on a
control

CD to display and close the subpanels.

To get help on a control, choose On Item in the Help subpanel; then, choose
the control for which you want help. (Keyboard: give the control focus and
press press (£D.)

3-11

Basic Skills
Using the Front Panel

What's In the Front Panel (Regular Session)

Clock displays the current workstation time.

Top-row controls

Date displays the current workstation date.

Load displays workstation activity. This control is actually an
application displaying a window in the Front Panel.

Style Manager starts Style Manager with which you change display
appearance, such as colors, and change system device behavior, such
as mouse double-click speed.

Help Manager starts Help Manager. The Help subpanel provides
access to additional online information.

Workspace Switch displays another workspace.

Printer displays printer job status on the system default printer.
The button is also a drop zone that accepts a file icon. The Printer
subpanel can be configured for other printers.

Mailer starts your electronic mail application. The button is also a
drop zone and accepts a file icon.

File Manager starts a File Manager window showing your home
directory.

Toolbox opens your Personal Toolbox. The Toolbox subpanel opens
other Toolboxes that contain actions and utilities.

Trash Can displays the contents of the trash can. The button is also
a drop zone that accepts a file icon.

3-12

Basic Skills
Using the Front Panel

Bottom-row controls

Logo gives HP VUE version information.

Lock locks your workstation, preventing unauthorized input.

Rename Workspace displays a dialog in which you can rename a
workspace.

Terminal Emulator starts a terminal emulator window, providing
access to a command-line prompt.

Text Editor starts Text Editor. The button is also a drop zone that
accepts a file icon.

Logout begins the logout process.

Progress Light blinks to indicate an activity in progress, such as a
new window opening.

What's In the Front Panel (HP VUE Lite Session)
2

Top-row controls

Clock displays the current workstation time.

Date displays the current workstation date.

Style Manager starts Style Manager with which you change display
appearance, such as colors, and change window behavior.

Help Manager starts Help Manager. The Help subpanel provides
access to additional online information.

Workspace Switch displays another workspace.

3-13

Basic Skills
Using the Front Panel

Bottom-row controls

Mailer starts your electronic mail application. The button is also a
drop zone and accepts a file icon.

Toolbox can be configured to run an application of your choice.

Terminal Emulator starts a terminal emulator window, providing
access to a command-line prompt.

Logo gives HP VUE version information.

Lock locks your workstation, preventing unauthorized input.

Rename Workspace displays a dialog in which you can rename a
workspace.

Text Editor starts Text Editor. The button is also a drop zone that
accepts a file icon.

Logout begins the logout process.

Progress Light blinks to indicate an activity in progress, such as a
new window opening.

To choose a Front Panel control
Mouse

• Move the pointer over the control and click mouse button 1.

Keyboard

1. Press @+(Tab) until you reach the Front Panel.

2. Move keyboard highlight to the control:
• (Tab) moves highlight to another row.
• The arrow keys move highlight to a control within a row.

3. Press (Enter) to choose the control.

3-14

Basic Skills
Using the Front Panel

To choose a control from a subpanel
Mouse

1. Move the pointer over the control's up arrow and click mouse button 1 to
display the subpanel.
2. Move the pointer over the subpanel control and click mouse button 1.

Keyboard

l. Move keyboard input focus to the Front Panel control's up arrow.

2. Press

(Enter)

to display the subpanel.

3. Move keyboard input focus to the subpanel control:
• @D+@moves focus between a subpanel and the Front Panel.
• The arrow keys move focus within a subpanel.
4. Press

(Enter)

to choose the control.

Use the arrow controls

CD to display and close the subpanels.

Closing a subpanel

• Choose the down arrow at the bottom of the subpanel.

Moving subpanels

• Move the subpanel as you would move any otner window.

3-15

Basic Skills
Using the Front Panel

To move the Front Panel
Mouse

1. Move the pointer over the Front Panel.
2. Hold down

(~ + mouse

button 1.

3. Drag the Front Panel to its new location.
4. Release @!,) and mouse button 1.
Keyboard

1. Press

(~+(Tab)

2. Press

(~+space

until you reach the Front Panel.
bar to display the Front Panel menu.

3. Press @.
4. Use the arrow keys to relocate the Front Panel.
5. Press (Enter ).

To turn the Front Panel into an icon
Mouse

• Choose MinimizelRestore Front Panel from the Workspace menu.

Keyboard

1. Press @D+(Tab) until you reach the Front Panel.

2. Press @!,)+space bar to display the menu.
3. Press (0.
Restoring the Front
Panel

• Double-click its icon.
• Or, choose MinimizelRestore Front Panel from the Workspace menu.
• Or, choose Restore from its icon menu.

3-16

Using Controls in Application Windows

To help you manipulate the application's data, windows contain standard sets
of controls. You'll come across some of the following standard controls:
• Buttons execute commands, start actions, or specify options and settings.
Types of buttons include push buttons, toggle buttons, and radio buttons.
• Text fields provide an area where you can type information.
• Lists display a list of choices from which you can select.
• Sliders provide incremental selection from a range of values.

To choose a push button
Choosing a push button immediately performs the associated command or
action. For example, choosing an OK button applies any changes made to a
dialog, then closes it.
Mouse

• Move the pointer over the button and click mouse button 1.

Keyboard

1. Use (Tab) and the arrow keys until you reach the button.

2. Press

(Enter ).

To select a toggle or a radio button
Generally, selecting a toggle button merely specifies the option or setting to
be used when a command, such as OK, is performed. You can select more
than one toggle button in a group.

3-17

Basic Skills
Using Controls in Application Windows

Selecting a radio button also specifies an option or setting, but only one radio
button in a group can be selected at a time.
Mouse

• Move the pointer over the button and click mouse button 1.
To unselect the button, move the pointer over a selected button and click
mouse button 1.

Keyboard

1. Use (Tab) and the arrow keys until you reach the button.
2. Press the space bar.

CD Selected radio button.

o Unselected radio button.
@ Selected toggle button.
@) Unselected toggle button.

3-18

Basic Skills
Using Controls in Application Windows

To scroll the contents of a window
Mouse

• Use the scroll bar.

CD Click to go up one line.
Q) Click to go up one page.

® Drag the slider to scroll incrementally.
® Click to go down one page.
(§) Click to go down one line.
Keyboard

1. Move to the window area you want to scroll.
2. Use the arrow keys, (Prev) and

(Next ),

or ~ and (Pg

Down ).

3-19

Basic Skills
Using Controls in Application Windows

To choose a list item
A selected list item highlights and is acted upon when a command, such as
OK, is chosen.
Mouse

1. Click the list item.
2. Choose a command, such as OK.
In some lists, double-clicking an item selects the item and chooses the default

command.
Keyboard

1. Tab to the list.
2. Select the list item:
• In a single-selection list, use the arrow keys to reach your choice.
• In a multiple-selection list, use the arrow keys to reach your choice,
then press the space bar. To unselect the item, press the space bar
again.

3-20

Basic Skills
Using Controls in Application Windows

3. Choose a command, such as OK.

CD Single-selection list.
(£) Multiple-selection list.

3-21

Basic Skills
Using Controls in Application Windows

To enter text into an empty field
Mouse

• Click the field to get the text insertion cursor.
• Start typing.

Keyboard

1. Press (Tab ), (Shift)+(Tab ), or the arrow keys until you reach the field.
2. Start typing.

Atext field

CD accepts information you type.

To edit text in a field
Mouse

1. Select the text in the field to edit:
• Character(s): Move the pointer to the first character and drag the
pointer to the last character.
• Word: Double-click the word.
• Line: Triple-click the line.
• Multi-line field: Quadruple-click the field.
2. Type the replacement text.

3-22

Basic Skills
Using Controls in Application Windows

Keyboard

1. Press (Tab ), (Shift )+(Tab ), or the arrow keys until you reach the field.

2. Use the editing keys to edit its contents.
Editing keys

Arrow

Move the text insertion cursor.

( Backspace)

Delete the character before the cursor.

(Delete char)

or @)

(CTRL )+(Delete char)
(CTRL)+@)

Delete the character following the cursor.
or

Delete all the characters from the cursor to the
end of the current line.

To cut and paste text into windows
Cutting and pasting eliminates the need to retype text. You can cut from and
paste into:
• Text fields.
• Terminal emulator windows.
• Editor windows.
Cutting text

1. Move the pointer to the start of the text block.
2. Hold down mouse button 1 and drag the pointer to the end of the text
block.

Pasting text

1. Put the text insertion cursor at the target location.
2. Click mouse button 2 to paste the text into the field.
To unselect text, click mouse button 1 in an empty area of the window that
has the text selected, or press (ESC ).

3-23

Basic Skills
Using Controls in Application Windows

To use sliders
Mouse

• Drag the slider by moving the mouse while holding down mouse button 1.

Keyboard

1. Press (Tab) or an arrow key until you reach the slider.

2. Use the arrow keys to move the slider incrementally. Using (CTRL) plus an
arrow key moves the slider faster.

3-24

Using Menus

A menu is a list of frequently-used commands that help you manage windows
and operate software applications.
Choosing a menu command performs an associated action. For example,
choosing Minimize from a window menu turns the window into an icon.
Some of the most common menus are:
• Window menus.
• The Workspace menu.
• Software application menus:
[] Menus that "pull down" from the application's menu bar.
[] Menus that "pop up" on an application or on a desktop object.

3-25

Basic Skills
Using Menus

CD An application's menu pulled down from a menu bar.

o A window menu.

CD The Workspace menu.
@) A desktop object menu popped-up from the object.

Menu commands that have mottled labels are inactive. These commands are
only available under certain conditions. For example, the Restore command is
available in a window menu only when the window is an icon.
An underlined character in a command is called a mnemonic. A key
sequence listed to the right of some commands is called an accelerator. Both
mnemonics and accelerators provide you with quick keyboard access to menu
commands.

3-26

Basic Skills
Using Menus

To choose a command from a window menu
Mouse

1. Click mouse button 1 on the window menu button to display the menu.
Or, if the window is an icon, click the icon.
2. Click a menu command.
Or, you can use the dragging method:

1. Hold down mouse button 1 as you drag the pointer through the menu.
2. When you reach the command, release the mouse button.
To close the menu without choosing a command, click anywhere off the
menu.
Keyboard

1. Press @+(Tab 1until you reach the window or window icon.

2. Press @+space bar to display the window menu.
3. Press the command's mnemonic, the underlined character.
To close the menu without choosing a command, press
The window menu

(ESC 1.

The window menu provides easy access to services that control the behavior
of the window.

3-27

Basic Skills
Using Menus

CD Window menu button.
Q) Window menu.
Q) Window icon menu.

Restore

Turns an icon back into a window. This item is
active only when the window is an icon.

Size

Interactively changes the size of the window.
This item is inactive in the icon's menu.

Minimize

Turns the window into an icon.

Maximize

Enlarges the window to its greatest allowable
size.

Lower

Puts the window on the bottom of the stack of
overlapping windows in a workspace.

Occupy Workspace

Displays a dialog to select the workspaces in
which the window should appear.

Occupy All Workspaces

Displays the window in all workspaces.

3-28

Basic Skills
Using Menus

Unoccupy Workspace

Removes the window from the current
workspace. This item is inactive if the window is
displayed in only one workspace.

Closes the window, removing it from the
workspace

To choose a command from the Workspace menu
1. Move the pointer over the workspace backdrop.
2. Hold down mouse button 3 as you drag the pointer through the menu.
3. When you reach your choice, release the mouse button.
The Workspace menu can only be accessed with the mouse.

The Workspace menu contains commands that help manage the workspace.
Shuffle Up

Puts the bottom window (in a stack of
overlapping windows) on the top of the stack.

Shuffle Down

Puts the top window (in a stack of overlapping
windows) on the bottom of the stack.

Refresh

"Repaints" the screen should the display become
unreadable.

3-29

Basic Skills
Using Menus

MinimizelRestore Front
Panel

Turns the Front Panel into an icon. When
selected a second time, restores the Front Panel.

Restart Workspace Manager Stops then restarts the Workspace Manager
after you have customized configuration files.
Log out

Begins the logout process, the same as pressing
the exit button in the Front Panel.

To choose a menu command with the mouse
Clicking method

1. Display the menu:

• For a menu bar menu, click the menu name using mouse button 1.
• For a popup menu, click inside the application using mouse button 3.
• For an object's popup menu, click the object with mouse button 3.
2. Click the command.
To close the menu without choosing a command, move the pointer off the
menu, and click the mouse button a second time.
Dragging method

1. Hold down the mouse button as you drag the pointer through the menu:

• For a menu bar menu, use mouse button 1.
• For a popup menu, use mouse button 3.
2. Release the mouse button when you reach the command.
To close the menu without choosing a command, move the pointer off the
menu and release the mouse button.

3-30

Basic Skills
Using Menus

To choose a menu command with the keyboard
Menu bar

1. Press @D+(Tab) until you reach the application window.

2. Press @+mnemonic, the underlined character, to display the menu.
3. Press the command's mnemonic.
Or, use the arrow keys to move to the command, and press
Popup menus

(Enter

1. Press @+(Tab) until you reach the application window or desktop object.

2. Press @ to display the popup menu.
3. Press the mnemonic.
Or, use the arrow keys to move to the command, and press (Enter 1.
To close the menu without choosing a command, press

(ESC 1.

3-31

Basic Skills
Using Menus

Getting Help

Hundreds of online help topics are at your fingertips while you're using HP
VUE. Here are the ways you can request help:
• Press Fl-also known as the "help key" -to get context-sensitive help.
• Choose a command from an application's Help menu.
• Open Help Manager to browse all the available help.
Press F1
The "Help" Key

The quickest and easiest way to get help when you get stuck is to press F1.
When you press F 1, the application you are using responds by displaying the
help topic most closely related to your current activity.
Some computers have a dedicated "Help" on the keyboard. If yours does, it
may take the place of the F 1 key.

Use the Help Menu

Most applications have a Help menu that contains additionl commands for
requesting specific kinds of help-such as "Introduction," "Tasks," and
"Reference. "
To learn more about using help windows, choose Using Help from the Help
menu in any HP VUE application. Or, you can press Fl while using a help
window.

Browsing Help with
Help Manager

The HP VUE Help Manager is a special help window that lists all of the online
help installed on your system.
To browse the HP VUE help volumes:
1. Choose the Help control in the Front Panel.
2. Choose the "HP Visual User Environment" title to display the list of help
volumes available with HP VUE.
3. Browse the list of titles. To open a volume, choose its title.

4-2

Getting Help Within an Application

The HP Help System is built into each of the HP VUE applications (and
possibly other applications installed on your system). When you ask for help
while using an application, the application displays a help window.
The HP Help System provides two types of help dialogs that applications may
use:
• General help dialogs have a menu bar, a Topic Hierarchy (that tells you
where you are), and a help topic display area. (See CD below.)
• Quick help dialogs have just a topic display area and one or more dialog
buttons at the bottom. (See (1) below.)

If you are new to HP VUE, here are the
essential skills you need to get started:

To get help within any window:
Press F1. (Try it now to get help
on using help windows.)

To select and raise a window: Click the
window's frame. Or, press Alt+Tab to select
the next window in the stack.
until

• Backtrack returns to the previous
topic. The Backtrack command (Ctrl+B)
is in the Navigate menu and in the popup menu in the help display area. (See
also "Backtracking")

4-3

Getting Help

Getting Help Within an Application

To display context-sensitive help
• Press FI-the "help key."
• Or, if you are using a dialog box, choose the dialog's Help button.

When you ask for context-sensitive help within an application, the application
determines which help topic is most appropriate for your current situation, or
context.

To display other application help
• Choose one of the following commands from the applcation's Help menu:
Introduction

Displays the home topic for the application. The home
topic is the main topic at the top of the application's help
topic hierarchy. Hyperlinks in the home topic lead to all
other help topics.

Tasks

Displays task instructions for most operations performed
with the application.

Reference

Displays reference summaries for various features, such as
windows and dialogs, menus, and resources.

On Item

Lets you pick an item in any of the application's windows,
then presents a description of the item you've selected.

Using Help

Provides help on using the help windows.

Version

Displays the version and copyright information for the
application.

Non-HP VUE applications may have different commands in their Help menus.

4-4

Using Hyperlinks

One of the most important skills you need for using help windows is using
hyperlinks. Any text in a help window that is displayed with an underline is
a hyperlink. Choosing a link (with the mouse or the keyboard) immediately
jumps to another related topic.
A solid underline CD indicates a standard jump. A dashed underline Q)
indicates a definition link, which displays a popup definition window
(actually a quick help dialog).

A 9.?.?D~9_Yn.q~rliD~ also indicates a hyperlink.
The only difference is that the related topic is
displayed in a smaller quick help dialog.

See Also
• Backtracking
• More About Hyperlinks

Some Links Display a

New Window

Most hyperlinks display the related topic in the same window. However, if
you choose a hyperlink that jumps to a help topic for another application, a
new window is displayed. Links that jump from one application's online help
into another's, are called cross-volume or cross-application hyperlinks.

4-5

Getting Help
Using Hyperlinks

Knowing Where You Are
Since hyperlinks can quickly take you from one piece of information to
another, it is sometimes helpful to know where you are. The Topic Hierarchy
list provided in general help dialogs provides this information.

The first item in the list is the home topic, or top, of the current help volume.
(Usually there's one help volume per application.) Each item below the home
topic represents a level of hierarchy down to the last item, which is always
the current topic.
As you follow hyperlinks, you'll notice the titles in the Topic Hierarchy list
changing, always to reflect your current location.

Knowing Where You've Been
Each general help dialog keeps track of the 20 most recent topics that you
have visited. To display this list, choose History from the Search menu. The
History dialog lists the title of each topic (most recent topic on top).

4-6

Getting Help
Using Hyperlinks

To return to a particular topic, choos its title in the list. When you're done,
choose Close.

To find a topic by exploring
• Choose hyperlinks to jump to related topics.
• Use the Topic Hierarchy list to jump "up" to a higher-level topic.
• Return to the home topic by choosing Horne Topic from the Navigate menu.
• Go back to the previous topic by choosing Backtrack from the Navigate
menu or from the popup menu in the topic display area.
• Use the Keyword Index to locate topics that cover a certain subject.
(Choose Keyword from the Search menu.)

4-7

Getting Help

Using Hyperlinks

To find a topic by keyword
1. Choose Keywords from the Search menu to display the Keyword dialog.
2. Optional: Type all or part of the keyword you are looking for into the

Keyword Filter field. As you type, the keyword list is shortened to show
only the keywords that begin with the characters you type in (case is
ignored).
3. In the keyword list, select the keyword you are looking for.
4. In the Keyword Result List, select a title of the topic you want to view.
The topic you select is displayed in the help dialog.

You may view as many topics as you want. When you are done, chose Close.
The scope of the keyword index is limited to the current help volume. That
is, you cannot review a global index of keywords for all online help.

4-8

Getting Help
Using Hyperlinks

To change the topic display colors
• Set the following resources:
*XmDialogShell.XvhHelpDialogWidget*DisplayArea.background:
cowr
*XmDialogShell*XmDialogShell.XvhHelpDialogWidget*DisplayArea.background: cowr
*XmDialogShell.XvhHelpDialogWidget*DisplayArea.foreground:
cowr
*XmDialogShell*XmDialogShell.XvhHelpDialogWidget*DisplayArea.foreground: color

Any application started after setting these resources will use the new values
for the topic display areas within its help windows.
Default Values

The default values for these resources are:
*XmDialogShell.XvhHelpDialogWidget*DisplayArea.background: white
*XmDialogShell*XmDialogShell.XvhHelpDialogWidget*DisplayArea.background:
*XmDialogShell.XvhHelpDialogWidget*DisplayArea.foreground: black
*XmDialogShell*XmDialogShell.XvhHelpDialogWidget*DisplayArea.foreground:

See Also

white
black

If you're unsure how to set resources, refer to the following topics for more

information:
• "To set resources using the EditResources action" in Chapter 25
• "To create a backup resource file" in Chapter 25
• "To set sys.resources for first session" in Chapter 25
• "To set sys.res.lite for VUE Lite" in Chapter 25

4-9

Browsing Help on Your System

The HP VUE Help Manager lets you browse lists of the online help installed
on your system. At the top level, Help Manager lists all of the product
families that have installed help. If you open a product family, you see a list
of help volumes installed for that product. To open a particular help volume,
you choose its title.
Accessing the Previous
Version of Help
Manager

Also listed at the top level (at the end of the list) is a special hyperlink for
starting the older version of the HP VUE Help Manager (for HP VUE 2.01 or
earlier). Access to the previous version of Help Manager is provided so you
can access help for applications that have not yet updated their online help
for the current 3.0 version of Help Manager.

4-10

Getting Help
Browsing Help on Your System

To open a help volume using Help Manager
l. Choose the Help control in the Front Panel (the books with a question

mark). A general help dialog is displayed, listing all of the product families
with online help. This is the top level of Help Manager.

Welcome to Help Manager
Each of the titles listed below represents aprodlJctfamlly
that has installed and registered its online help, Each title
(and icon) is a hyperlink that lists the help within the family,
• To display a list of the help available for a product
family, choose its title (underlined text) or icon,
• Within a product family, find the help you want to view,
then choose its title,
• If you need help while using help windows, press F1,

I£P Visual User Environment. Version 8.0 "
Welcome to HP VUE 3,0 + General HP
VUE Configuration + Front Panel and
Workspace Manager + Login Manager +
Session Manager + File Manager and the
Desktop + Toolboxes + File Annotator + Style Manager
+ Text Editor + Icon Editor

For example, in the figure above, the "HP Visual User Environment,
Version 3.0" product family is listed. You can scroll to see additional
families. (The order of families in your Help Manager may be different.)

4-11

Getting Help
Browsing Help on Your System

2. Scroll the window to find the product you are interested in. Then choose
its title (underlined). This lists the help volumes available for that product.
For example, suppose you want to browse File Manager's online help.
After choosing the "HP Visual User Environment, Version 3.0" product
family, scroll down until you see "File Manager and the Desktop, (HP VUE
3.0)"

File Manager and the Desktop (lIP VUE 3.0) ,
Basic File Management Skills + Using the Desktop + Using the
Trash + Accessing Remote Systems + Locating Files + File
Manager Reference

Toolboxes (lIP VUE 3.0)
Using Your Personal Toolbox + Using the General Toolbox +
Using the Nework Toolbox + Managing Applications and
Utilities + Toolbox Reference

Making Text Annotations + Making Audio Annotations + File
Annotator Reference

Style Manager (lIP VUE 3.0)
Changing Colors + Creating Custom Palettes + Changing
Workspace Backdrops + Choosing a Font Size + Customizing

4-12

Getting Help
Browsing Help on Your System

3. To open a particular help volume, choose its title (underlined text). A new
window is displayed showing the home topic of the volume you chose.
For example, if you choose the "File Manager and the Desktop, (HP VUE
3.0)" title, Help Manager displays File Manager's help in a new window

F6DW

HEWLETT

.:~ PACKARD

File Manager and
The Desktop
Welcome to HP VUE Ale Manager. With File Manager
you manage your work by manipulating icons that represent
files, directories, actions, and other objects.
File Manager uses the backdrop in each workspace as the
Desktop. You can place any File Manager icon directly on
the Desktop for quick access.
•
•
•
•

File Manager Tasks
Using the Desktop
File Manager Concepts
File Manager Reference

The HP VUE Toolboxes are displayed using special File
Manager windows. See Toolboxes for more information.

This is the same help topic you would see if you chose Introduction from
the Help menu in a File Manager window.

4-13

Displaying a Man Page

Manual reference pages, traditionally known as "man pages," can be
displayed using the Man Page control in the Help subpanel.

To display a man page
1. Choose Man Page from the Help subpanel. A dialog is displayed,
prompting you to enter a man page.
2. Enter the name of the man page you want to see.
3. Choose Show Man Page.
You may repeat steps 2 and 3 as many times as you want to view additional
man pages. When you are done, choose Exit.

4-14

Getting Help

Displaying a Man Page

Example

To display the man page for the vuewm command, first choose Man Page from
the Help subpanel. A dialog is displayed, prompting you for the man page
name. Enter the string "vueliiml" into the name field ...

. . . then choose Show Man Page. The man page is displayed in a Quick help
dialog.

VUEHM(lX)

VUEHH(lX)

vuewm. - The HP VUE Workspace Manager.

vuewm

[options]

Vuewm is an x11 window manager based upon the Motif Windo .... Manager
(mvm, veES ion 1.1.3). Vuewm. is an integral part of the He.... lett-Packard
Visual User Environment (HP VUE). It communicates with and facilitates
access to the other components in the environment.

Access to many other VUE components is provided throughout the front

panel (also called the workspa.ce manager in HP VUE 2.1). The front
panel can be configured to contain controls and indicators for tasks
that you perform frequently. These controls include file management.
session management, customization, printing, trash, help, or other
functions that you define.

When you're done, dismiss the man page by choosing OK. To display another
man page, enter its name just as you did for vuewm. When you are done
viewing man pages, choose Exit.

4-15

Printing Help Topics

Sometimes it is useful to have a printed version of a help topic-or even a
whole help volume-for a particular application. The HP Help System lets
you print help topics to LaserJet Series II or Series III printers. (The default is
Series III.)
When you print a topic, it is formatted just as it is on the display. Color
graphics are automatically dithered to black and white.

To print help topics
1. Choose Print from the File menu to display the Print dialog.
2. Select the topics you want to print:
• Print All-to print all topics.
• Print Current Topic-to print only the current topic (the default).
• Print Current and Down-to print the current topic and its subtopics.
3. Choose OK.
In quick help dialogs, the Print button immediately prints the current topic,

without displaying the Print dialog.
By default, printed output from HP Help is directed to your default printer.
You can specify another printer by setting the printer. name resource. If you
are not printing to a LaserJet Series III (or later) printer, you must also set the
printer .name.model resource.

4-16

Getting Help

Printing Help Topics

To choose a printer for yourself
l. Copy the /usr/lib/X11/app-defaults/Helpprint file into your home

directory and make it writable.
2. Edit your / HomeDirectory/Helpprint file, setting the name and model
resources for the printer you want to use:
*printer . name : name
*printer . name. model :

model

Where name is the device name of the printer and model is either LJ11 or
LJ11I. (The default model is LJ11I.)
Your system administrator may have already edited the Helpprint file to
configure the correct models for the printers on your system. If so, you
specify just the printer. name to select a printer.
Examples

Suppose you have a LaserJet II printer named hp-laser. To direct all printed
help topics to that printer, enter these resources into your Helpprint file:
*printer.name:
*printer.hp-Iaser.model:

hp-Iaser
LJ11

Or, suppose you want to direct all printed help topics to a LaserJet III printer
named l j 3d. Since the default model is LJ111, you need to specify only this
single resource:
*printer.name:

Ij3d

If you want to print help two-sided (duplex), include this resource, too:
*lpCommand:

Ip -oraw -od

The -od option requests duplex printing if your printer supports it.

4-17

Getting Help

Printing Help Topics

To choose a printer for all users
1. Login as superuser.
2. Edit the /usr/lib/X11/app-defaults/Helpprint file, adding the
necessary model resource for each printer as follows:
*printer. name. model : model

Where name is the device name of the printer and model is either LJll or
LJlll. The default model is LJlll.
3. To specify the default printer, use the printer name resource:
*printer . name :

name

Where name is the device name of the printer you are configuring.

4-18

Accessing a Help Server

A help server is a computer system on a network that other systems can rely
on for accessing online help files. You can configure your local system (the
"client") to access a remote system (the "server") by mounting the remote
system's disks on your system, modifying the help search path, and updating
your Help Manager.

To configure access to a help server
1. On the remote system (the "server"), log in as superuser, then do these

tasks:
Usually, online help files are
installed when you install application software. It is common for an
application server to also be a help server, since the files are usually
kept together.
o Export the disk volume where the online help resides. Usually, this is
the /usr/ volume-if not, also export /usr/, since the /usr/vhelp/
directory should also be available for mounting.
o Install the online help you want to access.

2. On the local system (the "client"), log in as superuser, then do these tasks:
o Mount the disk volume(s) exportedjrom the remote system
[J

(in step 1).

Edit the /usr/vue/config/Xsessionscript. Set the

XVHHELPSYSTEMSEARCHPATH environment variable to search the
newly mounted directories for online help.
o Log out and back into HP VUE. This ensures the Xsess ion script is
executed, setting the search path variable.
o Update your local Help Manager. Open a Terminal Emulator window.
Verify that the XVHHELPSYSTEMSEARCHPATH is set properly (use the
env command). Then, execute this command to update the browser
volume used by Help Manager to list available help:
/usr/vue/bin/helpgen

4-19

Getting Help
Accessing a Help Server

Example

This example shows how the XVHHELPSYSTEMSEARCHPATH environment
variable is used within HP VUE to access help installed on another computer
on the network. (These tasks require superuser permission to mount a new
file system and edit the /usr/vue/config/Xsession script.)
To make the remote files accessible, "mount" the remote system's /usr/
disk volume on your local system in the directory /nfs/hostname/usr/.
(Refer to the operating system documentation or online help to learn how to
"mount" a network file system.)
Once the remote files are physically available, you must tell the HP Help
System where to look for them. You do this in HP VUE by editing the
/usr/vue/config/Xsession script. Search for the section of the file that
defines XVHHELPSYSTEMSEARCHPATH, then uncomment and edit the lines
so that they look like this:
XVHHELPSYSTEMSEARCHPATH=\
/usr/vhelp/%T/%L/%H:\
/usr/vhelp/%T/%H:\
/usr/vhelp/%T/%L/%H.hv:\
/usr/vhelp/%T/%H.hv:\
/usr/vhelp/%T/C/%H:\
/usr/vhelp/%T/C/%H.hv:\
/nfs/hostname/usr/vhelp/%T/%L/%H:\
/nfs/hostname/usr/vhelp/%T/%H:\
/nfs/hostname/usr/vhelp/%T/%L/%H.hv:\
/nfs/hostname/usr/vhelp/%T/%H.hv:\
/nfs/hostname/usr/vhelp/%T/C/%H:\
/nfs/hostname/usr/vhelp/%T/C/%H.hv

Where hostname is the name of the directory you created for the remote
system.
When you're done editing, save the file, then log out and back in. To update
Help Manager on the local system, run this command:
/usr/vue/bin/helpgen

Any help installed on the remote system (hostname) should now be available
in Help Manager. (If you already have a Help Manager window open, close it
and open a new one to see the changes.)

4-20

Managing Files and Using the Desktop

HP VUE provides the following to help organize and maintain the files and
directories you use:
• File Manager is an application for managing files and directories.
• The Desktop allows you to place any file or directory icon directly on the
workspace backdrop for easy access.
• Toolboxes are special File Manager views for managing applications and
other software available to you.
Introducing
File Manager

The HP VUE File Manager displays files and directories as icons. Using a
mouse, you can manipulate the icons directly by dragging and dropping them
into place. For example, to print a file, simply drop it on the printer in the
Front Panel.
File Manager associates a meaningful icon with each file and directory based
on its filetype. More importantly, actions associated with each filetype define
the desired behavior for the file or directory.
For instance, you might have a filetype that identifies document files. The
default action-performed by double-clicking the file's icon-would open the
file for editing. That is, the action saves you the trouble of remembering and
typing the command to start your word processor. The action automatically
starts your word processor and loads the file. Additional actions may provide
shortcuts to other frequent tasks, such as printing the document.

5-2

Managing Files and Using the Desktop

The Desktop for
fingertip access

Any file, directory, or action that you access frequently can be placed directly
on the Desktop for quick access. The Desktop occupies the entire backdrop in
each workspace. In fact, since HP VUE has six workspace (by default), you
effectively have six separate Desktops.
When you put an object on the Desktop, the original object is not altered.
Each Desktop object is really just a reference to the actual object that remains
in its original location .
You can leave objects on the Desktop as long as you want. Their locations are
remembered when you log out and restored when you log in again.

Popup Menus

To display a popup menu, you point to the object's icon, then press and hold
mouse button 3 (the right button on a two-button mouse). The popup menu
contains a few standard commands for each object, but it also includes all of
the available actions for the object.
When you no longer need an object on the Desktop, choose Remove From
Desktop from the object's popup menu.

See Also

• Chapter 6 explains how to use the toolboxes.
• Chapter 19 is an introduction to creating filetypes and actions.
• The BeginnerJs Guide to HP-UX manual also includes basic file
management skills.

5-3

Introducing the Desktop

The HP VUE Desktop occupies each workspace. Its a handy place to put the
files, directories, actions, and applications that you use most freQuently.
To place an object on the Desktop, you drag its icon from a File Manager or
Toolbox window then drop it on the workspace backdrop. A Desktop icon
appears right where you drop the object.
You use Desktop icons exactly like the icons in the File Manager or Toolbox.
To execute an object's default action, double-click its icon on the Desktop.
Each Desktop object also has a popup menu containing additional commands
and actions for the object. To display the popup menu for a Desktop object
using the mouse, point to the icon, then press and hold the right mouse
button. To display the menu with the keyboard, use @!)+(Tab) until the icon
is highlighted, then press (E).

5-4

The Hierarchical File System

If you are new to computers, the idea of a "hierarchical file system" may be
new to you. Here are the basic concepts ...
What's a file?

A file is a named container for information. Most of the files you use contain
data of some particular format-a document, a spreadsheet, a chart.
Most applications understand a limited number of file formats. For example,
a document editor may not be able to read a spreadsheet file. HP VUE
helps you recognize different types of files using a filetype database. A
filetype identifies the files of a particular format and associates them with
the appropriate applications. These associations mean you don't have to
remember commands to accomplish frequent tasks.
On some computers, file names cannot be longer than 14 characters. If you
are not sure if your computer can support longer file names, check with your
system administrator.

What's a directory?

A directory is a container for files, similar to a folder in a file cabinet. Since a
directory can contain other directories-sometimes called subdirectories-you
can create multiple layers of organization that forms a hierarchy.
Within any single directory, each file name must be unique. However, files in
different directories may have the same name.
As you navigate from directory to directory, your current location is referred
to as the current working directory.

What's a path?

The location of a file is often specified using the directories and subdirectories
that lead to the file-this is called a path. A path is an absolute path if
it begins at the root directory. The root directory is the single common
directory where the hierarchy begins. If a path begins with a slash (I), it is
an absolute path specified from the root directory. For example, this is an
absolute path to the file sys. vueliJIIlrc :
lusr/vue/config/sys.vuewmrc

A path is relative if it describes the location of a file or directory as it relates
to the current working directory. If a path does not begin with a slash, it is a

5-5

Managing Files and Using the Desktop
The Hierarchical File System

relative path. For example, if the current working directory is /usr /vue/,
the relative path to the sys . vuewmrc file is:
config/sys.vuewmrc

If your current working directory is different, then the relative path to the

same file is different.
Two special directory names are useful specifying relative paths. The . /
directory (sometimes called "dot") represents the current working directory.
The .. / directory (sometimes called "dot-dot") represents the parent
directory-the directory one level up in the directory hierarchy. For example,
if you current working directory is /usr/vue/ config/panels/, then the
relative path to the sys. vuewmrc file is:
.. /sys.vuewmrc

That's because the file is in the /usr/vue/ config/ directory, one level
above the current directory.
See Also

•
•
•
•

"To change to another directory"
"To specify a remote directory or file"
"To find a file by name"
"To find a file by contents"

If you still want to learn more about your computer's file system, refer to
the online help or documentation for your operating system. There are also
many commercial books available that cover the basics of file systems and file
management.

5-6

File Ownership and Security

Three groups of users can access files: owner, group, and other. File access is
divided into three functions: read permission, write permission, and execute
permission.
Who Has Access?

The three basic classes of users are:
• Owner-Usually the person who created the file.
• Group-Several users that have been grouped together by the system
administrator. For example, the members of a department might belong to
the same group.
• Other-All other users on the system.

What Kind of Access?

The access permissions on a files specify how that file can be accessed by the
owner, group, and other.
• Read Permission-Allows access to retrieve or view the contents of the file
or directory.
• Write Permission-Allows access to change the contents of the file or
directory.
• Execute Permission-For a file, allows access to run the file (for executable
files, scripts, and actions). For a directory, allows access to run commands,
scripts, and actions within that directory.
With File Manager, you can view and change the access permissions for any
file or directory. See "To change the owner of a file or directory" and "To
change the access permissions on a file or directory" .

5-7

Managing Files and Using the Desktop
File Ownership and Security

Examples

To make a directory private:
• Change the directory's properties, giving yourself (the "owner") read,
write, and execute permission, but give no permissions for "group" and
"other." This means that only you and the superuser can view the contents
of the directory.
To make an action that you've created available for everyone to use, but
protected so it isn't inadvertently overwritten:

• Change the file's properties, giving read and execute permission to
"owner," "group," and "other." Don't give anyone write permission.
Default Permissions

The default permissions used when you create a new file or directory may
be altered by your system administrator. To determine what your current
defaults are, create a new file or directory, then open the Properties dialog for
that file or directory.
Check with your system administrator regarding how to change your default
permissions.

5-8

Basic File Management Skills

To get started using File Manager, you need to learn a few basic skills:
• Selecting-Many commands operate on the "selected" file or directory.
• Dragging and Dropping-If you use a mouse, the easiest way to perfonn

many operations is to manipulate the icons with the mouse.
• Using RJpup Menus-Each icon displayed by File Manager has its own

popup menu, including objects on the Desktop. Each popup menu provides
shortcuts to many common operations.

To select a single file or directory
Mouse

• Click the object's icon.

Keyboard

1. Use the (Tab) and direction keys to move the highlight to the object you

want to select.
2. Press Enter or Spacebar.

5-9

Managing Files and Using the Desktop

Basic File Management Skills

When an object is selected, its name and icon are highlighted.

When you select an object, its name is highlighted. Many commands in File
Manager's menus apply to the selected object. In particular, the Actions
menu always contains the actions that can be performed on the selected file
or directory. If no icons are selected, the entire Actions menu (and some
commands in other menus) is inactive.
To select multiple objects, hold down (Ctrl) while selecting.
To deselect an object, select another one or click an empty area within the
File Manager window.

To select multiple files and directories
Mouse

• Drag a box around the objects you want to select. (Press mouse button 1
in a blank area of the view, drag to draw a box, then release to select the
icons included in the box.)
• Or, click to select the first object, then @)+click to select additional

objects.

5-10

Managing Files and Using the Desktop
Basic File Management Skills

Keyboard

1. Select the first object.
2. For each additional object you want to select, move the highlight to its
icon, then press @)+(Enter).
When multiple icons are selected, dragging anyone of the selected icons
drags the whole group.
Also, when multiple icons are selected, the Actions menu and some
commands in other menus are inactive.

Reasons for Selecting
Multiple Objects

• Deleting several files at once.
• Moving a group of files to a new directory.
• Putting several objects on the Desktop.

To rename a file or directory
Mouse

• Select the object's name, type the new name, then press Enter.

Keyboard or Mouse

• Choose Rename from the File menu, type the new name, then press Enter.
To cancel a rename operation, press (Esc).

To get help on a file or directory
Mouse

• Select the object, then press Fl.
• Or, choose On Item from the Help menu, then click the object's icon.

5-11

Managing Files and Using the Desktop
Basic File Management Skills

Keyboard

• Move the keyboard highlight to the object's icon, then press (IT).
The description displayed when you ask for help on an icon describes the
filetype associated with the file or directory. The description is specified in
the file type definition.

See Also

• Chapter 4 explains how to use HP Help.
• Chapter 19 is an introduction to creating filetypes and actions.

To open a file or directory
• Double-click the object's icon.
• Or, select the object's icon, then choose a conunand fforn the Actions rrtenu

that opens the file or directory. (The Actions menu contains different
commands depending on the filetype of the selected object.)
• Or, choose a command from the object's popup menu.

Double-clicking an icon executes the object's default action, which is always
the first command in the Actions menu. For most data files, the default action
opens the file by starting the appropriate application and loading the file.
Directories have actions defined to open them (either in place, using the
current File Manager window, or in a new window).

To drop a file or directory
1. Point to the object's icon.

2. Press and hold mouse button 2, known as the "drag" button. (On a
two-button mouse, press both buttons simultaneously.)
3. Drag the icon to the location where you want to drop it, then release the
mouse button.
5-12

Managing Files and Using the Desktop
Basic File Management Skills

So, the motion for dropping an object is press . .. drag ... release.
I
I

~..........

~~~-

t&~-./2.·.·
• ·• ·• ·• · • • ____}
'~~

To cancel a drag in progress, press (Esc) before releasing the mouse button.
If more than one icon is selected, you drag the entire group by dragging any

of the selected icons.

What Dropping a File
Means

• If you drop an object into an open File Manager window or into a directory

icon, the file is moved to that directory.
• If you drop an object onto the workspace backdrop, it's placed on the

Desktop in the current workspace. (Actually, a Desktop object is really just
a reference to the real object, which remains in the File Manager view,
unchanged. )
• If you drop a file on the Printer control in the Front Panel (or one of the

printers in the Printers subpanel), the file is printed.
• If you drop a file on the Personal Toolbox control in the Front Panel, the

object is copied into your Personal Toolbox.
• If you drop a file on the Trash control in the Front Panel, the object is

moved into the Trash Can.
• If you drop a file on an action icon, the action is invoked with the file as a

parameter.

5-13

Managing Files and Using the Desktop
Basic File Management Skills

If you attempt to drop the icon in a location that does not support dropped

objects, the icon snaps back to its original location in File Manager or on the
Desktop.

To display a popup menu
Mouse

1. Point to the icon whose popup menu you want to display.
2. Press mouse button 3-the "popup" button. (On a two-button mouse,
press the right mouse button.)
3. To choose a command from the menu, drag to the command, then release.
Or, click the command.

Keyboard

1. Using the [Tab) and direction keys, move the highlight to the icon whose
menu you want to display.
2. Press (E).
3. To choose a command from the menu, use the direction keys to highlight
the command, then press Enter.
To cancel the menu without choosing a command, press [Esc).

5-14

Manipulating Files and Directories

The major identifying features of a file or directory are:
• Its name and location in the file hierarchy.
• Its owner permissions (properties).
• Whether or not it is linked to another file. A linked file is a representation
of another file. Linked files provide a way for you to have one file that
appears to exist in two or more directories.

To create a new file or directory
1. Choose New ...
• From the File menu to create a new file.
• Or, from the Directory menu to create a new directory.
A dialog box prompts you for the name of the new file or directory.
2. Enter the new name.
3. Choose OK.
Other Ways to
Create Objects

• Copying an existing object, then rename it.
• Create a new file within an application. For example, if you use Text Editor
to write a new text file, when you save it for the first time, a new file is
created.

5-15

Managing Files and Using the Desktop
Manipulating Files and Directories

To move a file or directory
Mouse

1. Be sure the destination directory is visible (either as an icon or as an open
File Manager view).
2. Drop the icon into its new directory.

Keyboard

• Copy the file, then delete the original file.

For HP VUE Lite

Since File Manager is not available in HP VUE Lite, you must use the mv
command (move), to move and rename files. Open a Terminal Window then
execute the mv command like this:
mv oldjile newjile

Or, to move one or more files into an existing directory:
mv jiles directory

5-16

Managing Files and Using the Desktop
Manipulating Files and Directories

To copy a file
Mouse

1. Be sure the destination directory is visible (either as an icon or as an open
File Manager view).
2. Press and hold @) while dragging the file's icon, then drop the icon into
the directory where you want the copy.

Keyboard

l. Select the file's icon.

2. Choose Copy from the File menu. A dialog displays, prompting you for the
name of the new copy.
3. Enter a name for the new copy of the file.
4. Choose OK.

For HP VUE Lite

Since File Manager is not available in HP VUE Lite, you must use the cp
command (copy), to copy files and directories. To copy a file, open a Terminal
Emulator then execute the cp command like this:
cp oldfile newfile
Or, to copy a directory and its entire contents:
cp -r directory new directory
File and directory names may include a path, if needed.

5-17

Managing Files and Using the Desktop

Manipulating Files and Directories

See Also

• "To re-sort files and directories (clean up)"

To create a symbolic link
Mouse

• Press and hold (Shift) while dragging the object's icon. When you drop the
icon into a new directory, a symbolic link is created in that directory that
points to the original object.

Keyboard

1. Choose Terminal from the Directory menu. This opens a Terminal

Emulator window with the same current working directory.
2. Use the In command to create the symbolic link:
In

-8

filename linkname

Where filename is a complete path to the file, if it isn't in the current
directory, and linkname is the name of the symbolic link, which may also
be a complete path.
3. Close the Terminal Emulator window by choosing Close from the window
menu or by executing the exit command.
For HP VUE Lite

Since File Manager is not available in HP VUE Lite, you must use the In
command (link) to create a symbolic link. Open a Terminal Emulator, the
execute the In command as shown above under "Keyboard."

To change the owner of a file or directory
1. Select the object's icon.

2. Choose Properties from the File menu or from the object's pop-up menu.
File Manager displays the File Properties dialog.

5-18

Managing Files and Using the Desktop
Manipulating Files and Directories

3. Make the desired changes:
• To change the file's owner, type the new owner's name into the Owner
Name field.
• To change the file's group, type the new group name into the Group
Name field.
4. Choose OK.

Notes

• If you give . 'oWnership qf Fh~ ,file to . anoth~r user, you may' not be able to change the permissions,
again, H~I~ss "thatfuser; rewrp~~\JVnership M,YOU., ......' .' .........•......... '.' . .
. . . ," . .
...... .
•• If yo~ f~P nbtjh~vep~rrni~s~}l toandt~Eln remQve,accessrothar,sysrem, you .carInot, 'rester~
" tHe: fileun:tilaccess: tothe'sysfem"is"re~stabltsheq~;\< \ <. t£ ; "
%

!;,,,,,~,.,,;/,,

.\~"

'>~','"

},"'r;,

" ,

',<'t{\'·"~;"",,,,h'

To empty the trash
1. Open the Trash Can.

2. Select the object(s) you want to empty from the trash:
• Select individual objects in the list.
• Or; choose Select All from the File menu.
3. Choose Remove from the File menu.
4. Close the Trash Can by choosing Close from the File menu.
If there are no objects in the trash, some menu commands are inactive.
CAUTION

When you remove a file from the trash, it cannot be recovered.

5-25

Accessing Files on Remote Systems

If your system is part of a network, you may need to access files on other

systems. You can use File Manager to browse directories on remote systems
and to open remote files.

To open a directory on a remote system
• Using the Remote Systems command:
1. Choose Remote Systems from the Directory menu. File Manager

displays a new window. Each directory in the new window represents a
remote system you can access.
2. Open the directory representing the system you want-you are now
working on the remote computer's file system. Work your way to the
directory you want to view.
• Or, by typing a new path:

1. Select the path (just below the menu bar) to make it active for editing.
(If you are not using a mouse, choose Fast Change To from the Directory
menu.)
2. Replace the current path with the path to the remote system, using a
colon to separate the host name from the path.
hostname: / path

3. Press Enter.

5-26

Managing Files and Using the Desktop
Accessing Files on Remote Systems

Example

To change to the directory /users/sonja/ on the machine host28, click the
path area or choose Fast Change To from the Directory menu.

Double-click the current path to select it (the selected text is overwritten as
soon as you begin to type). You can also use Backspace to erase the current
path.
Now, type the new path: host28: /users/sonj a. When you press Enter,
the new directory is displayed.
If the machine host28 has not been configured to provide network access,

File Manager displays an error, telling you that the directory is invalid.

To transfer a file to a remote system
• Drag the file's icon to the new location:
1. Open two File Manager views, one showing the file you want to transfer,
the other showing the destination on the remote system.
2. Drag the file's icon to the new location. If you are making a copy, hold
down (Ctrl ) while dragging. If you are making a symbolic link, hold down
(Shift) while dragging.

5-27

Managing Files and Using the Desktop
Accessing Files on Remote Systems

• Use the Copy command:
1. Select the file's icon.
2. Choose Copy from the File menu. File Manager displays the Copy File
dialog, prompting you for the new name.
3. Enter the host, path, and file name, using the following format:

hostname: / path/filename
For example: hostS: /users/aaron/myfile
4. Choose OK.

To add access to a remote system
1. On the renlOte system, e:hport the disk volumes that you want available by
editing the / etc/ exports file.
2. On the local system, mount the remote disk volumes by editing the
/ etc/ checklist file, creating directories as mount points, then executing
the mount command.

Notes

• This task requires youto . ·have·slJpeniser permission.onthelocal.andremote.systems .
•. File. Manaqer recognizes onlysystemsmo\Jnted .aslnf.s /,host(Jame. File systems .mounted. in
other locations are not. recognized as Uremotesystems,"however,you can navigate to them just .as
voUcan . any other directory;
• If. you are not familiar with the procedures to "ex port andJlmount" .network file systems, refer
to the isystem administration dncurnentation •. or .online .help for your· computer.· .Yournay. also. find
usefulinformatioD in commercial·· books ·on the Network .File System tN FSL
II

5-28

Managing Files and Using the Desktop
Accessing Files on Remote Systems

To specify a remote directory or file
• Use the syntax:
hostname: / path/filename

This syntax for specifying remote files and directories is used in action and
filetype definitions and in any File Manager dialog where a file name is
required.
Example

To access the file /tmp/data1 on remote host scribe, use this name:
scribe:/tmp/datal

See Also

• Refer to the networking documentation for your operating system for more
information about domain naming.

5-29

Using the Desktop

The Desktop lets you put any file or directory icon directly on the backdrop of
the current workspace for quick access. Any icon you drop on the Desktop
stays where you put it.

The Desktop is not availabl.e in HP VUE Lite.

A Desktop in
Each Workspace

Since each workspace has its own Desktop, you can set up your working
environment by putting the files and directories in the workspaces where
you use them most. Objects can be placed on the Desktop in more than one
workspace, if needed.
Placing an object on the Desktop does not alter the original file or directory.
In fact, the icon that appears on the Desktop is really just a shortcut for

accessing the real file or directory. Any operation you perform on the
Desktop object, is actually performed on the file or directory it represents.
Popup Menus

Each Desktop object has its own popup menu, displayed with the right mouse
button or by pressing ® when the icon has the highlight. This menu
contains commands for manipulating the object, including all of the actions
that appear in the File Manager's Actions menu when the object is selected.
The Destkop popup menu is similar to the popup menu available within File
Manager windows, but contains a few different commands.

5-30

Managing Files and Using the Desktop
Using the Desktop

To put an object on the Desktop
1. Switch to the workspace where you want the object.

2. Then:
• Drop the object's icon on the workspace backdrop.
• Or, select the object, then choose Put On Desktop from the File menu or
from the object's pop-up menu.
You can repeat these steps to put the object on the Desktop in as many
workspaces as you want.

To display the pop-up menu
for a file or directory
Mouse

1. Point to the object's icon.

2. Press and hold mouse button 3.
3. Choose a command from the menu by dragging to the command then
releasing the mouse button.
Keyboard

1. Move the highlight to the object's icon:

• For an object in a File Manager window, use @+[Tab) to highlight the
File Manager window, then use the (Tab) and direction keys to move the
highlight to the correct icon.
• For a Desktop object, use @D+(Tab) to move the highlight.
2. Press (E).
3. Choose a command from the menu by using the direction keys to highlight
the command, then press Enter.
To cancel the menu without choosing a command, press [Esc 1.

5-31

Managing Files and Using the Desktop
Using the Desktop

Each icon in a File Manager window has a popup menu.

Each icon on the Desktop also has popup menu.

To remove an object from the Desktop
1. Switch to the workspace where the object resides.
2. Locate the object's icon on the Desktop
3. Choose Remove From Desktop from the object's popup menu.
Removing an object from the Desktop does not alter the original object. That
is, the object still exists.

5-32

Locating Files

Keeping track of many files can quickly become too much to remember. File
Manager helps by providing the ability to search for a file or directory by
name. You can also search for files based on the contents of the file.

To find a file by name
1. Choose Find from the File menu. File Manager displays the Find dialog.

2. Enter the name of the file or directory you want to find into the File Name
field.
3. If you want the search to include symbolic links, choose On from the
Follow Links options menu. Otherwise, symbolic links are ignored.
4. Enter the directory where you want the search to begin into the Search
Directory field. (By default, this field contains the current working
directory of the File Manager view.)
5. Choose Start.
File Manager begins searching the Search Directory and its subdirectories
for files that match the name you've given. As matches are found, they
are listed in the Files Found list. You may stop the search at any time by
choosing Stop.
Matching Patterns

When you specify a file or directory name, you can include wildcard
characters, such as asterisk (*) and question mark (?). The * matches any
string of characters (including no characters), and ? matches any single
character.
Examples:
vue*

Matches all names that begin with the string vue.

*.vf

Matches all names that end with the . vf extension.

*.???

Matches all names that have a three-character dot extension.
5-33

Managing Files and Using the Desktop

Locating Files

To find a file by contents
1. Choose Find from the File menu. File Manager displays the Find dialog.
2. Enter the string you want to search for into the File Contents field.
Case is ignored for this string-that is, upper- and lower-case letters are
equivalent.
3. If you want the search to include symbolic links, choose On from the
Follow Links options menu. Otherwise, symbolic links are ignored.
4. Enter the directory where you want the search to begin into the Search
Directory field. (By default, this field contains the current working
directory of the File Manager view.)
5. Choose Start.
File Manager begins searching the Search Directory and its subdirectories
for files that contain the File Contents string. As matches are found, they
are listed in the Files Found list. You may stop the search at any time by
choosing Stop.
If you leave the File or Directory Name field empty, File Manager searches
every file within the Search Directory. If you know the name (or a partial

name) of the files that contains the search string, you may be able to speed
up the search by also providing a file name (or pattern) in the File or
Directory Name field. File Manager examines only the files that match the
File or Directory Name field.

5-34

Managing Files and Using the Desktop
Locating Files

Tip for Advanced Users
The file name and contents can be. specified using the same reglllar expression syntax allowed by the

find command. (Refer to the find man page for more· information.!

5-35

Altering File Manager Views

As you become more familiar with File Manager, you may want to change
some settings to better suit your needs or personal preferences. The
Preferences dialog lets you make these changes.
You may also want to alter your File Manager views by specifying which
filetypes you are not interested in seeing. You can hide certain files and
directories using the Filter List.

To change the order icons are sorted
1. Choose Set Preference from the View menu.
2. Select the sort order you prefer from the Order box.
• Alphabetically sorts all icons alphabetically by name, A-Z (ascending) or
Z-A (descending). Upper-case letters are sorted first.
• By File Type groups icons according to file type. Within each group of
similar types, the icons are sorted alphabetically.
• By Date sorts icons according to the last time the files were modified,
oldest to youngest (ascending) or youngest to oldest (descending).
• By Size sorts icons by file size, smallest to largest (ascending) or largest
to smallest (descending).
3. Select the sort direction, from the Direction box: Ascending or
Descending.
4. Choose OK.
If you have Placement set to As Placed, icons are sorted only when you

choose Clean Up from the View menu or when you choose Apply in the
Preferences dialog. If Placement is set to Sorted Grid, the icons are sorted
each time there's a change to the directory's contents or when you choose
Reread from the Directory menu.

5-36

Managing Files and Using the Desktop
Altering File Manager Views

To re-sort files and directories (clean up)
• Choose Clean Up from the View menu.
The Clean Up command sorts the objects in the current view (according to
the settings in the Set Preferences dialog) and lines them up in a grid pattern.
The settings in other File Manager windows are not affected.
The Clean Up command is inactive if you have the Placement preference set
to Sorted Grid.

To change the style of
a File Manager view (preferences)
1. Choose Set Preference from the View menu.

2. Select your preferences (Placement, Show, View, Order, and Direction).
3. Choose OK.
If you want to view the results before closing the Set Preferences dialog,

choose Apply.

5-37

Managing Files and Using the Desktop
Altering File Manager Views

To save the current preferences as your default
1. Set the preferences that you want (using Set Preferences and Modify Filter
List in the View menu).
2. Choose Save Settings from the View menu. File Manager prompts to verify
that you want the current settings saved.
3. Choose OK.
After saving the current preferences, all new File Manager views you open
uses the new preferences and filter list.

To show hidden files and directories
• Choose Show Hidden Files from the View menu.
The Show Hidden Files command is a toggle, so to hide the files, choose Show
Hidden Files again.
Hidden files and directories are those whose filetypes are selected in the
filter list. By default, the hidden filetypes are DOT _FILE, DOT _DIR, and
CURRENT _DIRECTORY.

5-38

Managing Files and Using the Desktop
Altering File Manager Views

To hide certain types of files and
directories (filter list)
1. Choose Modify Filter List from the View menu. File Manager displays the
Modify Filter List dialog
2. In the horizontal list of icons, select the icons for the filetypes you want to
be hidden.
3. Optional: Enter a name pattern into the Filter String field specifying
additional file and directory names to be hidden.
4. Choose OK.
If you want to view the results before closing the dialog, choose Apply.

To reset to the default filter list, choose Reset. This resets the default values
but does not apply them until you choose Apply or OK.

N OlE
The filteLli?tsp~cifi~s .which JilesSreJlOtto 'be displaved,lf'you selectallfiletypesorenter* into
the . Filter.· String .field no files are di$fJ/ayerJ.
I

Advanced users: The Filter String may be any regular expression. Refer to
the regexp man page (section 5) for more information.

5-39

Managing Files and Using the Desktop
Altering File Manager Views

Using the Tholboxes to Run Applications

The toolboxes are containers for applications and utilities.

The toolboxes contain icons representing applications and utilities.

There are three toolboxes:
Personal Toolbox

Your personally-configurable toolbox. You can create
actions yourself or copy them from other toolboxes.

General Toolbox

Contains applications and utilities built into HP VUE or
provided by your system administrator.

Network Toolbox

Lets you access actions on other systems.

6-2

Using the Toolboxes to Run Applications

The toolboxes are based
on File Manager

You can think of the toolboxes as File Manager views of special directories set
aside for applications and utilities. However, within a toolbox, you cannot go
up past the top level of the toolbox, which is represented in the status line by
/ ... /.

The toolboxes contain
action icons

Each application or utility is represented by an icon called an action icon.
Actions and their icons are HP VUE's way of creating a visual representation
for applications, utilities, and other commands.

See Also

•

"Basic File Management Skills" in Chapter 5 covers manipulating files (and
actions icons) .

• "Using Tools in HP VUE Lite" covers using the HP VUE Lite Toolbox .
• "General Action and Filetype Concepts" in Chapter 19 explains what
actions are and how they integrate applications into HP VUE.

6-3

The Personal Toolbox

The Personal Toolbox is a container for applications and utilties you use
frequently or create yourself.
Initially, the personal toolbox contains:
• Actions you personally place there.
• Several actions from the General Toolbox that you may want to use
frequently.
• Other actions provided by your system administator.
You have control over the contents of your Personal Toolbox. You can add and
remove tools, and organize the contents by creating subdirectories.
PreyiOl.!s HP VUE 2,01

Actions you created in HP VUE 2.01 are preserved in HP VUE 3.0.

users
See Also

• "To display HP VUE 2.01 tools from the HP VUE 3.0 toolboxes" in
Chapter 28 explains how to access your HP VUE 2.01 actions using the
toolboxes.

To open the Personal Toolbox
• Choose the Tools control in the Front Panel.

Choose the Tools control

6-4

CD to display the Personal Toolbox.

Using the Toolboxes to Run Applications

The Personal Toolbox

• Or, choose Personal in the Toolboxes subpanel.

To start an application or utility
• Double-click an action icon. If the application requires file data, a prompt is
displayed.
• Or, drop a data file onto the action icon (if the application or utility accepts

file data).
To get help on an action • Select the action and press
icon

Cill.

To add a subdirectory to the Personal Toolbox
1. Choose New from the Directory menu.
2. In the Personal Toolbox - New Directory dialog box, enter a name into the
New Directory Name Field.
3. Choose OK or press (Return ).

To make a personal action more readily available
• Put the action icon on your Desktop.
• Or, add the action to your Front Panel.
• Or, copy ((Ctrl)+drag) the action icon to a directory where you'll be using it

frequently.

6-5

Using the Toolboxes to Run Applications
The Personal Toolbox

It is often useful to copy action icons to directories containing application
data.
• If the action takes a data file, you can drop the data file on the action icon

using only one File Manager view.
• If the action prompts for data when double-clicked, you can supply a

filename (without the entire path). The action assumes the data file is
located in the same directory as the action icon.
See Also

• "To put an object on the Desktop" in Chapter 5.
• Chapter 17 explains how to add controls that start actions to the Front
Panel.

To copy a general or network action to the personal
toolbox
• Drop the action icon on the Tools control in the Front Panel.

Dropping an action icon on the Tools control

CD copies the action to your Personal Toolbox.

• Or, open both the Personal toolbox and the toolbox containing the icon.

Copy (( Ctrl )+drag) the action icon to the Personal Toolbox.

6-6

Using the Toolboxes to Run Applications

The Personal Toolbox

To add an application to the Personal Toolbox
1. If you have not already done so, install the application on your system and
find out The command line you would execute to start the application from
a Terminal Emulator.
2. Double-click CreateAction in the Utilities subdirectory of the System
Toolbox to display the Create Action dialog box.

Use Create Action to add an application to your Personal Toolbox.

3. In the Name field, type a unique name for the action.

6-7

Using the Toolboxes to Run Applications
The Personal Toolbox

4. In the Command Line field, type the command that would start the
application. If the the command takes a data file, substitute $n for each
argument, where n is 1 for the first data file, 2 for the second, etc.
(Example: Wingz $1.)
5. Use the Window Type options menu to select how the action's output
will be displayed. Select X Windows if the application creates it's own
window; select Terminal if the application runs in a Terminal Emulator
window.
6. Choose Apply.
• An icon for the action will appear in your Personal Toolbox.
• The action definition will be put in a new configuration file. A dialog box
will tell you the location of the new configuration file.
7. Test the action by doubl-clicking the action icon. If it doesn't work
properly, edit the fields in the Create Action dialog and Apply your
changes.
8. When you are satisfied that the action is working properly, choose Close.
If the application is located on another system, you can use remsh in the

Command Line. However, HP VUE actions provide a better way to start
applications on other systems.
See Also

• "Using Actions to Run Remote Applications" in Chapter 22 covers creating
actions for applications located on other systems.
• "Creating a Simple Action" in Chapter 19 explains additional features of
Create Action.
• "Creating Actions Manually" in Chapter 21 covers creating actions by
editing a configuration file.
• These are step-by-step examples for creating actions:
D "Example: Creating an action for an application" in Chapter 19
D "Example: Creating a personal action and filetype" in Chapter 19

6-8

The General Toolbox

The General Toolbox is a container for:
• Actions built into HP VUE.
• Actions placed there by your system administrator for system-wide use.
You can move about in the General Toolbox and invoke actions from it.
However, you are not allowed to write to it (unless you are logged in as
superuser). Therefore, you cannot add actions to it or reorganize it.
Some of the actions in the General Toolbox require you to be logged in as
superuser. If you try to start one of these actions logged in as yourself, a
dialog box will prompt you for the root password.
See Also

• "To start an application or utility" explains how to start actions.

To open the General Toolbox
1. Display the Toolboxes subpanel by choosing the up arrow above the Tools
control.
2. Choose General in the Toolboxes subpanel.

6-9

Using the Toolboxes to Run Applications
The General Toolbox

Choose the iiGenerai" controi to dispiay the Generai iooibox.

To make a general action more readily available
• Put the action on your Desktop.
• Or, copy the action to your Personal Toolbox.
• Or, add the action to your Front Panel.
See Also

• "To put an object on the Desktop" in Chapter 5 covers how to put an action
on the Desktop.
• "To copy a file" in Chapter 5 explains how to copy actions.
• Chapter 17 explains how to add controls that start actions to the Front
Panel.

6-10

The Network Toolbox

The Network Toolbox lets you use actions that are defined on other systems.
The top level of the Network Toolbox contains a subdirectory for each remote
system whose actions you can access. If your system has not been set up to
access remote actions, no subdirectories will be present.

The top level of the Network Toolbox contains a subdirectory
actions you can access.
See Also

CD for each system whose

• "To start an application or utility" explains how to start actions .
• "Importing and Exporting Actions" in Chapter 22 covers how to configure
the Network Toolbox.

6-11

Using the Toolboxes to Run Applications

The Network Toolbox

To open the Network Toolbox
1. Display the Toolboxes subpanel by choosing the up arrow above the Tools
control.
2. Choose Network in the Toolboxes subpanel.
3. Double-click the icon for the system that contains the action.

Choose the "Network" control to display the Network Toolbox.

6-12

Using the Toolboxes to Run Applications
The Network Toolbox

To make a network action more readily available
• Put the action on your Desktop.
• Or, copy the action to your Personal Toolbox.
• Or, add the action to your Front Panel.
See Also

6-13

Using Tools in HP VUE Lite

HP VUE Lite provides a Front Panel control and subpanel for accessing tools.

Use the HP VUE lite Tools control and subpanel to run applications.

6-14

Using the Toolboxes to Run Applications
Using Tools in HP VUE Lite

To start an application or utility in HP VUE Lite
• Choose the Tools control on the top row of the Front Panel, or one of the
controls in the Tools subpanel.
The Tools control is initially not attached to an application; you or your
system administrator can configure it to run the application of your choice.
You can also change the contents of the Tools subpanel so that it contains
applications you use often (see "To add an application to HP VUE Lite").
See Also

• "To run an action from the command line" in Chapter 23 explains how to
run actions from a Terminal Emulator.

To add an application to HP VUE Lite
Adding an application to the Tools involves configuring the Front Panel to
include the new tool.
See Also

For information on adding applications to HP VUE Lite:
• "To assign an application to the HP VUE Lite Tools control" in Chapter 23
• "To add an application to the Tools subpanel" in Chapter 23
For information on configuring the Front Panel:
• "To add or remove a control from an existing subpanel" in Chapter 17.
• "Defining Front Panel Controls" in Chapter 17
• "To create a push button for an application" in Chapter 17
For information on creating actions:
• "To use Create Action in HP VUE Lite" in Chapter 23
• "Example: Creating an action for an application" in Chapter 19 is a
step-by-step example.

6-15

Using the Toolboxes to Run Applications
Using Tools in HP VUE Lite

Using Text Editor

Text Editor is appropriate for small editing tasks such as writing memos and
editing resource files.
The lext Editor window contains:
• Title bar, showing the name of the current document.
• Menu bar, containing five menus: File, Edit, Search, Format, and Help.
• Tablet, the area where you write and edit text.

7-2

Starting and Stopping Text Editor

Text Editor is readily accessible from many locations in HP VUE:
• The Front Panel.
• File Manager.
• Terminal emulator.
Once Text Editor starts, the tablet area is ready to receive text entry or edits.

To start Text Editor
From the Front Panel

• Choose the Text Editor button in the Front Panel.

Start Text Editor by choosing its button in the Front Panel.
From File Manager

• Double-click a data file icon.
• Or, drag a file icon and drop it on the Text Editor button in the Front

Panel.

7-3

Using Text Editor
Starting and Stopping Text Editor

From a terminal
emulator

• Type the following after a command-line prompt:
vuepad filename & The filename is optional.

To close Text Editor
1. Save the open document.

2. Choose Exit from the File menu .
See Also

• "To save a document".

7-4

Opening and Saving Documents

Opening a document displays the contents of a selected file in the tablet area.
You can open new or existing documents.
Saving a document stores the edited contents into a file. You can save a
document to its original file or to a new file.

To open a new document
• Choose New from Text Editor's File menu.
New documents are titled Text Editor - (unnamed).

To open an existing document
From Text Editor

1. Choose Open from the File menu to display a dialog.

2. Enter or select the document name.
3. Choose OK.
The Open File dialog lists files and directories on your system. You can
browse the lists to locate a file.

7-5

Using Text Editor
Opening and Saving Documents

From File Manager

• Display the document's file icon in a File Manager window.
• Do one of the following:
o

Double-click the document's file icon.
select the document, then choose Edit from File Manager's Actions
menu.

o Or,

drag the document to Text Editor's tablet.

o Or,

drag the document to Text Editor's button in the Front Panel.

7-6

Using Text Editor
Opening and Saving Documents

To save a document
To a new file

1. Choose Save As from the File menu to display the Save As Dialog dialog
box.
2. If you used word wrap, choose whether or not to add newline characters
to the end of word-wrapped lines.
3. Supply the complete file name in the Save File As field.
4. Choose OK.

Use the Save As Dialog Box to Save a New File .
To the original file

• Choose Save from the File menu.
Your edited document is automatically saved to its original file. If you used
word wrap, you'll be asked whether or not to add newline characters to the
end of word-wrapped lines.

7-7

Entering and Editing Text

As you create a document, you enter and edit text. A text cursor (I) shows
your current position, and a marker C) shows where you last edited,
inserted, or selected text.

To enter new text
• Start typing. Text is inserted at the current cursor position.
• To start a new line, press

(Enter)

• To start a paragraph, press

or use word wrap.

(Enter)

twice.

To turn on/off word wrap
• Choose Word Wrap from the Edit menu.
When word wrap is on, typed words continue onto the next line when the
cursor nears the right edge of the tablet.
Using word wrap affects how you save your document. When saving, you
can:
• Add a newline character to the end of each word-wrapped line, or
• Preserve only line breaks that were created by pressing (Enter).

7-8

Using Text Editor
Entering and Editing Text

To move around in a document
Moving the cursor

• Point to the new location in the tablet and click mouse button 1.
• Or, use the cursor movement keys:

Key ...

Cursor Movement ...

Up one line.

(!)

Down one line.

o
o

Right one character.

(CTRL)+0

Right one word.

(CTRL)+0

Left one word.

(CTRL)+(!)

Beginning of the next paragraph.

(CTRL)+(!)

Beginning of the previous paragraph.

(!)

Scrolling a document

Left one character.

Beginning of the current line.

or (Home)

End of the current line.

( CTRL ) +(!) or
(CTRL)+(Home)

Beginning of the document.

(CTRL)+@

End of the document.

• Use the scroll bars.
• Or, use the scrolling keys:

Scroll Movement ...

Key . . .
(Prev) or

(Next} or (Pg Dn)

Up one page.
Down one page.

(CTRL) (Prev)

or (CTRL) (Pg up)

Left one page.

( CTRL) (Next)

or (CTRL) (Pg Dn)

Right one page.

7-9

Using Text Editor
Entering and Editing Text

To edit text
Editing characters

• Use the editing keys for simple editing.
Key

Action

(Back space)

Deletes the character before the cursor.

(Delete char)

or ~

Deletes the character following the insertion cursor.

(CTRL)+(Delete char]

Deletes all the characters from the cursor to the end
of the current line.

(Delete line)

Deletes the line containing the cursor.

Selecting text

Text must be selected before using move (cut and paste), copy, delete, or clear
Edit menu commands.

Selecting with the
mouse

• Text block:
1. Move the cursor to the beginning of the text block.
2. Hold down mouse button 1 and drag the cursor to the end of the text
block.
To change the amount of selected text, hold down (Shift] and mouse
button 1 as you drag the cursor to the new ending point for the
selection.
To unselect text, click any empty area in the window.
• Word: Double-click the word.
• Line: Triple-click the line.
• All text: Quadruple-click the tablet.

Selecting with the
keyboard

• Text block:
1. Move the cursor to the beginning of the text block.
2. Hold down (Shift} plus an arrow key to move the cursor to the end of the
text block.
• All text: Press
7-10

(Shift)+( CTRL )+0.

uSing leXT tailor

Entering and Editing Text

Replacing text

1. Select the text.

2. Type the replacement text.
Moving text (Cutting
and Pasting)

1. Select the text.
2. Choose Cut from the Edit menu. The text is erased from the tablet and
stored temporarily.
3. Move the cursor to the new location, then choose Paste from the Edit
menu.

Copying text

1. Select the text to be copied.
2. Choose Copy from the Edit menu. A copy of the text is stored temporarily.
3. Move the cursor to the new location.
4. Choose Paste from the Edit menu.

Deleting text

1. Select the text.

2. Choose Delete from the Edit menu.
Deleted text cannot be pasted, but it can be recovered with the Undo
command.
Clearing text

1. Select the text to be cleared.
2. Choose Clear from the Edit menu.
Or, press (Clear display).
Use Clear to replace a text block with spaces or blank lines .

Undoing an edit

• Choose Undo from the Edit menu.
Undo reverses the last cut, paste, clear, delete, replace, include, or format
operation.

7-11

USing Text Editor

Entering and Editing Text

To include a file
1. Position the cursor where you want to insert the document.

2. Choose Include from the File menu to open a dialog.
3. Enter or select the document name.
4. Choose OK.
The Include File dialog lists files and directories on your system. You can
browse the lists to locate a file.

Dragging a file from File 1. Open a File Manager displaying the file you want to include.
Manager

2. Position the text insertion cursor in the document where you want the file
inserted.

3. Hold down (CTRL) and mouse button 1 as you drag the file from File
Manager to Text Editor's tablet.
4. Release the mouse button, then release

7-12

(CTRL ).

Using Text Editor

Entering and Editing Text

To find text
1. Choose Find from the Search menu to open the Find dialog box.
2. Type the text to find in the Find field. The search is not case-sensitive, so
you don't need to worry about upper- or lowercase letters.
3. Choose Find to locate the first occurrence of the text.
4. To find additional occurrences:
• Choose Find again .
• Or, choose Next from the Search menu.
Find starts at the current cursor position and continues through the entire
document.

To replace text
1. Choose Replace from the Search menu.
2. Type the text to locate in the Find field. The search is not case-sensitive,
so you don't need to worry about upper- or lowercase letters.
3. Type the replacement text in the Replace With field.
4. Choose Find to locate an occurrence of the text.
5. Choose Replace.

7-13

Using Text Editor

Entering and Editing Text

Find and Replace starts at the current cursor position and continues through
the entire document.

To correct misspelled words
1. Choose Spell from the Search menu to open the Spell dialog listing
misspelled or unrecognized words.
2. Select the word in the Misspelled Word list. The selected word is
automatically pasted into the Find field.
3.. Choose Find to locate and highlight the word in the document.
4. Type the correct word into the Replace With field.
5. Choose Replace.
6. Repeat steps 2 - 5 to correct other words.

7-14

Using Text Editor
Entering and Editing Text

Correct misspelled words with the Spell dialog.

NOTE
The: Spendialog· iSJmjyavaHableforE~glish;

7-15

Using Text Editor
Entering and Editing Text

To use special characters in your text
1. Position the cursor in the text where you want the special character.

2. Type CTRL+Q, then the special character.
There are two kinds of characters you may want to include in your
document:
• Special instructional characters, such as one that forces a form feed when
printing.
• Special language characters, such as the umlaut used in German text.
Example

To embed a form feed character into your document:

1. Position the cursor.

2. Type (CTRL )+@)' then (CTRL1+(D.

7-16

Formatting and Printing Documents

Once your editing is complete, format your document by choosing margins
and justifications.

To format a document
1. Choose Settings from the Format menu.
2. Enter margins and select justifications.
3. Do one of the following:
• To format a paragraph, place the cursor in the paragraph, then choose
Paragraph .
• To format the entire document, choose All.
To use the settings after the dialog box is closed, choose Paragraph or All
from the Format menu.

Choose format settings in the Settings dialog.

7-17

Using Text Editor

Formatting and Printing Documents

To print a document
1. Open the document in Text Editor.
2. Choose Print from the File menu.
The document prints on your system's printer.

7-18

Using Terminal Emulators

A terminal emulator is an application that displays a window which allows
you to use HP-UX commands and cut and paste text within or between
terminal emulation windows.
The command line prompt is a special character that is displayed in your
terminal emulator after you press (Enter ). It can be a '/., <, $, or other special
character. A small box, called a cursor, shows where characters will appear in
the window when you type something on the keyboard.

The command line prompt CD and cursor Q) appear in terminal windows.

HP VUE provides two terminal emulators:
hpterm

hpt erm is the default terminal emulator for HP VUE. It
displays a window in which command-line prompts and soft
keys act like an HP TermO terminal.

xterm

xterm provides a terminal window that emulates DEC and
Tektronix terminals.

8-2

Starting and Stopping a Terminal Emulator

You can start a HP VUE terminal emulator either with a Front Panel control,
from the Toolbox, or by typing a command. The method of stopping the
terminal emulator is the same, regardless of how it was started.
See Also

• "Using Terminal Emulators with HP VUE Lite" explains how to start a
terminal emulator in HP VUE Lite.

To start terminal emulator with terminal control
• Click the Terminal control in the Front Panel.

Use the terminal button

CD to start a terminal emulator.

A terminal window containing a command line prompt and cursor appears.
The terminal emulator that appears is the default terminal emulator.

To open a terminal from a File Manager view
• Choose Terminal from the Directory menu.
This opens a Terminal Emulator with the same current working directory as
the File Manager view where it is started.

8-3

Using Terminal Emulators
Starting and Stopping a Terminal Emulator

To start a terminal emulator from the command line
1. At the command line prompt, type the name of the terminal emulator and
any options you want, using:
hpterm

[options]

Nt;

Or:
xterm

[options]

Nt;

Where:
options

Represents optional items to customize the terminal
emulator.

Specifies that the terminal emulator runs in the
background, that is, you can continue working in your
original window while the terminal emulator is also
running.

The terminal emulator starts in the current workspace unless directed
otherwise by options.
Examples

The following command starts an hpt erm window with a black background
and a white foreground. (This window will not participate in dynamic color
changes through Style Manager since colors are specified directly.)
hpterm -bg Black -fg White

Nt;

The following command starts an xterm window in the workspace named
"Project Notes":
xterm -xrm '*workspaceList:

"Project Notes'"

Nt;

The following command starts an hpterm window on a screen on the system
named "LGMCD":
hpterm -display LGMCD:O.l

See Also

Nt;

• Refer to the xterm or hpterm man pages for details about the options
available for each.

8-4

Using Terminal Emulators

Starting and Stopping a Terminal Emulator

To start a terminal emulator from the Toolbox
• Execute the hpterm or xterm action in the Utilities subdirectory of the
General Toolbox directory.

To close a terminal emulator window
Menu button

• Double-click on the window menu button in the window frame.

Close a terminal emulator with the window menu button CD.
Command line

• Type:
exit (Return)

8-5

Using the Terminal Emulator

The terminal emulator window provides a means to enter HP-UX commands
and the ability to cut and paste text between and within windows.

To cut and paste text
You can select text within one window and copy it to another location within
that window, or to another terminal emulator window.
The original text is left in place. If you want to delete it, you must do so
manually.
cutting text

1. Move the pointer over the first character you want to cut.

2. Press and hold down mouse button 1.
3. Drag the pointer over the text you want to move. The text appears
highlighted.
4. Release mouse button 1 after all the text you want to cut is hightlighted.
The highlighted text is copied to an internal "clipboard". The text is not
removed from your original source.
pasting text

1. Position the cursor where you want to insert the text.

2. Click mouse button 2.
A copy of the contents of the clipboard is pasted at the location you
indicated. You can make additional copies by repeating the above steps.

8-6

Using Terminal Emulators
Using the Terminal Emulator

To resize the window contents
• Type the following at the conunand-line prompt:
eval 'resize' (Enter]

You can change the size of the window using the frame components.
However, applications running within the window may not know about the
resizing and act as if the window were the original size.

To start applications in a terminal window
• Enter the conunand to start the application at the conunand line prompt.
The general syntax for starting an application is:
application [options] &;

Example

application

The application name.

options

A list of optional information to be passed to the application.

Indicates that the application runs in the background; that
is, you can continue to use the terminal emulator window
while the application is also running.

The following example starts a digital clock from the conunand line:
xclock -digital

See Also

• Refer to the man page or other documentation for each application to find
the conunand and options to use for that application.

8-7

Customizing Your Terminal Emulator

There are several ways in which you can customize your terminal emulator:
• Run the terminal emulator with special options, such as scrollbars.
• Use a different terminal emulator.
• Run the terminal emulator on another system.
• Run the terminal emulator using non-English characters.
See Also

• The hpterm or xterm man page lists all the options available.
• "Using a Non-English Terminal Emulator" in Chapter 27 explains how to
run a terminal emulator with non-English characters.
• "Changing the Default Terminal, Editor, and Mailer" in Chapter 18 explains
how to change the terminal emulator that appears by default when you
press the Terminal control.

To specify scrollbars
1. Use the EditResources action to specify a scrollBar resource for the

terminal emulator.
2. Log out, then log back in for the current session. (For home session, set
home session, log out, then log back in.)
If the value of scrollBar is True, the terminal emulator windows will have

scrollbars. If the value is False, they will not have scrollbars.
Example

The following line sets scrollbars in all hpt erm windows:
hpterm*scrollBar:

True

The following line sets scrollbars only for hpt erm windows named
"localTerminal" :
hpterm*localTerminal*scrollbar:

8-8

True

Using Terminal Emulators

Customizing Your Terminal Emulator

To display a terminal emulator window on another
system
Using ·display option

• Run hpterm or xterm with the -display option.
The -display option has the fonnat:
-display host: display. screen

where:

host

is the name of a valid system on the network.

display

is the number of the display on the host.

screen

is the screen within the display. The default is O.

You can find these values by typing env, and examining the DISPLAY line.
The tenninal emulator is running on your system, but the window shows on
another system.
The following starts an hpterm window on the host computer named anna:
hpterm -display anna:O.1 &

Using rlogin

• Run rlogin from a tenninal window on your system.
You can use an existing tenninal emulator window to log into a remote host.
Once the window is acting as a tenninal to the remote host, you can run
applications there, redirecting the display back to your system if you desire.
For example, the following command logs onto a system named there, runs
the client xload, and redirects the display back to your original system.
Assume your system is named here.
rlogin there
xload -display here:O.O

Using remsh

• Run the remsh command from a tenninal window on your system.
The remsh command starts a shell on a remote host, perfonns some client
(often starting a tenninal emulator on that host), and redirects the display
back to your original system if desired. It has the syntax:
8-9

Using Terminal Emulators

Customizing Your Terminal Emulator

remsh rerrwte -n client -display system:display.screen

where:
remote

The remote host name.

client

The program you want to run on the remote host.

local:display. screen

The host and display the results are to be displayed
on.

For example, the following command runs xload on the remote host named
there, and directs output back to your system, here.
remsh there -n /usr/bin/Xll/xload -display here:O.O

The remsh command is often used when customizing a menu to access other
hosts.
See Also

• Chapter 22 contains more information about networks and running
applications on other computers.

To set terminal control characters
1. Use the EditResources action to update the ttyModes resource.
2. Choose Restart Workspace Manager from the workspace menu.
Because the hpterm and xterm only emulate a terminal, your control
characters might not be what you are used to on a physical terminal. The
ttyModes resource allows you to set control characters for your terminal
emulator.

8-10

Using Terminal Emulators
Customizing Your Terminal Emulator

By default, Login Manager sets the following control characters.
Control name

Character

erase

AH (backspace erases characters)

intr

AC (interrupt - cancel the current operation and redisplay the
cormnand line prompt.)

kill

AU (stop an operation or application)

start

AQ (accept keyboard input - used to "continue" an
application that has been paused.)

stop

AS (do not accept keyboard input - used to "pause" an
application. )

swtch

A@ (switch between layers in a shell.)

The "~,, character stands for the
progress, you press @) (9.

(Ctrl)

key. So to interrupt an operation in

The syntax for this resource is:
ttyModes:

name

where name is the control, and C is the character. For example, the default
value of ttyModes describing the above list is:
ttyModes: erase

intr

kill

start -Q stop

swtch

Additional controls are listed in the xterm or hpterm man pages.
See Also

• Chapter 25 for information about how and where to set resources.

8-11

Using Terminal Emulators with HP VUE Lite

Terminal control

• Click the Terminal control on the Front Panel.
The default terminal emulator will display a window containing a command
line prompt and a cursor.

Use the HP VUE Lite terminal control
Menu

CD to start a terminal emulator.

1. Click on the arrow above the Terminal front panel control.
2. Select one of the choices from the slide up menu:

Make a selection from the Terminals subpanel.

You can start an hpterm or an xterm terminal emulator.
8-12

Using Terminal Emulators
Using Terminal Emulators with HP VUE Lite

3. If you chose a remote terminal emulator, a dialog box appears. Enter the
name of the system you want to log on to.

Enter the host name in the Host Dialog.

See Also

• "To display a terminal emulator window on another system" explains how
the terminal window can run on another computer.

8-13

Using Terminal Emulators

Using Terminal Emulators with HP VUE lite

;Qtl"st:otn~zing,Ap:pe,aran¢:~';:;'

. ·~nd?·,Behavior
-' ~;.;' '; \

. ,>2

-:.,~,

,,-,<,'

Customizing Appearance and Behavior

Color

Workspace colors and palettes.

Font

Application font sizes.

Backdrop

Workspace backdrop patterns.

Keyboard

Key click volume or character repeat capability.

Mouse

Mouse button click settings, double-click speed, pointer
acceleration, or pointer movement threshold.

Audio

Beeper volume, tone, or duration.

Screen

Number of minutes before your screen times out or whether
or not your screen is covered and locked at time out.

Window

How a window acquires focus, if the window raises when it
receives focus, or where window icons are placed.

Startup

How your session begins and ends.

If you're working in an HP VUE Lite session, Style Manager contains four

buttons-Color, Backdrop, Font, and Window.
Starting Style Manager • Choose the Style Manager button in the Front Panel.

9-2

Customizing Appearance and Behavior

To start Style Manager, choose its control
See Also

CD in the Front Panel.

There are other behaviors you may want to change in your HP VUE working
environment, such as changing what a button does in the front panel, or
changing your default editor from Text Editor to either vi or emacs.
• Chapter 17 explains how to customize Front Panel behavior.
• Chapter 18 explains how to change your default Terminal Emulator, Mailer,
and Editor.
• "Workspace Manager Menus" in Chapter 24 explains how to add or delete
commands from menus.
• "Creating a Simple Filetype" in Chapter 19 explains how to define a file
type. When you define a file type, you can specify the actions associated
with the file.
• Chapter 14 explains how to change variables affecting your windowing
environment.

9-3

Customizing Screen Appearance

The visual elements of your screen can be easily changed with Style Manager:
• Workspace colors.
• Workspace backdrop patterns.
• Font sizes used to label windows and enter text.

To select a palette
l. Choose Style Manager's Color button.

2. Select a palette from the Palettes list.
3. Choose OK.
Workspace colors come from predefined color palettes. Palettes that come
with your system are listed in the Color dialog.

9-4

Customizing Appearance and Behavior
Customizing Screen Appearance

CD List of palettes.
@ Color buttons, representing the selected palette's colors.

To modify a palette
1. Select a palette in the Color dialog.
2. Double-click a color button to open the Modify dialog.
Or, click the button, then click Modify.
3. Adjust the settings.
4. Choose OK in the Modify dialog.
5. Repeat steps 2-4 to modify another color button.
6. Choose OK in the Color dialog.

9-5

Customizing Appearance and Behavior
Customizing Screen Appearance

CD Shows the current color.
Q) Shows the new color as you make changes.

® Displays a pointer for you to choose a color in your workspace.
@) Changes red, green, and blue values.

® Changes red, green, and blue proportions.
@ Changes the color's intensity.
(f) Changes the color's brightness.
Grabbing a color from
the workspace

1. Choose Grab Color to get the grab pointer.
2. Click the desired color to make it the New color.

9-6

Customizing Appearance and Behavior
Customizing Screen Appearance

To create a custom palette
(by copying and modifying an existing palette)
1. Choose Add in the Color dialog.
2. Type the new palette name in the New Palette Name field.
3. Choose OK in the Add Palette dialog.
4. Modify the palette.
5. Choose OK in the Color dialog.
Adding a palette makes a copy of the currently selected palette and gives the
copy a unique name. You then create a palette by modifying the copy, thus
keeping the original palette intact.

To delete a palette
1. Select the palette from the Palettes list.
2. Choose Delete.
3. Choose OK in the Delete Palette dialog.
Restoring a deleted
palette

1. Open a File Manager showing HomeDirectory/. vue/palettes.
2. Rename the deleted palette from -PaletteName.vp to PaletteName.vp.
3. Restart Style Manager (close, then reopen).
When you delete a palette, its name is prefixed with
. vue/palettes in your home directory.

and placed in

9-7

Customizing Appearance and Behavior
Customizing Screen Appearance

To change the number of colors used by HP VUE
1. Choose HP VUE Color Use in the Color dialog.

2. Select the color use.
3. Choose OK.
The change takes effect the next time you log in.

Your display type and the HP VUE Color Use selection determine the number
of colors buttons that make up a palette.
While you can't use more colors than your display allows, you can limit the
amount of colors used by HP VUE by specifying a lower-valued display type.
For example, if you have a high color display and want to run a color-rich
application such as a CAD program, you could choose Low Color to lower the
amount of colors that HP VUE uses. The color difference is available for the
CAD program.

9-8

Customizing Appearance and Behavior
Customizing Screen Appearance

To select a font size
1. Choose Style Manager's Font button.

2. Select a font size.
3. Choose OK.
Window labels and text show the new font size as applications are started.

9-9

Customizing Appearance and Behavior
Customizing Screen Appearance

To select a backdrop
1. Switch to the workspace in which you want the backdrop.
2. Choose Style Manager's Backdrop button.
3. Select a backdrop.
4. Choose Apply.

A backdrop is a pattern that covers the screen area underneath your
windows. A unique backdrop for each workspace adds variety and helps you
to quickly identify the workspace.

9-10

Customizing System Behavior

Behavior settings for system devices can be easily adjusted to fit your
preferences and needs:
• Key click volume and character repeat.
• Mouse button click settings, double-click speed, pointer acceleration, or
pointer movement threshold.
• Audio beeper volume, tone, or duration.
• Screen time outs and cover when not in use.
• Window focus, movement, and icon behavior.

To change keyboard behavior
1. Choose Style Manager's Keyboard button.

2. Select settings.
3. Choose OK.

Auto Repeat:

Have a character repeat as you hold down its key.

9-11

Customizing Appearance and Behavior
Customizing System Behavior

Click Volume:

Tum off key click (when at 0%) or change volume (up to
100%).

To change mouse behavior
1. Choose Style Manager's Mouse button.

2. Select settings.
3. Choose OK.
A new double-click speed takes effect the next time you log in.

Right-Handed:

Use standard settings for mouse button clicks.

Left-Handed:

Reverse standard settings for mouse button clicks.

9-12

Customizing Appearance and Behavior
Customizing System Behavior

Double-Click:

Choose double-click time from .1 to 1 second. To test,
double-click the mouse image.

Acceleration:

Choose how fast the pointer moves across the display.

Threshold:

Choose the distance (in pixels) the pointer moves at a slow
speed in a short amount of time before the pointer moves at
the "accelerated" rate.

To change audio behavior
1. Choose Style Manager's Audio button.
2. Select settings.
3. Choose OK.

Volume:

Turn off beeper sound (at 0%) or change volume (up to
100%).

Tone:

Choose a beeper pitch from 82 to 9000 Hertz.

Duration:

Choose how long the beeper sounds from .1 to 2.5 seconds.

9-13

Customizing Appearance and Behavior
Customizing System Behavior

To change screen settings
1. Choose Style Manager's Screen button.

2. Select settings.
3. Choose OK.

Screen Saver:

Turns screen saver on or off.

Screen Lock On Timeout:

If screen saver is on and your server supports

this feature, also locks your screen.
Timeout:

Specifies the time interval (from 1 to 120
minutes) from the last pointer move or keystroke
to when the screen times out.

Full Screen Cover:

Choose whether or not to cover your screen
when Lock is used from the Front Panel.

9-14

Customizing Appearance and Behavior
Customizing System Behavior

If you have a color display, bright colors on the screen can "bum" into

the picture tube. A time out - when the screen goes blank or is covered prevents this from happening.

To change window behavior
l. Choose Style Manager's Window button.

2. Select settings.
3. Choose OK.
4. Choose OK when asked to Restart the Workspace Manager.

9-15

Customizing Appearance and Behavior
Customizing System Behavior

Focus follows Mouse:

Makes a window active when the mouse pointer
enters it.

Click In Window For Focus: Makes the window active when the mouse
pointer enters the window and you click mouse
button 1.
Raise Window With Focus:

Brings a partially concealed window to the top
when it becomes active.

Opaque Move:

Moves the window during a window move
(instead of moving its outline first).

Use Icon Box:

Displays an icon box for window icons.

Place On Desktop:

Places window icons on the desktop.

To change how your next session starts
1. Choose Style Manager's Startup button.

2. Select settings.
3. Choose OK.
Whenever you are logged into HP VUE, you are working in a current session.
By default, when you log out, HP VUE saves your current session and
restores it the next time you log in.
You can also save a home session, a session you choose to be the one to
which you can always return, regardless of what you do during the current
session.

9-16

Customizing Appearance and Behavior
Customizing System Behavior

Resume current session:

Starts your next session the way you left
your last one, including any setting, client, or
resource modifications.

Return to Home session:

Starts the session that you've designated as
your Home Session (see Set Home Session). If
you have never set a home session, the system
default session starts.

Ask me at Logout:

Asks you at logout whether to restart the
current session or to restore the home session.

Logout Confirmation Dialog: When On, asks you to confirm that you want to
log out.
Set Home Session:

Defines a new Home Session based on your
current state.

9-17

Customizing Appearance and Behavior
Customizing System Behavior

9-18

Annotating Files

An annotated file is a file that has additional data attached to it. The file can
be of any type, and the data can be text or audio.
File annotations are created and accessed using File Annotator, which
provides the ability to:
• Review, create, edit, and delete annotations.
• Turn a file into an annotation or an annotation into a file.
To annotate a file, you must have write permission for the directory
containing the file. An annotated file is underlined in File Manager.
Your system must be configured for audio before you can record or hear audio
annotations.
See Also

• "Configuring Audio Devices (HP-UX only)" in Chapter 13 gives audio
configuring information if you have audio capability.

10-2

Reviewing Annotations Attached to a File

The File Annotator window lists all annotations attached to a file and shows
information about each annotation:
• The type of annotation: text or audio.
• The person who created the annotation.
• The date and time the annotation was created or last modified.
You can review a single annotation or cue up all annotations to be read or
played back.

To see a list of annotations attached to a file
1. In a File Manager window, select the annotated file.
2. Choose Annotate from the File menu to open File Annotator.

10-3

Annotating Files
Reviewing Annotations Attached to a File

To review a single annotation (text and audio)
Text

1. Open File Manager and select the annotated file.
2. Choose Annotate from the File menu.
3. Double-click the annotation in the list to open a dialog displaying the
message.

Audio

1. Open File Manager and select the annotated file.
2. Choose Annotate from the File menu.
3. Double-click the annotation in the list.

10-4

Annotating Files

Reviewing Annotations Attached to a File

The message plays back as soon as the dialog opens. Use the audio buttons
much like you use a tape recorder's buttons.
• To raise or lower the volume, adjust the Volume control.
• To temporarily suspend playback, choose Pause. Choose Pause again to
continue playback.
• To repeat the message, choose Replay.
• To choose a new listening device, select headphones or speakers. The new
device takes effect the next time an annotation is played.
• To stop playback and close the dialog, choose Stop.

To review all annotations attached to a file
1. Open File Manager and select the annotated file.
2. Choose Review Annotations from the File menu. A Review Annotations
dialog appears for each type (text or audio) of annotation attached to the
file.
3. Choose Next to review the next annotation.
When all annotations have been reviewed, the focus moves to Stop.
During an audio review, choosing Next skips the rest of the current message
and moves on to the next.

10-5

Annotating Files

Reviewing Annotations Attached to a File

To delete annotations
Deleting a single
annotation

1. Open File Manager and select the annotated file.
2. Choose Annotate from the File menu.
3. Select the annotation to be deleted.
4. Choose Delete from the Annotations menu.
To delete an annotation, you must have write permission for the directory
containing the annotated file.

Deleting all annotations

1. Select the file and choose Annotate from the File menu.
2. Choose Delete All from the Annotations menu.
The Delete menu choices are inactive if you do not have Write permission for
the directory in which the annotated file resides.

10-6

Working with Text Annotations

Text annotations, like documents, can be created, edited, and printed.

To create a text annotation
1. Open File Manager and select the file to be annotated.
2. Choose Annotate from the File menu to open File Annotator.
3. Choose Add Text from the Annotations menu to open the Add Text
Annotation dialog.
4. Type the annotation.
5. Choose OK.

10-7

Annotating Files

Working with Text Annotations

To edit an existing text annotation
1. Open File Manager and select the file.
2. Choose Annotate from the File menu to open File Annotator.
3. Select the annotation to be edited.
4. Choose Edit from the Annotations menu to open the Edit Text Annotation
dialog.
5. Edit the text.
6. Choose OK.
You must be the annotation's author to edit it.
Including an existing
file into an annotation

1. While editing an annotation, place the cursor where you want to insert the

existing file's contents.
2. Choose Include from the File menu to open a dialog.
3. Type the name of the file to be included. Use the space bar for file name
completion.
4. Choose OK in the Include Text File dialog. The file's contents are inserted
into the Add Text Annotation dialog.
5. Choose OK.

To print a text annotation
1. Save the text annotation into a separate file.
2. Open the file in Text Editor.
3. Choose Print from Text Editor's File menu .
See Also

• "To save an annotation as a file" explains how to save an annotation as a
separate file.

10-8

Working with Audio Annotations

An audio annotation is a recorded message that is represented visually by
an audio waveform. The waveform is automatically created as you record
your message. Editing the waveform is similar to editing a text file; you can
insert more information or append the message, delete a selected segment,
and move or copy segments.

To record a new audio annotation
1. Open File Manager and select the file.
2. Choose Annotate from the File menu to open the File Annotator.
3. Choose Add Audio from the Annotations menu to open the Add Audio
Annotation dialog.
4. Choose Record and speak into the microphone.
5. Choose Stop.
6. Choose OK.

10-9

Annotating Files

Working with Audio Annotations

CD Record.
(£)
@
@)
@

Stop.
Play.
Pause.
Time Counter.

@ Zoom In.
(£) Zoom Out.
@) Headphones.

® Speaker.

Operating audio buttons Use the audio buttons much like you use a tape recorder's buttons.

• To raise or lower the volume, adjust the Volume control.
• To temporarily suspend recording, choose Pause. Choose Pause again to
continue recording, or choose Stop to end the recording.
• To hear the complete message, choose Play.
• To append the message, choose Record.
• To erase the message you're currently recording, choose Erase from the
Edit menu.
• To discard the message and close the dialog, choose Cancel.

10-10

Annotating Files
Working with Audio Annotations

To select a portion of the recording to edit
Selecting a single point

•

Point to a place on the wavefonn and click mouse button 1.

The audio pointer is a vertical line that shows your current position in the
audio waveform.
Erase, Play, Paste, Record, Insert, and Save operations start at the selected
point.
Selecting a point unselects any previously selected point or segment.
Selecting a segment

1. Point to the beginning of the segment.
2. Hold down mouse button 1 as you drag the pointer to the end of the
segment.

Erase, Play, Paste, Record, Cut, Copy, Insert, and Save operations affect the
selected segment.
Selecting a segment unselects any previously selected point or segment. Only
one segment can be selected at a time.

10-11

Annotating Files
Working with Audio Annotations

To lengthen or shorten the segment, drag the segment end marker using
+ mouse button 1.
Clearing the markers

(Shift)

• Choose Clear Markers from the Edit menu.
Clear Markers clears both the segment and point markers.

Zooming in

• Choose Zoom In to see a more detailed view of the waveform.
Each time you choose Zoom In, you get a closer view of the waveform, which
allows for more precise segment selection.
Choose Zoom Out to see a less detailed view of the waveform.

To edit a recording
Appending the message

1. Choose Clear Markers from the Edit menu.

2. Choose Record and speak into the microphone.
3. Choose Stop.
Hearing a segment

1. Select a segment or a point from which to start playback.
2. Choose Play.

Recording over a
segment

1. Select the segment.
2. Choose Record and speak into the microphone.
3. Choose Stop.
The selected area is replaced by the newly recorded audio data.

10-12

Annotating Files
Worl(ing with Audio Annotations

Inserting a segment

1. Select the point where the new information is to be inserted.
2. Choose Record and speak into the microphone.
3. Choose Stop.

Erasing part of a
message

1. Select the segment to be erased.
2. Choose Erase from the Edit menu.
Only the marked segment is erased.

Erasing to the end

1. Select the point at which to start erasing.

2. Choose Erase from the Edit menu.
Erasing the entire
message

Copying a segment

1. Clear the markers.
2. Choose Erase from the Edit menu.
1. Select the segment to be copied.
2. Choose Copy from the Edit menu.
3. Select the point where the new information is to be inserted.
Or, select the segment that will be replaced.
4. Choose Paste from the Edit menu.

Moving a segment

1. Select the segment to be moved.
2. Choose Cut from the Edit menu.
3. Select the point where the new information is to be moved.
4. Choose Paste from the Edit menu.

Including an existing
file

1. Select the point where the existing file will be inserted, or select the
segment to be replaced.
2. Choose Include.
3. Type the name and path of the file to be included. Use the space bar for
file name completion.

10-13

Annotating Files

Working with Audio Annotations

If no point or segment is specified, the external file is appended to the end of

the current annotation.

10-14

Using Files with Annotations

Annotations are attached to the file they annotate. There may be times when
you want to:
• Save an annotation as a separate file.
• Create an annotation from the contents of a separate file.

To save an annotation as a file
1. Open File Manager and select the file.
2. Choose Annotate from the File menu.
3. Select the annotation to be saved as a file.
4. Choose Show from the Annotations menu to open the Show Annotation
dialog.
5. Choose Save from the File menu to open the Save dialog.
6. Type the name and path of the file into which the annotation will be
saved. Use the space bar for file name completion.
7. Press (Enter) or choose OK.
You can save both text and audio annotations as files.
To save only a portion of an audio annotation, select the audio segment before
choosing Save.

10-15

Annotating Files
Using Files with Annotations

To create an annotation from a file
Text

1. Open File Manager and select the file to be annotated.
2. Choose Annotate from the File menu.

3. Choose Add Text from the Annotations menu to open the Add Text
Annotation dialog.
4. Choose Include from the File menu to open the Include Text File dialog.

5. Type the name and path of the file to be included and press [Enter) or
choose OK. Use the space bar for file name completion. The file's contents
display in the dialog.

6. Choose OK in the Add Text Annotation dialog.
Audio

1. Open File Manager and select the file to be annotated.
2. Choose Annotate from the File menu.

3. Choose Add Audio from the Annotations menu to open the Add Audio
Annotation dialog.
4. Choose Include from the File menu to open the Include Audio File dialog.
5. Type the name and path of the file to be included and press [Enter) or
choose OK. Use the space bar for file name completion.
6. Choose OK in the Add Audio Annotation dialog.

10-16

Part 2

Ch(lpter 11
Cl1apter 12
Cha~tei 13 .
~4apt~rl~

"i ClUlpt~r"l~

Cp(lp~~r: 10
'c:h~pter't7' .
'. Ch,apter' ~8

~l!~~ter'~?,
Chapt~r2o.
,~hapter21
.~hapt~r,2Z

"C:lr~P~~t:. 23

C:~&Pter 24
'C:ha,P!er '2.5
• 'Ch&Pter2(i"
, Cbapter 27
',Clt~~tE!i" Z~,

"t~apt~t'jZ9,

Enahl,ing anpiPisabling H~ VUE
C~stomiZ,iiig;iI.-Qg~:,¥anager
,Spe~i(lt~oPfigu~~tio~s '
'EnviFQnriien'ty~tiables ' '.' 'i.'

,,'~dmi~lst .• " \HPVpE!Se~s!~ri,s,

")VQ~~~'1If~t "\.J~~~s'.1Jild.,,Backdr9P.I1Uage~
Cust9~~i1l~;t~e,F~o~t'fane,1"

'>' ,.' '., ", '

Thrminal, 'Ma~~r; ,Editor" ~nd' PrinteJ: CQnfi!wration
Int~odu~~iQn to .~(;t~ons and EiletYP.es
, MQ~e A90ptFil~t.yp.e,s,
' ,.
More Ab0l.ltActions '. " .."
.
N etwprkiiig:·and· pi~triblJted Computing
Cu~toiniZ4igflP\VVeLite' "".
'
Cqst~m,~ziJilg\Vor~&pace' MaJ}!lger
Using i~~s'0l.lrc~s, ."i ",
. EontJ'Color" ,'ane Appllea,ti?nReso'urce,s,
Non..i~ngliS,~/H~JYUE.Se~sipns

E~t~~yipl.ls·~VUEj3.0or ~trUsers

Trbublesftoot;u1g
".'i
\(,

Enabling and Disabling HP VUE

This chapter covers how to start and halt the HP VUE Login Manager. Login
Manager is the portion of HP VUE responsible for starting the X server,
validating the user's login and password, and starting sessions. Once Login
Manager is running, the user has access to HP VUE sessions and other login
options.

NOTE
This chapter appliesJo HPowUXsystems only.,
'- ~.

you ,must, have ro~!' permis~ionto confIgure a ~Vste[T1. to start '6rs1opH~ VUg:

Some systems are set up to automatically start Login Manager during the
system ini t process. These systems automatically display the HP VUE Login
Screen when they are rebooted.
Other systems may be initially configured to run a console. There are two
ways to start HP VUE:
• You can configure the system to automatically start HP VUE when the
system is rebooted. This is done by changing the default run level for the
system.
• You can manually change the system run level from the console. This has
no effect on what happens when you reboot your system.
Once a system is running Login Manager, HP VUE can be halted by:
• Changing the default run level.
• Manually changing the run level from the console.

11-2

Before You Start HP VUE

If your system has one of these special configurations, you may need to edit

certain Login Manager files before starting HP VUE:
• If the system console is a non-bitmap device, see "Configuring

Character-Display Consoles" in Chapter 13.
• If the system is part of a diskess cluster, see "Configuring Diskless Clusters"
in Chapter 13.
• If the system is an X terminal or a host for X terminals, see "Configuring

X-Terminals" in Chapter 13.
• If the system has more than one display, see "Configuring

Multiple-Displays" in Chapter 13.

11-3

Starting HP VUE automatically

When HP VUE is started automatically, the HP VUE Login Manager is run
when the system is booted.
To start HP VUE automatically, the system default run level must match a run
level assigned to HP VUE. The default run level and run level assignments are
made in /etc/inittab.
There are two ways to change the default system run level in
/etc/inittab:
• If the IGNITION fileset is installed on your system, you may be able to use

the script / etc/newconfig/Igni tion/ configure. sh.
• You can manually edit / etc/ ini ttab in a text editor.

To use 'configure.sh' to edit 'inittab'
Requirements for using
'configure.sh'

You can use configure. sh to edit / etc/ ini ttab if your system meets these
requirements:
• The console is a bitmap display.
• The / etc/ ini ttab file has not been extensively customized.
If your system is not suitable for running the conf igure . sh script, you must

edit / etc/ ini ttab using a text editor.
Procedure for running
'configure.sh'

1. Log in as root.

2. Run the script by executing:
/etc/newconfig/Ignition/configure.sh

For a diskless cluster, you must run the script on every cnode that will be
running HP VUE.
3. Respond appropriately to the prompts.
11-4

Enabling and Disabling HP VUE
Starting HP VUE automatically

What 'configure.sh'
does

The script changes the system default run level to 4.

To edit '/etc/inittab' in a text editor
• Log in as root.
• Make a backup copy of /etc/inittab.
• Edit /etc/inittab (in a diskless cluster, /etc/inittab is a
context-dependent file). The default run level (ini tdef aul t) must match
a run level specified for respawning HP VUE (vue). The / etc/ ini ttab file
shipped with HP-UX 9.0 systems respawns HP VUE at run levels 3 and 4;
you should avoid changing this line.
Example

The following portion of / etc/ini ttab illustrates how to automatically start
HP VUE when the system is booted. The default run level is set to 4-a run
level assigned to HP VUE.
init:4:initdefault:

cons:012456:respawn:/etc/getty -h console console
vue :34:respawn:/etc/vuerc

11-5

Starting HP VUE manually

If Login Manager is not started automatically when the system is booted, it

can be started later from the console.
1. Log into your system console as root.
2. Examine (for example, with the page command) the contents of
/etc/inittab. Look for the line that respawns HP VUE, and make note
of the run level(s) used. For example, the following lines specify that HP
VUE runs at run levels 3 and 4.
vue :34:respawn:/etc/vuerc

3. Execute:
/etc/telinit n; exit

where n is a run level assigned to HP VIJE.
Example

If /etc/inittab contains these lines:
init:2:initdefault:

cons:012456:respawn:/etc/getty -h console console
vue :34:respawn:/etc/vuerc

then HP VUE does not start when the system is booted. However, you can
start HP VUE by executing:
/etc/telinit 3; exit

11-6

/etc/telinit 4; exit

Stopping HP VUE

There are two basic ways to stop HP VUE:
• Change the system default run level so that HP VUE does not start when
the system is rebooted. This is done by changing the default run level.
• Change system run levels manually.

To configure the system so that HP VUE does not run
at boot time
The following procedure prevents HP VUE from starting automatically when
the system is booted. However, HP VUE can be started later by changing run
levels.
• If you are in an HP VUE session, log out.
• Use the Options menu on the login screen to enter No Windows mode.
• Log in as root.
• Make a backup copy of /etc/inittab.
• Edit /etc/inittab. Change the default run level (initdefault) to a run
level that runs a console but does not run HP VUE.
Example

The following lines show a portion of /etc/inittab in which the default run
level is set to 2, which runs a console. Since the file specifies that HP VUE
runs only at run levels 3 and 4, HP VUE does will not start automatically
when the system is booted.
init:2:initdefault:

cons:012456:respawn:/etc/getty -h console console
vue :34:respawn:/etc/vuerc

11-7

Enabling and Disabling HP VUE
Stopping HP VUE

To stop HP VUE manually
1. If you are in an HP VUE session, log out.
2. Use the Options menu on the login screen to enter No Windows Mode.
Alternatively, you can log into a fail-safe session.
3. Log in as root.
4. Switch to a run level that does not run HP VUE by executing:
/etc/telinit n; exit

where n is a run level for which / etc/ ini ttab specifies a terminal or
console and does not specify HP VUE.
Example

Suppose the contents of /etc/inittab is:
init:4:initdefault:

cons:012456:respawn:/etc/getty -h console console
vue :34:respawn:/etc/vuerc

The following command would stop HP VUE:
/etc/telinit 2; exit

11-8

Customizing Login Manager

Login manager is responsible for:
• Reading initial configuration files. These files configure HP VUE for various
types of systems, such as character-display consoles, X-terminals, and
systems with multiple displays
• Starting the X server.
• Displaying the login screen and validating the login and password supplied
by the user.
• Invoking the HP VUE Session Manager.
See Also

• For information on special configurations.
o "Configuring Character-Display Consoles" in Chapter 13
[J "Configuring X-Terminals" in Chapter 13.
[J "Configuring Diskless Clusters" in Chapter 13.
o "Configuring Multiple-Displays" in Chapter 13.
o "Configuring Multiple Screens" in Chapter 13.
o "Running Starbase Applications" in Chapter 13.
o "Partial HP VUE Environments" in Chapter 13.
• For information on environment variables:
o "Default Environment Variables" in Chapter 14
o "Setting System-Wide Environment Variables" in Chapter 14
o "Setting Personal Environment Variables" in Chapter 14

12-2

Customizing the Login Screen

You can customize:
• Appearance-the logo, greeting, color, and fonts.
• Entries in the language menu.
• The transition screen-the screen displayed after you log in, before your
workspace backdrops appear.
See Also

• The vuelogin(lx) manpage contains additional information about Login
Manager resources.

To change the login screen appearance
• Set the appropriate resource in /usr/vue/config/Xresources.

Vuelogin*resource:

value

• Reread the Login Manager configuration files (see "To reread Login Manager
configuration files").

Logo image

Logo position

Vuelogin*logo*bitmapFile: path
• Percent of the logo above the login matte:

Vuelogin*logo*verticalOffset: percent
• x,y position:

Vuelogin*logo*x:
Vuelogin*logo*y:

pi~~
pi~~

12-3

Customizing Login Manager

Customizing the Login Screen

General logo
appearance

Vuelogin*logo*resource:

Fonts

Vuelogin*textFont:
Vuelogin*labelFont:

Content and appearance
of greeting:

Vuelogin*greeting.labelString:
Vuelogin*greeting.fontList:

value

font
font
string
font

To include the host name in the greeting, use the string %LocalHost%.
Example

These lines in Xresources set colors and fonts for the login screen.
Vuelogin*background:
Vuelogin*highlightColor:
Vuelogin*textFont:
Vuelogin*labelFont:

Example

These lines in Xresources specifies a bitmap and background color for the
logo:
Vuelogin*logo*bitmapFile:
Vuelogin*logo*background:

Example

lightgray
#ef506f
-*-prestige-medium-r--normal-*-128-72-*
-*-swiss 742-medium-r-normal-*-140-*-p-ll0-*

/usr/local/lib/Xll/vue/bitmaps/MYlogo.bm
#ef506f

This line in Xresources specifies the login screen greeting:
Vuelogin*greeting.labelString: This is %LocalHost%

See Also

• "To reread Login Manager configuration files" covers how to reread
Xresources.
• "To use different Login Manager resources for each display" in Chapter 13
covers using different resources for different displays.
• "To provide different resources for each node" in Chapter 13 covers setting
Login Manager resources in a diskless cluster.
• The comments in /usr/vue/config/Xresources contain more
information about login screen resources.

12-4

Customizing Login Manager

Customizing the login Screen

To customize the language menu
1. Set the languageList resource in lusr/vue/config/Xconfig:
Vuelogin*languageList: language [language

.,. ]

where language is a valid value for the LANG environment variable.
2. Reread the Login Manager configuration files.
Example

The following line in Xconfig specifies the contents of the language menu:
Vuelogin*languageList: french italian german japanese

See Also

• "To reread Login Manager configuration files" explains how to reread
Xconfig.

12-5

Customizing Login Manager Behavior

This section covers how to:
• Display a message of the day.
• Run system-wide scripts at login and logout.
• Use a different X server.

To display a message of the day
1. Create a file containing the rnessage of the day.

2. Log in as root.
3. In /usr/vue/config/Xsession, find the line that defines the variable

VUEHELLO:
VUEHELLO=$VUEDIR/vuehello

4. Modify the line to include the -file option, which takes as its parameter
the name of the file containing the message of the day:
VUEHELLO=$VUEDIR/vuehello -file path

The vuehello client displays the transition window after the user login and
password are validated, before the session manager is run.
By default, vuehello displays Starting the HP Visual User Environment
and the copyright message (I etc/ copyright) in the transition window.
The -file option specifies files containing additional messages. Up to five files
can be added; each uses a separate -file option.
Example

The following line adds the general message of the day and a user-specified
message.
VUEHELLO=$VUEDIR/vuehello -file /etc/motd -file $HOME/mymessage

12-6

Customizing Login Manager

Customizing Login Manager Behavior

See Also

• "To reread Login Manager configuration files" explains how to reread
Xsession.

To run system-wide scripts at login and logout
At login

1. Log in as root.
2. If /usr/vue/config/Xstartup does not exist, create it and make the file
executable.
3. Edit the file to contain conunands you want run.

At logout

1. If /usr/vue/config/Xreset does not exist, create it and make the file

executable.
2. Edit the file to contain conunands you want run.
Xstartup is run as root after the user has been authenticated, before the
session manager is started. Usually, Xstartup will be a shell script.

You can use Xreset to undo tasks done by Xstartup. Usually, Xreset will
be a shell script.
Environment variables
for 'Xstartup' and
'Xreset'

These environment variables are set while Xstartup and Xreset are
running:
Variable

Value

DISPLAY

Display name.

USER

Name of user logging in or out.

HOME

Home directory of the user.

PATH

Value of the systemPath resource in Xconfig.

SHELL

Value of the systemShell resource in Xconfig.

XAUTHORITY

May be set to an authority file.

Set to the current time zone.
12-7

Customizing Login Manager

Customizing Login Manager Behavior

To run a different X server
• Edit the line in /usr / vue/ conf ig/Xs ervers that starts the server.
The change takes effect the next time the user logs in. Xservers contains a
line for each server. The syntax for specifying a server is:
DisplayName DisplayClass DisplayType Command

Example

DisplayName

$DISPLAY. The display name that is passed to X programs
by the -display option. The default is hostname: o.

DisplayClass

Used in setting display-specific resources for a particular
class of displays.

DisplayType

Set to local.

Command

The command line to start the server (for local servers only).

The following entry in Xservers starts the server /usr/bin/Xii/X on
display hpcvaaa: o.
hpcvaaa:O Local local /usr/bin/X11/X :0

The hostname can be a simple host name (for example, hpcvaaa) or a fully
qualified domain name (for example, hpcvaaa. cv . hp . com).
See Also

• "Configuring X-Terminals" in Chapter 13 covers connecting to the X server
on an X terminal.
• "To reread Login Manager configuration files" explains how to reread
Xconfig.

12-8

General Login Manager Database Administration

Since Login Manager starts when the system is booted before a user has
logged in Login Manager must log errors separately from errors written during
an HP VUE session.
Login Manager configuration files must be reread in order for changes made
to Login Manager confuration files to take effect. Ordinarily, this is done
by logging out and back in, but Login Manager files can be reread within a
session.

To display Login Manager errors
• Read /usr/vue/config/Xerrors.
Xerrors records errors produced by:
• vuelogin.

• Any standard error output by Xstartup, Xsession, or Xreset.
In a diskless cluster, Xerrors is a context-dependent file.

12-9

Customizing Login Manager
General Login Manager Database Administration

To reread Login Manager configuration files
• Log out. The configuration files are reread and take effect at the next login
screen.
• Reread the files from within a session by executing (as root):
kill -HUP pid

where pid is the process ID of the parent vuelogin process.
'pid' of the parent
vuelogin

• Obtain the process ID from the file /usr/vue/config/Xpid. In a diskless
cluster, Xpid is a context-dependent file.
• Or, execute:

ps -ef I grep vuelogin

There will be two or more vuelogin processes. The parent vuelogin
process is parented (PPID column) by init (1).

12-10

This section covers:
• Default configuration
• Login Manager files.
• How (the order in which) Login Manager accomplishes its functionality.

The default Login Manager configuration
Login Manager configuration files are set up to run HP VUE on these
configurations:
• System with a single bitmap display that is also the system console.
• Diskless clusters consisting of cnodes, each with a single bitmap display
that is the system console.
See Also

•
•
•
•
•
•
•

"Configuring Character-Display Consoles" in Chapter 13
"Configuring X-Terminals" in Chapter 13.
"Configuring Diskless Clusters" in Chapter 13.
"Configuring Multiple-Displays" in Chapter 13.
"Configuring Multiple Screens" in Chapter 13.
"Running Starbase Applications" in Chapter 13.
"Partial HP VUE Environments" in Chapter 13.

12-11

Customizing Login Manager

System-wide
configuration files

The functionality of Login Manager is provided by three HP VUE clients in
/usr/vue/bin.
Client

Description

vuelogin

Performs configuration tasks and spawns another vuelogin
process for each display in the system. Thus, there will be
n+ 1 vuelogin clients running, where n is the number of
displays managed by the system.

vuegreet

Provides the functionality of the login screen.

vuehello

Provides a transition effect between successful login and
the beginning of the HP VUE session. By default, this is a
welcome message and copyright notice.

These files are located in /usr/vue/config.
File Name

Description

Xconfig

Contains the resources for the behavior of vuelogin. It
can also define new locations for the other vuelogin
configuration files.

Xservers

Contains a list of servers to be run by vuelogin.

Xresources

Contains resources for the appearance of the login screen.

Xstartup

Program (usually a shell script) that is run as root after the
user login and password is validated.

Xsession

Shell script that sets up the user environment variables,
runs vuehello, and invokes the session manager.

Xreset

Shell script that is run as root upon termination of an HP
VUE session. It can be used to return the system to its
pre-Xstartup configuration.

12-12

Customizing Login Manager

User-specific
configuration files

See Also

These files are located in the user's home directory.
File Name

Description

. Xauthori ty

Contains authorization information needed by clients that
require an authorization mechanism to connect to the server.

. vueprofile

Contains environment variables.

• The vuelogin man page.

How Login Manager starts an HP VUE session
l. The Login Manager executable (vuelogin) is started by the init process

during the system boot sequence.
2. vuelogin reads lusr/vue/config/Xconfig. Xconfig contains
resources for various login manager actions.
3. vuelogin reads the following files in lusr/vue/config:
• Xservers, or the file identified by the resource Vuelogin. servers in
the Xconf ig file .
• Xresources, or the file identified by the Vuelogin*resources
resource in the Xconf ig file.

4. The parent vuelogin starts the X server for each local display.
5. The parent vuelogin starts another vuelogin process for each managed
display.
The following steps happen for each vuelogin started by the parent
vuelogin:
l. vuelogin invokes vuegreet, which displays the login screen and handles

the user's interaction with the login screen.
2. Once the user login and password have been validated, vuelogin runs
lusr/vuel config/Xstartup if it is present.
3. vuelogin sets certain environment variables to default values.

12-13

Customizing Login Manager

4. vuelogin then runs /usr/vue/config/Xsession, which performs

several operations:
• It runs vuehello, which displays the message of the day or some other
transition effect .
• It reads $HOME/ . vueprofile, which may contain additional
environment variables or variables that override those set automatically
by vuelogin.
5. vuelogin invokes the session manager, vuesession.

When the user terminates a session, Login Manager runs Xreset if it is
present.

L---

Run parent vuelogin

Local Display

Run child
vuelogin

Foreign Display

Read :-+-7
Xresources

Run child
vuelogin

Run vuegreet

Itr- V~~~~te-rl

Run vuegreet

Run Xstartup

I
I
I
I

Run Xsession

Run vuehe 110

Read Xconfig

~ Read Xserver

Run K server

~ Read

Run
vuesession

~
Run Kreset

Run vuehe110

I
I
I

.....;-+-?

.vueprofil.

Run
vuesession

J,
Run Kreset

I
I

• "How Session Manager Works" in Chapter 15 covers how Session Manager
starts a session .
• "Default Environment Variables" in Chapter 14

12-14

Special Configurations

If your system includes any of these special configurations, you must

customize Login Manager to accommodate them:
• Character-terminal consoles.
• X terminals.
• Diskless clusters.
• Multiple displays.
• Multiple screens.
• Starbase applications.
Other special configurations include:
• Starting an HP VUE session from an X Window System startup script.
• Running the 'vuewm' Window Manager without HP VUE.
• Moving from Softbench to HP VUE.
• Using an audio server.
See Also

• "The default Login Manager configuration" in Chapter 12 describes the
configuration handled by the default Lgin Manager configuration files.

13-2

Configuring Character-Display Consoles

A character-display console is a configuration in which the console is not a
bitmap device.

To configure a character-display console if no bitmap
display is present
1. Comment out the line in /usr/vue/config/Xservers that starts the X

server.
#

Local local@console /usr/bin/X11/X :0

2. Reread the Login Manager configuration files.
See Also

• "To reread Login Manager configuration files" in Chapter 12 explains how
to reread Xconf ig.

To configure a character-display console if a bitmap
display exists
1. Edit the line in /usr/vue/config/Xservers that starts the X server to

read:

Local local@none /usr/bin/X11/X :0

2. Reread the Login Manager configuration files.
See Also

• "To reread Login Manager configuration files" in Chapter 12 explains how
to reread Xconfig.

13-3

Configuring X-Terminals

An X-terminal system consists of a display, keyboard, and mouse that
runs only the X server; clients, including HP VUE, are run on one or more
"host" systems on the networks. Output from the clients is directed to the
X-terminal display.
Wherever possible, you should use terminals that support XDMCP.

To configure terminals that support XDMCP
1. Make sure Login Manager is running on the host system.
2. Enable XDMCP on the X-terminal and direct it to contact Login Manager
on the host system.
XDMCP eX Display Manager Control Protocol) provides a mechanism by
which X-terminals can request login services from a network host. It ensures
that the X-terminal is communicating with a valid login manager, and
provides the protocol for exchanging authentication information between the
X-terminal and the host login manager.
See Also

• "To limit access by X-terminals to a host".
• Documentation for your X-terminal covers the procedure for enabling
XDMCP.

To limit access by X-terminals to a host
• Edit /usr/vue/config/Xaccess on the host. List only those X-terminals
permitted to access Login Manager.
If Xaccess is empty, any host can connect.

13-4

Special Configurations

Configuring X·Terminals

To use a workstation as an X-terminal.
• From a command line, execute:
/usr/bin/Xll/X -query hostname

The X server of the workstation acting as an X terminal must:
• Support XDMCP and the -query command-line option.
• Provide xhost permission (in / etc/X* . hosts) to the terminal host.

To configure non-XDMCP Terminals
l. Edit /usr/vue/config/Xservers to include an entry for each terminal.
The displayType of each terminal must be foreign.

2. Reread the Login Manager configuration files.
When Login Manager receives a SIGHUP, it rereads Xconfig and the
Xservers file (or the file specified by the Vuelogin. servers resource).
If it finds a new entry, vuelogin starts managing that display. If an entry
has been removed, the process associated with that entry is immediately
terminated.
Example

The following lines in Xservers directs vuelogin to manage sessions on two
non-XDMCP terminals.
ext1:0 NPD200X foreign
ext2:0 QCP-19 foreign

See Also

• "To reread Login Manager configuration files" in Chapter 12 explains how
to reread the Login Manager configuration files.

13-5

Configuring Diskless Clusters

In a diskless cluster, each cnode runs its own Login Manager (vuelogin).
However, all the cnodes share these configuration files in /usr/vue/ config:
• Xconfig.
• Xstartup and Xreset.
• Xsession.
• Xresources.

Special configuration for diskess clusters include:
• Starting the server on each node.
• Configuring Login Manager resources for each display.
• Configuring networking.

To start a server on each node
• If the cnode does not match the default configuration, you must
edit /usr /vue/ conf ig/Xservers for each cnode. Xservers is a

context-dependent file.
The default configuration assumes each of the cnodes has a single bitmap
display that is the system console.
See Also

• "To run a different X server" in Chapter 12 explains how to edit Xservers.

13-6

Special Configurations
Configuring Diskless Clusters

To provide different resources for each node
l. On the cluster server, edit /usr/vue/config/Xconfig to specify a
different resource file for the cnode. (There is only one Xconf ig file per

cluster.)
Vuelogin. DisplayName. resources: path/file

2. Create each of the resource files specified in Xconfig.
3. In each file, place the vuelogin resources for that display.
Example

The following lines in Xconf ig specify different resource files for three
cnodes.
Vuelogin.hpcvaaa_O.resources: /usr/vue/config/Xresources.hpcvaaa
Vuelogin.hpcvbbb_O.resources: /usr/vue/config/Xresources.hpcvbbb
Vuelogin.hpcvccc_O.resources: /usr/vue/config/Xresources.hpcvccc

See Also

• "To specify the display name in 'Xconfig'" explains the syntax for display
name in Xconf ig.
• "To change the login screen appearance" in Chapter 12 covers setting
resources in Xresources.

Context-dependent files
These Login Manager files in /usr/vue/config are context dependent:
• Xservers
• Xpid
• Xerrors

13-7

Special Configurations
Configuring Diskless Clusters

To configure networking for a diskless cluster
• Edit /etc/adm/inetd.sec. This file determines which systems can use
the system remotely.
See Also

• "Configuring diskless clusters for remote data access" in Chapter 22 and
"Specifying remote data on a diskless cluster" in Chapter 22 describe
configuring a diskless cluster for networking.

13-8

Configuring Multiple-Displays

This section explains how to configure Login Manager to run on systems with
two or more displays.
When a system includes multiple displays, the following configuration
requirements must be met:
• A server must be started on each display.
• No Windows mode must be configured for each display.
• It may be necessary or desirable to invoke different vuelogin resources for

each display.
• It may be necessary or desirable to use different system-wide environment
variables for each display.

To start the server on each display
• Edit /usr/vue/config/Xservers to start an X server on each display.
Syntax

The general syntax for starting the server is:
DisplayName DisplayClass DisplayType[ @ite ] Command

Only displays with an associated ITE can operate in No Windows Mode. No
Windows mode temporarily disables HP VUE for the display and runs a
getty process if one is not already started. This allows the user to log in and
perform tasks not possible under HP VUE. When the user logs out, HP VUE is
restarted for the display. If a getty is not already running on a display, Login
Manager starts one when No Windows Mode is invoked.
Default configuration

When ite is omitted, display : 0 is associated with the ITE (/ dev / console).

13-9

Special Configurations

Configuring Multiple-Displays

To specify a different
display as ITE

• On the ITE display, set ite to the character device.

Example

The following entries in Xservers start a server on three local displays on
hpcvaaa: O. Display : 0 will be the console CITE).

• On all other displays, set ite to none.

hpcvaaa:O Local local /usr/bin/X11/X :0
hpcvaaa:1 Local local /usr/bin/X11/X :1
hpcvaaa:2 Local local /usr/bin/X11/X :2

Example

On host hpcvbbb, the bitmap display : 0 is not the ITE; the ITE is associated
with device /dev/ttyi1. The following entries in Xservers start servers on
the two bitmap displays with No Windows Mode enabled on : 1.
hpcvaaa:O Local local@none /usr/bin/X11/X :0
hpcvaaa:1 Local local@ttyi1 /usr/bin/X11/X :1

See Also

• "To run a different X server" in Chapter 12 covers the syntax for starting a
server in Xservers.

To specify the display name in 'Xconfig'
You cannot use regular hostname: 0 syntax for the display name in
/usr/vue/config/Xconfig.

• Use underscore in place of the colon.
• In a fully-qualified host name, use underscores in place of the periods.
Example

Vuelogin. claaa_ 0 . resource: value
Vuelogin.hpcvaaa_prsm_ld_edu_O. resource: value

13-10

Special Configurations
Configuring Multiple·Displays

To use different Login Manager
resources for each display
1. Use the resources resource in /usr/vue/ config/Xconfig to specify a
different resource file for each display (this file will be the equivalent to
/usr/vue/config/Xresources):
Vuelogin. DisplayName. resources: path/file

2. Create each of the resource files specified in Xconfig.
3. In each file, place the vuelogin resources for that display.
Example

The following lines in Xconf ig specify different resource files for three
displays.
Vuelogin.hpcvaaa_O.resources: /usr/vue/config/XresourcesO
Vuelogin.hpcvaaa_1.resources: /usr/vue/config/Xresources1
Vuelogin.hpcvaaa_2.resources: /usr/vue/config/Xresources2

See Also

• "To change the login screen appearance" in Chapter 12 covers setting
resources in Xresources .
• "To specify the display name in 'Xconfig'" explains the syntax for display
name in Xconfig.

13-11

Special Configurations
Configuring Multiple·Displays

To run a different startup script for each display
• Use the startup resource in /usr/vue/config/Xconfig to specify a
different startup script for each display (this file will be the equivalent of
the Xstartup file):
Vuelogin*DisplayName. startup: /path/file

The startup script is run as root after the user has logged in, before the HP
VUE session is started.
The script /usr/vue/config/Xreset can be used to reverse the setting
made in Xstartup. Xreset runs when the user logs out.
Example

The following lines in Xconf ig specify different startup scripts for three
displays.
Vuelogin.hpcvaaa_O.startup: /usr/vue/config/XstartupO
Vuelogin.hpcvaaa_1.startup: /usr/vue/config/Xstartup1
Vuelogin.hpcvaaa_2.startup: /usr/vue/config/Xstartup2

See Also

• "To specify the display name in 'Xconfig'" explains the syntax for display
name in Xconfig.

13-12

Special Configurations
Configuring Multiple-Displays

To set different system-wide environment variables
for each display
• Set the environment resource in /usr/vue/ config/Xconfig separately
for each display:
Vuelogin*DisplayName*environment: value

Separate variable assignments with a space or tab.
Do not use the environment resource to set TZ and LANG.
There is no shell processing within Xconfig.
Example

The following lines in Xconf ig set variables for two displays.
Vuelogin*hpcvhere_O*environment: EDITOR=vi \
SB_DISPLAY_ADDR=OxBOOOOO
Vuelogin*hpcvhere_1*environment: EDITOR=emacs \
SB_DISPLAY_ADDR=OxBOOOOO

See Also

• For information about environment variables:
o "Setting System-Wide Environment Variables" in Chapter 14 provides
more information about system-wide variables.
o "Setting Personal Environment Variables" in Chapter 14
• "To specify the display name in 'Xconfig'" explains the syntax for display
name in Xconfig.

13-13

Configuring Multiple Screens

Both the Workspace Manager and Session Manager support multiple screens,
with certain limitations.
See Also

Configuring systems for multiple screens is covered in Using the X Window
System.

How HP VUE Supports Multiple Screens
HP VUE supports rnultiple screens in these ways:
• The Window Manager can be started on multiple screens. screen -specific
resources can be specified for Window Manager resources.
• Session Manager will save screen-related information about clients and
restore clients to their proper screens at the beginning of the next session.
Multiple screens are not supported by the following portions of HP VUE:
• Only one front panel is allowed per X server (display). It will be displayed
on the default screen, or on the screen specified in the command line that
starts Window Manager (see "Using the Window Manager with Multiple
Screens" in chapter x).
• Session Manager can run on only one screen. (However, it can save clients
running on other screens.)
• The Broadcast Message Server and Command Invoker will run only on the
screen running Session Manager. This affects cormnunication between
clients, and may produce unpredictable behavior. For example, clients
invoked from File Manager on screen 1 may display on screen O.

13-14

Special Configurations
Configuring Multiple Screens

To manage multiple screens
There are two ways to manage multiple screens.
Using window manager
resources

1. Use the vueliJIIl resource mul t iScreen to tell the Window Manager to
manage multiple screens:
VueliJIIl*multiscreen:

true

2. Use the vueliJIIl resource screenList to specify the screen names:
VueliJIIl*screenList: name

name ellipsis;

The front panel starts on the first screen listed. The new resources take effect
when the Window Manager is restarted.
Using Session Manager
resources

•

Use the Session Manager resource wmStartupcommand to specify a
command line for starting the Window Manager. Command-line options let
vuewm manage multiple displays.
D

-display specifies the display. It has the syntax:
-display hostname: display. screen

The front panel will be displayed on the screen specified by the screen
parameter.
D

-multiscreen causes the Window Manager to manage all the screens
on the specified display.
-screens specifies the screen names used to obtain screen-specific

resources.
Example

The following resources tell the Window Manager to manager two screens:
Vuewm*multiscreen: true
Vuewm*screenList: screen_O

screen_1

13-15

Special Configurations
Configuring Multiple Screens

Example

The resource:
Vuesession*wmStartupcommand: vuewm -display local:O.1 \
-multiscreen \
-screens zero one

causes vuewm to manage all the screens on display O. Screens 0 and 1 are
named zero and one. The workspace manager is displayed on screen 1
(named one).

13-16

Running Starbase Applications

If you plan to run Starbase applications in HP VUE, you need to:

• Allocate for Starbase applications.
• Set certain environment variables before the X server is started by Login
Manager.

To allocate colors to Starbase applications
1. Edit /usr/vue/config/Xsession to include a line that runs
xini tcolormap. Use the -f option to specify the file containing the

colors.
2. Create the file containing the colors to be allocated to Starbase.
Starbase applications can create their own colormap. However, if a Starbase
application uses the default colormap, then colors must be allocated to it
before an HP VUE session is run. The colors allocated to Starbase are not
available to HP VUE.
Starbase applications do not communicate with the HP VUE color server.

13-17

Special Configurations
Running Starbase Applications

To set environment variables for starbase applications
• Use Login Manager's environment resource to set SB_DISP _ADDR and
VVMS~SPCm/usr/vue/config/Xconfig.

Vuelogin*environment:

SB_DISPLAY_ADDR=value \
WMSHMSPC=value

SB_DISPLAY_ADDR and VVMSHMSPC must be set before the X server is
started. Meaningful defaults are provided for these variables.
Example

The following entry in Xconfig set the SB_DISPLAY_ADDR and
variables.
Vuelogin*environment:

13-18

SB_DISPLAY_ADDR=OxBOOOOO \
WMSHMSPC=Ox200000

\VMS~SPC

Partial HP VUE Environments

Ordinarily, the HP VUE Session Manager is invoked automatically by Login
Manager. Session Manager, in turn, automatically starts the Window Manager
and saved applications. It may be preferable in certain configurations to have
manual control over sessions.

To run an HP VUE session from an X Startup Script
1. Place the following line in the X Window System startup script:
/usr/vue/bin/vuesession -norestore

You must use the full path to vuesession, and it must be run in the
foreground.
2. Remove the line that starts a window manager from the startup script
(vuesession automatically starts vuewm).
3. Edit the script so that the only client started before vuesession is
xrdb. You must run xrdb before vuesession if vuesession requires
resources-for example, if you are using the wmStartupCommand resource
to start a different window manager.
When the session manager is started this way:
• The HP VUE Login Manager is not run.
• Session Manager does not provide the ability to save and restore sessions.
It does not run a vue. session file; the only clients that are started are the
workspace manager and clients specified in the startup script. Resources
are note loaded from vue. resources; clients get their resources from the
file loaded with xrdb in the startup script, or from system app-defaults
files.

13-19

Special Configurations

Partial HP VUE Environments

• Session Manager runs vuewm workspace manager. To run a different
window manager:
o

Use the resource wmStartupCommand to specify a different window
manager.

o Use xrdb to read in this resource prior to running vuesession.

• Session Manager runs the Broadcast Message Server.
• The user cannot log out from the front panel logout control. To stop the
server and return to a system console, press (Shift) (Ctrl ) (Reset) (( Shift) ( Ctrl )
(Pause) for HP C1429A Enhanced Vectra keyboards).
• Fonts may not be properly set for the HP VUE clients.
See Also

• "To integrate XII resource files into HP VUE" in Chapter 28.

To run 'vuewrn' without HP VUE
• Set the following resource before running the Window Manager:
Vuewm*useMessaging:

False

This allows vuewm to run without the HP VUE Broadcast Message Server.

13-20

Moving to HP VUE from Softbench

HP VUE and Softbench are both built on the same Tool Integration Platform,
which includes:
• The Broadcast Message Server (BMS).
• Sub-Process Control Daemon (SPCD).
The Tool Integration Platform includes these configuration files in
/usr/softbench/config.

softenv

Environment variables settings for processes started through
the SPCD.

softini t

Specifications used by the BMS for starting messaging tools.

softtypes/C

Filetype specifications used by the BMS with Softbench. HP
VUE does not use this file.

Installing HP VUE over Softbench
Files saved during
installation

When the BMS fileset is installed, any existing Tool
Integration Platform configuration files are saved in
/usr/softbench/oldconfig/re~ase/usr/softbench/config.

If you customized any of the configuration files, you may want to

compare your old version of the file to the new one and make any desired
modifications.
Softbench 1.0

To create a softini t file containing entries for both products:
• Execute the following command as super-user:
cat /usr/softbench/config/softinitsrc/class-defaults/vue.softinit
/usr/softbench/oldconfig/rewase/usr/softbench/config/softinit \
> /usr/softbench/config/softinit

13-21

Special Configurations
Moving to HP VUE from Softbench

• If you reinstall HP VUE 2.01 after executing this command, the merged
softinit file is saved in /usr/softbench/oldconfig, and you can
merely restore it. If you reinstall Softbench 1. after having performed this
step, you will need to rexecute the command to merge the files.

Softbench 1.1

HP VUE and Softbench 1.1 can be installed on the same system in either
order without any problems. Their softinit files are combined.

Removing Softbench
1.0

If you use the sysrm command to remove Softbench 1.0, you will also

remove the Tool Integration Platform files required by HP VUE. To recover
from this situation you must reinstall the BMS fileset from the HP VUE
distribution.

To run HP VUE if you've customized Softbench
1. Rename $HOME/ . softini t file to some other name.
2. Copy /usr/softbench/config/softinit to $HOME/ .softinit
3. Add any modifications you had previously made to $HOME/ . softini t to
your new copy.
If you have created a $HOME/ . softinit file, you must modify this file using

the following steps before running HP VUE.
Any time you modify your $HOME/ . soft ini t file, you must restart both
HP VUE and Softbench to make use of your modifications. The best way to
accomplish this is to simply log out and restart your HP VUE session .
See Also

• The Installing HP Sojtbench manual explains how to customize Softbench.

13-22

Special Configurations

Moving to HP VUE from Softbench

To quit Softbench
• To stop Softbench applications, select the application in Tool Manager
window and choose Stop from the Tool menu.

13-23

Configuring Audio Devices (HP-UX only)

Your system must meet the following configuration requirements to record
and play back audio.
• The Audio Application Program Interface (AAPI) must be installed.
• The NCS Local Location Broker Daemon (llbd) must be running on every
system that is involved with the audio operation.
• The audio server must be running.
• The TCP Daemon must be running.
The AUDIO environment variable can be set to specify the system running
the audio server. If it is not set, it defaults to the local audio server.
Saa Also

• The Audio Users Guide contains additional infonnation about configuring
and using audio.

To start the NCS Local Location Broker Daemon at
boot time
• Edit /etc/netncsrc. Change the line:

START_LLBD=O
to

START_LLBD=l

13-24

Special Config urations

Configuring Audio Devices (Hp·UX only)

To start the audio server
Manually

• Execute:
/usr/audio/bin/Aserver

At boot time

• As superuser, create an /etc/audiorc file containing these lines:
#!/bin/sh
if [ -x /usr/audio/bin/Aserver ]
then
echo "Starting Aserver"
/usr/audio/bin/Aserver
fi

• Add the following section to the localrc procedure in /etc/rc:
# start audio server
localrcO
{

# This function is intended for adding local ...

/usr/bin/slp -iO > /dev/lp

# start audio server
if [ -x /etc/audiorc ]
then
/etc/audiorc
fi
}

• Set the permissions, owner and user on these files as follows:
/usr/audio/bin/Aserver
/etc/rc
/etc/audiorc

-r-xr-xr-x
-r-xr--r-x
-r-xr--r-x

root
root
root

sys
sys
sys

13-25

Special Configurations

Configuring AlJdio Devices (Hp·UX only)

To see i¥ the audio
$~nm[ !:§

Execute:
ps -e I grep Aserver

One server (two processes) can handle multiple clients, but it is not desirable
to have more than one server running on a node.

13-26

EItYiroItroent'¥ariables

Environment Variables

HP VUE acquires environment variables from several sources.
• Certain default variables are built into Login Manager.
• System-wide environment variables can be set in Login Manager
configuration files.
• Special resouces exist for setting time zone (TZ) and language (LANG).
• Personal environment variables are set in the the user's. vueprofile file.
• The. vueprofile file can source in the user's shell environment
file. There are special requirements for doing this (see "To use a shell
environment file with' .vueprofile' ").
Precedence of Variable
Definitions

Since environment variables can be defined in a number of files, it is
necessary to understand which definition takes precedence. A later definition
overrides a previous one. For example, a definition in . vueprofile overrides
a setting in /usr/vue/ config/Xsession.

14-2

Environment Variables

Built into vue login

Resource in lusr/vue/config/Xconfig
~----------~----------~

lusr/vue/config/Xsession

$HOME!.vueprofile

System-wide variables
available to the X server
and HP VUE session.

System-wide variables
available to the
HP VUE session.

Personal variables

Personal variables have precedence over system·wide variables.

14-3

Default Environment Variables

Default environment variables are either:
• Built into Login Manager.
• Set in the script /usr/vue/config/Xsession.

Variables built into Login Manager
These variables are set separately for each display after the user login and
password have been validated.
Variable

Default Value

DISPLAY

The first field in the Xservers file.

USER

User name.

HOME

Home directory specified in / etc/pass1ii7d.

PATH

Value of the resource userPath in the
/usr/vue/ config/Xconfig file.

SHELL

The shell specified in / etc/pass1ii7d.

LANG

The display's current NLS language, if any.

LC_ALL

Set to the value of LANG.

LC_MESSAGES

Set to the value of LANG.

LOGNAME

User name.

Value of the timeZone resource in Xconfig (or in the
operating system file that sets the time zone).

XAUTHORITY

May be set to an authority file.

14-4

Environment Variables
Default Environment Variables

Variables set by 'Xsession'
The script /usr/vue/ config/Xsession is run by Login Manager after the X
server has been started. Therefore, these variables are not available to the X
server.
Variable

Default Value

EDITOR

/usr/vue/bin/vuepad

KBD_LANG

Set to the value of LANG for appropriate languages.

TERM

xterm

MAIL

/usr/mail/$USER

The Xsession script also includes a section for setting the
XVHHELPSYSTEMSEARCHPATH environment variable, which determines
which online help is found. By default, this variable is commented (not
set). However, if you are setting up a "help server," you may need to edit
Xsession. (See also "To configure access to a help server" in Chapter 4.)

14-5

Setting System-Wide Environment Variables

System-wide variables are available to all users on a system. Variables can be
set so that they are:
• Available both to the HP VUE session and to the X server.
• Available only to the HP VUE session.
In addition, in multi-display systems, the scope of the variable can be set so

that it is available to:
• All displays in a system.
• A particular display.

To set system-wide variables for X server and session
• Set the environment resource in /usr/vue/config/Xconfig:
Vuelogin*environment: variable=value ...

Separate variable assignments with a space or tab.
Do not use the environment resource to set TZ and LANG.
If the X server does not use the variable, it will be applied only to the HP

VUE session.
There is no shell processing within Xconfig. Thus, you cannot use
shell programming constructs such as variable assignments (for example,
VARIABLE=value) and conditional expressions (for example, if . .. f i).
Multiple-display
systems with different
environments

For multiple-display systems, where different environments are needed
for the displays, use this syntax for the environment resource in
/usr/vue/config/Xconfig
Vuelogin*display*environment: variable=value ...

14-6

Environment Variables

Setting System-Wide Environment Variables

If display includes a colon (:), replace it with an underscore character-for

example, hpcvhere_O.
Example

The following line in Xconf ig sets the EDITOR variable for all displays.
Vuelogin*environment: EDITOR=vi

Example

The following line in Xconfig sets the SB_DISPLAY_ADDR variable for
display hpcvxhere : 1.
Vuelogin*hpcvhere_l*environment: EDITOR=vi \
SB_DISPLAY_ADDR=OxBOOOOO

To set system-wide variables for the session only
Single-display systems

• Edit /usr/vue/config/Xsession to include variable definitions using the

syntax:
variable=value
export variable [variable

... ]

Xsession is a shell (ksh) script, so shell processing is available.
Multiple-display
systems with different
environments

If the system has multiple displays, and different session variables are needed
for the displays, use the session resource in /usr/vue/config/Xconfig to

specify a different "Xsession" file for each display:
Vuelogin*display*session: /path/jilename
If display includes a colon (:), replace it with an underscore character-for

example, hpcvhere_O.
• Create the specified files .
• Edit the files to include the variable definitions.

14-7

Environment Variables

Setting System-Wide Environment Variables

Example

The following lines in Xsession set values for the MAIL and TERM variables
and then export the variables.
MAIL=/usr/mail/$USER
TERM=xterm
export MAIL TERM

Example

The following line in Xconfig specifies the Xsession file for display
hpcvhere: 1 :
Vuelogin*hpcvhere_1.session: /usr/lib/X11/vue/Vuelogin/Xsession.hpcvhere

To set a system-wide timezone (TZ)
• Set the timeZone resource in /usr/vue/ config/Xconfig:
Vuelogin [*display] *timeZone: value
If display includes a colon (:), replace it with an underscore character-for

example, hpcvhere_ o.
The time zone will apply to all users logging in using HP VUE, and will
override any time zone value set by the operating system.
Example

The following line in Xconfig sets the time zone for all displays:
Vuelogin*timeZone: PST8PDT

You can set a personal value for TZ in . vueprofile.

14-8

Environment Variables
Setting System-Wide Environment Variables

To set a system-wide language (LANG)
• Set the language resource in /usr/vue/config/Xconfig:
Vuelogin [*display] *language: value
If display includes a colon (:), replace it with an underscore character-for

example, hpcvhere_ 0.
Example

The following line in Xconfig sets the value of LANG to swedish for display
hpcvxpae: 0:
Vuelogin*hpcvxpae_O*language: swedish

The DISPLAY environment variable
The DISPLAY environment variable sets the host, display number, and screen
number to which a system sends bitmapped output for clients.
Default value for

DISPLAY

System-wide value for

DISPLAY
Personal value for
DISPLAY

The default value of DISPLAY is set automatically by vuelogin to
hostname: 0, which is display 0, screen of the local display. If you must
change it, edit the first field of the appropriate entry in the Xservers file.

When specifying a display in /usr/vue/config/Xconfig, replace the colon
(:) with an underscore character-for example, hpcvhere_O.
DISPLAY can be set in _vueprofile.

14-9

Setting Personal Environment Variables

User-specific environment variables are set in
I HameDirectoryl. vueprofile.

When a user logs in toHP VUE/the .profile or • login file is not automatically read.
Instead" •vueprofile is read.

To set personal environment variables
• Copy the template lusr/vue/config/sys. vueprofile to
$HOME/. vueprofile. Give the new file write permission.
The. vueprofile file should contain only variable settings; it should not
contain shell commands that require terminal I/O or commands that run in
the foreground.
If you want the file interpreted according to a shell other than the default
shell, specify the shell for the file by placing #! Ibinl sh, #! Ibinl csh, or
#! Ibin/ksh at the top of the file. (HP VUE supports these three shells; it

does not support other shells.)

14-10

Environment Variables

Setting Personal Environment Variables

Example

The following line in . vueprof ile sets the value for the MAILPATH
en vironment variable:
MAILPATH="${MAIL}?You have new mail."

To use a shell environment file with' .vueprofile'
l. Place variables and shell commands in . vueprofile that apply only to

HP VUE.
2. Add lines to the end of . vueprofile to source in the shell environment
file.
3. Edit the shell environment file to provide two sections:
• One section contains commands that do not apply to HP VUE (for
example, commands that require terminal 110, or variables for which you
want to replicate the HP VUE default values).
• The other section contains variables that apply, whether or not HP
VUE is run-for example, when logging into the system from a remote
system.
If you have an existing shell environment file (. profile or . login), this

procedure lets you continue to use that file. This avoids duplicate variable
assigments between. vueprofile and the shell environment file.
If a terminal emulator is started with the -Is option, . login or .profile

will be read automatically.

14-11

Environment Variables

Setting Personal Environment Veriables

Example (ksh)

The following lines at the end of . vueprof ile sources in . prof ile:
VUE=true; export VUE
. $HOME/.profile
unset VUE

The following sample .profile shows how to separate it into a non-HP VUE
section and a section for variables that apply both to HP VUE and non-HP
VUE environments.
if [ ! "$VUE" ]; then
stty options
tset options
DISPLAY=value
MAIL=value

export DISPLAY MAIL
Additional shell commands that do not apply to HP VUE
Additional variable assignments that do not apply to HP VUE

fi
PATH=value
Assignments jar common variables

Example (csh)

The following line at the end of . vueprofile sources in . login:
setenv VUE true
source $HOME/.login

The following sample . login shows how to separate it into a non-HP VUE
section and a section for variables that apply both to HP VUE and non -HP
VUE environments.
if ( ! "$VUE" ) then

s tty options
tset options
setenv DISPLAY value
set mail = value
Additional shell commands that do not apply to HP VUE
Additional variable assignments that do not apply to HP VUE

endif
setenv PATH value
Assignments jor common variables

14-12

Administering .HPVUE
Sessions'

Administering HP VUE Sessions

Session Manager provides the ability to save and restore sessions.
Regular HP VUE
sessions

These things, characteristic of a particular session, are saved and restored by
Session Manager:
• Which applications are running.
• What application windows look like (colors, fonts, size, location, etc.).
• Other settings controlled by the X server, such as mouse behavior, audio
volume, and keyboard click.
Session Manager also lets you:
• Run a customized shell script after the user logs in.
• Change the window manager.
• Change the fail-safe session.

HP VUE Lite sessions

HP VUE Lite provides an alternative to the full HP VUE environment. HP
VUE Lite sessions are managed separately from regular sessions.

See Also

• "Administering HP VUE Lite Sessions" in Chapter 23 describes how to

configure HP VUE lite sessions.
• "Providing Networked Sessions" in Chapter 22 covers distributing an HP
VUE session among multiple systems.
• "Session Management (HP VUE 2.01 to HP VUE 3.0)" in Chapter 28
covers the differences between the HP VUE 3.0 and HP VUE 2.01 Session
Managers.

15-2

How Session Manager Works

Session Manager is responsible for loading the appropriate resources, restoring
server settings, and starting the clients.
Session Manager is implemented by the client /usr/vue/bin/vuesession.

Types of HP VUE sessions
Sessions are divided into these categories:
• Current sessions. A current session is stored at logout, providing the user
with the ability to "start where he left off."
• Home sessions. The home session is explicitly stored by the user at some
other time during a session, allowing the user to always return to some
"known" session.

Location of Session Data
Files

Session information is stored under the following file names.
vue.session

The names of active clients, their window geometries,
their workspace presence status (which workspaces
they are in, their state (normalized or minimized), and
startup string.

vue.resources

The resources for the active clients (including the
Workspace Manager) in the session.

vue.settings

Server settings and session manager settings, such as
screen saver timeout, audio (bell) settings, and keyboard
repeat settings.
15-3

Administering HP VUE Sessions
How Session Manager Works

SesSiQnif¥1aQageruses .sPElciaf~yntax. vvheQwritingtovu~ • s ess ion. and vll.;e. settings.
You should·· (lot edit these files.
' .

Directories

Back-up sessions

The location of the session files depends on the session type.
current

/ HorneDirectory/. vue/sessions/current

home

/ HorneDirectory/. vue/sessions/home

HP VUE lite

/ HorneDirectory/ . vue/lite

Back-up

/ HorneDirectory/. vue/sessions/current. old
/ HorneDirectory/ . vue/sessions/home. old

When the current session is saved at logout, the old session files are saved to
a current. old directory. Similarly, when the user saves a home session,
the previous home session is saved to home. old. If a session directory is
lost, you can copy a back-up sessions. For example, the following command,
executed from the / HorneDirectory/ . vue/sessions directory, restores a
back-up session:
cp -r current.old

Display-dependent
sessions

current

HP VUE 2.01 saved and restored display-dependent sessions. Displaydependent sessions are stored in directories in which sessions is replaced
by the display name. For example, /users/ dm/ . vue/hpkbdc: 0/ current
stores the display-dependent current session for user dm on display
hpkbdc: O. In HP VUE 3.0, display-dependent sessions have precedence over
display-independent sessions; therefore, HP VUE 3.0 will continue to use a
display-dependent session if it exists.

15-4

Administering HP VUE Sessions
How Session Manager Works

How Session Manager chooses the session to use
When Session Manager starts a regular session, it searches for the existence
of a session directory and uses the first session it finds.
Order of search

/ HomeDirectory/ . vue/display/current
/ HomeDirectory/ . vue/ display/home
/ HomeDirectory/. vue/sessions/current
/ HomeDirectory/. vue/sessions/home
/usr/vue/config

Home sessions

Display-dependent current
session.
Display -dependent home
session.
Display-independent current
session.
Display-independent home
session.
Default session.

There are two user interactions involving home sessions:
• When the user saves a home session using the Startup dialog
box in the Style manager, the state of the session is stored
in the / HomeDirectory/ . vue/sessions/home directory (or
/ HomeDirectory/ . vue/display/sessions/home for display-dependent
sessions).
• If the user has selected Return to Home session in the Startup dialog box,

the current directory is removed at logout.

15-5

Administering HP VUE Sessions
How Session Manager Works

The First HP VUE Session
login

When a user logs into HP VUE for the first time, Session Manager uses
the default session files in the /usr/vue/config: sys. session and
sys.resources.

logout

When the user logs out, the state of the session is saved to the
/ HomeDirectory/ . vue/sessions/ current This session is retrieved the next
time the user logs in.

Previous HP VUE 2.01
users

The first time the user logs into HP VUE 3.0, the previous HP VUE
2.01 session is restored. At logout, the session is stored to the same
display-dependent directory. You can continue to use the HP VUE 2.01
session files, which are display-dependent. However, you may find it easier to
transfer your session management to display-independent directories.

See Also

"Session Management (HP VUE 2.01 to HP VUE 3.0)" in Chapter 28 covers
the differences between the HP VUE 2.01 and 3.0 Session Managers and
how to make your sessions display-independent.
• "Administering HP VUE Lite Sessions" in Chapter 23 covers how HP VUE
Lite sessions are started.
•

15-6

Customizing Sessions

There are several ways to customize a session:
• Creating a customized first session and distributing it to other systems.
• Running a script.
• Starting a different window manager.
• Creating display-dependent sessions.
See Also

• "Providing Networked Sessions" in Chapter 22 describes how to distribute
a session to other systems.

To create a customized first session
1. Log in to obtain the HP VUE 3.0 default session.
2. Set up the session. Start the clients you want in your session, and set the
appearance and behavior you want with Style Manager or resources.
3. Log out. This creates a directory / HorneDirectory/ . vue/sessions and
session files in that directory containing the actual session information.
4. Copy the newly-created directory to other systems whose first session
you want to customize. Since sessions are saved in a display-independent
syntax, you can copy sessions to displays of different resolutions.
5. Remove any display-dependent session directories (directories named
/ HorneDirectory/ . vue/ displayname) from the other systems.

15-7

Administering HP VUE Sessions
Customizing Sessions

To execute additional commands at session startup
1. Create the shell script file / HameDirectory/. vue/sessions/sessionetc.
(Replace sessions with display for display-dependent sessions.) Make the

file executable.
2. Add a line for each process.
If the file sessionetc exists, it is executed each time the user logs into a

regular HP VUE session.
Use sessionetc to execute additional commands at session startup; for
example:
• To execute X commands for processes or settings that are not saved by
Session Manager. For example, you might want to use xsetroot to
customize the root (workspace) pointer.
• To start X clients (applications) that are not saved by Session Manager. (An
application cannot be saved and restored by Session Manager if it does not
set the WM_ COMMAND property.)

NOTE
Processes started by sessionetc must be run in the background.

00 not use $essionetc to start clients that are automatically.restored. Doing so causes multiple
copies of the application to be started; you. may not be able to seethe copies immediately because
the windows.are stack~don top of one another.

15-8

Administering HP VUE Sessions
Customizing Sessions

The following line customizes the root cursor:
xsetroot -cursor /users/anna/point /users/anna/mask -fg blue -bg red &

To use a different window manager
1. Set the liirIIlStartupCommand resource:
vuesession*liirIIlStartupCommand:

execution_string

where execution_string is the command to start a different window
manager.
2. Log out and back in.
In the default configuration, the HP VUE Workspace Manager (vuewm is
automatically started by Session Manager. The wmStartupCommand cancels

the default behavior and executes the specified command instead.
The following line starts mwm:
vuesession*wmStartupCommand:

/usr/bin/X11/mwm

To create a display-dependent session
1. Log in and out of at least one HP VUE 3.0 session. This will create session
files in / HomeDirectory/ . vue/sessions.
2. Copy / HomeDirectory/. vue/sessions to one or more display-dependent
directories / HomeDirectory/ . vue/ display.

Create a display-dependent directory if you want to run different sessions on
different displays. The display directory name must be the real, unqualified
host name (for example, hpabcd: 0 is valid; hpabcd. cv . com: 0 or local: 0

15-9

Administering HP VUE Sessions
Customizing Sessions

are not). If the display name exceeds 14 characters, truncate the name
starting with the last character.
Example

The following command creates a display-dependent session for display
hpcvxdm:O:
cp -r / HomeDirectory/ . vue/ sessions

/ HomeDirectory/ . vue/hpcvxdm: 0

The display -dependent session will be used on all subsequent sessions on
display hpcvxdm: O.
See Also

• "Session Management (HP VUE 2.01 to HP VUE 3.0)" in Chapter 28
describes the differences between HP VUE 2.01 and HP VUE 3.0 sessions
and how to create a display-independent session.

To customize the fail-safe session
• Edit /usr/vue/config/Xfailsafe. You can insert commands between
the line that starts mwm and the the line that starts the Terminal Emulator.
The commands you insert must be run in the background.

$XDIR/mwm

sleep $DELAY
new_command $XDIR/hpterm -Is
The Terminal Emulator hpt erm is run in the foreground. The script
terminates and the fail-safe session ends when the user exits the Terminal
Emulator window.
The fail-safe session is useful for correcting problems in Login Manager and
Session Manager configuration files that prevent an HP VUE session from
starting properly.

15-10

Restoring Remote Applications

Applications running on remote systems will be restored by Session Manager
if either of the following conditions are met.

• The local and remote systems are configured properly to use actions to run
remote applications. This allows Session Manager to use the SPCD to start
the remote application.
• Or, the local host can access the application using remsh. For this to

happen, both of these conditions must be met:
D

The remote system lists the local system in its / HomeDirectory/ . rhosts
file.

The local system permits the remote system to use its display. This is
done in the local system's / etc/X* . hosts file.

An application started during a session may not be restarted at the next
session if:
• The xhost permission was acquired using the xhost command prior to
running the application. The xhost permission must be supplied by the
/ etc/X* . hosts file.
• The application was started by logging into the remote system (using
telnet or rlogin). The local host may not have .rhost permission on
the remote host.
See Also

• "Using Actions to Run Remote Applications" in Chapter 22

15-11

Administering HP VUE Sessions
Restoring Remote Applications

Working with Icons
and Backdrop Images

Icons and backdrop images are an important part of the visual appearance of
your HP VUE display. Icons are associated with actions and filetypes, Front
Panel controls, and minimized application windows to make them easier to
identify.
A unique backdrop can be displayed in each HP VUE workspace (behind all
other windows). Images used for backdrops are typically larger than icons,
however, the same formats are used in the image files. You select backdrops
using Style Manager's Backdrop dialog.

16-2

Working with Icons
and Backdrop Images

Introducing
Icon Editor

The HP VUE Icon Editor is a simple tool for creating image files for use as
icons or backdrops. It supports both image formats (bitmap and pixmap) used
for icons and backdrops.

See Also

• "Icon Design Recommendations"

16-3

Getting Started with Icon Editor

Icon Editor lets you create and edit images in two formats:
• X pixmap (XPM jorrnat)-multicolor images that include static and

dynamic colors. Pixmap files are normally identified by a . pm file name
extension.
• X bitmap (XBM jormat)-two-color images limited to a foreground and

background color. Bitmap files are normally identified by a . bm file name
extension.
You draw images by selecting a tool and a color, then drawing in the work
area. As you draw, Icon Editor displays an actual-size copy of your icon in
both formats. Even if you are drawing an image for use on color systems, you
should consider the two-color version since icons may revert to two colors if
there are not enough free colors to display in full color.

To start Icon Editor
• Open your Personal Toolbox, then execute the IconEditor action.
Icon Editor starts with an empty drawing area.
Other Ways to
Start Icon Editor

You can also start Icon Editor with an icon already loaded:
• Using File Manager, locate the icon file and open it. (The default action for
pixmap and bitmap files runs Icon Editor and loads the file.)
• Or, drop an icon file on the IconEditor action in your Personal Toolbox.
• Or, if you are using HP VUE Lite, enter this command in a Terminal

Emulator window:
vueicon -f filename &

16-4

Working with Icons
and Backdrop Images
Getting Started with Icon Editor

To draw an image
l. Select a drawing tool (such as the pencil, circle, or line).

2. Select a color (static color, static gray, or a dynamic color).
3. Begin drawing with the tool you've selected.
Summary
of Tools

• Pencil-for drawing free-hand lines and individual pixels.
Click to draw individual pixels.
Press and hold to draw free-hand lines.
• Line-for drawing straight lines.
Press and hold to stretch the line. Release to draw the line.
• Rectangle-for drawing solid or outlined rectangles.
Press and hold to stretch ouline of rectangle. Release to draw the
rectangle.
• Circle-for drawing solid or outlined circles.
Point to center of circle, press and hold, drag to desired size, release.
• Eraser-for erasing large areas of the image.
Press and hold, then drag over area to erase.
To erase individual pixels, select the Pencil tool and the Transparent
color.
• Flood-for flooding a region of one color with the selected color.
Click any pixel within the region to be flooded. The selected pixel, and
all adjacent pixels, are recolored with the selected color. The filled region
extends in all directions, bounded only by pixels of different color.
• Open Polygon-for drawing connected straight lines.
Click the starting point, then click for each segment.
Double-click to end the last segment.
• Closed Polygon-for drawing connected straight lines, where the first line
and last line are connected to form a closed polygon.
Click starting point, then click for each segment.
Double-click to end last segment.
• Ellipse-for drawing solid or outlined ellipses.
Press and hold, drag to desired size and shape, release.
• Selection-for making a primary selection. Several commands in the Edit
menu require a primary selection first.
Point to corner pixel of the region to be selected, press and hold, drag to
desired region, release.

16-5

Working with Icons
and Backdrop Images

Getting Started with Icon Editor

To undo a drawing operation
• Choose Undo from the Edit menu.
Only the single most recent change can be undone.

To open an existing icon
1. Choose Open from the File menu.
If you have unsaved changes, Icon Editor warns you that your changes

will be lost by loading another icon. Choose Cancel to cancel the Open
command. Choose OK if you want to lose your changes.
2. Enter or select the icon file you want to load.
3. Choose OK.

16-6

Working with Icons
and Backdrop Images

Getting Started with Icon Editor

To save the icon
1. Choose an output format from the Options menu:
• XBM for two-color X bitmap format.
• XPM for multicolor X pixmap format (the default).
2. Choose Save from the File menu. (If the icon is unnamed or you choose
Save As, Icon Editor prompts you for a file name. Enter the name then
choose OK.)
See Also

• "Where to put icon files"
• "Where to put backdrop image files"
• "How Image Files are Found"

To save the icon with a new name
1. Choose Save As from the File menu.
2. Enter (or select) the file name you want to save as.
3. Choose OK.

To start a new icon
1. Choose New from the File menu.
If you have unsaved changes, Icon Editor warns you that your changes

will be lost by starting a new icon. Choose Cancel to cancel the New
command. Choose OK if you want to lose your changes.
2. Enter the width and height of the new icon you want to create.

16-7

Working with Icons
and Backdrop Images

Getting Started with Icon Editor

3. Choose OK.
Icon Editor clears the work area and resizes it to the size you specified. The
maximum size for an icon is 256 x 256.
If you want to start a new icon of the current size, choose Clear Icon from the

Edit menu.

To resize the current icon
1. Choose Resize Icon from the Edit menu. Icon Editor displays a dialog,

prompting for the new size.
2. Edit the current width and height to specify the new size.
3. Choose OK.

16-8

Manipulating Images within Icon Editor

After you become familiar with the basic drawing facilities in Icon Editor, you
may be anxious to try some more advanced operations.
Many of these operations require you to first select an area of the icon. This
is done using the Selection tool (next to the eraser). When an area of the icon
is selected, you can:
• Copy or move it.
• Scale (resize) it.
• Flip it (horizontally or vertically).
• Rotate it (right or left).

To select an area of the icon
1. Select the Selection tool (next to the eraser).

2. Drag a box around the area you want to select.
When an area is selected, a box flashes around the selected area.

To copy a region of the icon
1. Using the Selection tool, select the area of the icon you want to copy.
2. Choose Copy from the Edit menu.
3. Choose Paste from the Edit menu.
4. Position the outline where you want to paste the copy, then click.

16-9

Working with Icons
and Backdrop Images

Manipulating Images within Icon Editor

You may repeat steps 3 and 4 as many times as you like to paste multiple
copies of the region you copied.

To cut a region of the icon
1. Using the Selection tool, select the area of the icon you want to cut.

2. Choose Cut from the Edit menu.
When you cut a portion of an icon, the exposed area becomes "transparent"
(that is, it is filled in with the Transparent color).
After cutting a region, you can paste it back into the image using the Paste
command in the Edit menu.

To move a region of the icon
1. Using the Selection tool, select the area of the icon you want to move.

2. Choose Cut from the Edit menu.
3. Choose Paste from the Edit menu.
4. Position the outline where you want to paste the copy, then click.
You may repeat steps 4 and 5 as many times as you like to paste multiple
copies of the region you cut.

16-10

Working with Icons
and Backdrop Images

Manipulating Images within Icon Editor

To resize (scale) a region of the icon
1. Using the Selection tool, select the area of the icon you want to resize.
2. Choose Scale from the Edit menu.
3. Drag a box that defines the size and shape that you want the scaled image

to be. This determines how the selected portion oj the image will be
scaled, it does not determine where to place the results.
4. Position the outline where you want to paste the scaled copy, then click.

To rotate part of the icon
1. Select the Selection tool (next to the eraser).

2. Drag a box around the region of the icon that you want to rotate. This
"selects" the region.
3. Choose Rotate ~Left or Rotate ~Right from the Edit menu.
4. Position the outline where you want to paste the rotated area, then click.

To flip (mirror) part of the icon
1. Using the Selection tool, select the area of the icon you want to flip.
2. Choose

Flip~Vertical

Flip~Horizontal

from the Edit menu.

Flipping an area creates a pixel-for-pixel mirror image of the selected area.

16-11

Working with Icons
and Backdrop Images
Manipulating Images within Icon Editor

To add a hotspot
1. Choose Add Hotspot from the Edit menu.

2. Click the pixel where you want the hotspot.
Bitmap images (XBM format) can be used as special mouse pointer shapes.
The hotspot marks a single pixel that is the true "point" of the pointer.
To remove the current hotspot, choose Delete Hotspot from the Edit menu.

To capture (grab) a region of the display
1. Save your current icon, if necessary.

2. Choose Grab Screen hnage from the Edit menu.
3. Drag a box around the portion of the display you want to capture (press,
drag, release).

16-12

How Image Files are Found

Each icon and backdrop image is stored as a separate file. Typically, an icon
is specified with just the base part of its file name. For example, an icon
might be referenced with just the name mail when the file is actually stored
as:
/usr/vue/icons/Color/mail.m.pm

The file naming convention of adding suffixes helps group icons by size
and type. For HP VUE components, many icon names are in these general
formats:

basename. size .format
basename .format
where basename is the image name used to reference the image, size is 1 (for
large), m (for medium), or 8 (for small), and format is pm for X pixmaps or bm
for X bitmaps.
For example, suppose you specify an icon named "mail" for a filetype
you've written. If you have a color display and have set the File Manager
preferences to use "small" icons, the assumed icon name is "mail. 8. pm" (the
"8" represents small, and "pm" is for pixmap, the color icon format).

16-13

Working with Icons
and Backdrop Images
How Image Files are Found

Search Paths

The directory where an image is stored is detenuined by searching for the file
in a list of directories. The first match completes the search. By default, HP
VUE components look in these directories:
/ HomeDirectory/ . vue/icons/ application/Col or/
/ HomeDirectory/ . vue/icons/ application/
/HomeDirectory/.vue/icons/Color/
/ HomeDirectory/ . vue/ icons/
/usr /vue/ icons/ country/ application/ Color /
/usr /vue/ icons/ country/ application/
/usr/vue/icons/country/Color/
/usr /vue/ icons/ country/
/usr/vue/icons/Color/
/usr/vue/icons/Color/
/usr/vue/icons/
If you are using a color display, the search paths look for files ending in . pm.

Otherwise, the search path looks for files ending in . bm.
If an image is specified with a complete path name, the search path is not

used.

16-14

Working with Icons
and Backdrop Images
How Image Files are Found

Where to put icon files
For Personal Use

• If the icon is intended for color displays (XPM format), store the file as
/ HomeDirectory/ . vue/icons/Color/jilename. pm.

• Otherwise, store the file as /HomeDirectory/ .vue/icons/jilename.bm.
For Public Use

• If the icon is intended for color displays (XPM format), store the file as

/usr/vue/icons/Color/country/jiiename.pm.
• Otherwise, store the file as /usr/vue/icons/country/jiiename. bm.
The country/ subdirectory is optional. However, if it's used, it must match
the country portion of the user's LANG environment variable.

' , '

.(.(

'(()~ .m4Srhe~:sUp'erl.l~erto:placen.e\IVfilesjnto.the··/usrlvU:elq.¢ons/:directory(orany of. its
·~uMirect9rjesh <.

16-15

Working with Icons
and Backdrop Images
How Image Files are Found

Where to put backdrop image files
Each backdrop listed in Style Manager's Backdrop dialog represents an image
file. By default, Style Manager looks in /usr/vue/icons/Vuebackdrops/
and /usr/vue/icons/Vuebackdrops/Color/ for backdrops. To override
these locations, you must set the Vuestyle*backdropDirectory resource.
For Personal Use

• Create a custom backdrop directory, add the new image to the new
directory, then set the Vuestyle*backdropDirectory resource.

For Public Use

• If the backdrop is intended for color displays (XPM format), store the file as

/usr/vue/icons/Vuebackdrops/Color/filename.pm.

• Otherwise, store the file as
lusr Ivue/ icons/Vue backdrops/filename. bm.

See Also

• "To customize backdrops" in Chapter 24 describes in more detail how to set
up a personal backdrop directory.

16-16

Making Icon Associations

By associathlg an icon with a particular object you make it easier to recognize.
You can associate icons with:
• Actions and filetypes
• Controls in the Front Panel and subpanels
• Minimized application windows
Specifying
Icon Files

For icons used for actions, filetypes, and in the Front Panel or subpanels,
specify only the basename of the icon (no extensions). The correct extensions
are added automatically based on your display resolution, color support, and
File Manager preferences (such as "use small icons").
For minimized window icons, specify the entire icon name, including
extensions.
For any icon, you can also provide the complete path and name of the icon to
override the search path.

To associate an icon with an action or filetype
• Specify a large icon with the L- ICON keyword.
• Specify a small icon with the S- ICON keyword.
If you follow the appropriate naming conventions for icon files, you can

specify only the base name of the icon. The correct icon will be displayed
based on the resolution and color support of your display.

16-17

Working with Icons
and Backdrop Images
Making Icon Associations

Example:
Action Icons

The following example is an action definition for starting Island Paint (a
drawing tool). The icons Ipaint.1 and Ipaint . s are associated with the
action.
ACTION
WINDOW-TYPE
L-ICON
S-ICON
EXEC-HOST
EXEC-STRING
END

I slandPaintOpenDoc
NO-STDIO
Ipaint.l
Ipaint.s
machine2
/usr/bin/IslandPaint $(File)Arg_1"File to open:"%

If you are using color icons, HP VUE first appends. pm when looking for

the actual icon files. Otherwise (or if no match is found with . pm), HP VUE
appends . bm.
Example:
Filetype Icons

The following filetype definition associates the icons comprsd.1 and
comprsd. s with compressed files:
FILETYPE COMPRESSED
FILE-PATTERN
MODE
L-ICON
S-ICON
ACTIONS
DESCRIPTION
END

See Also

• Chapter 19

16-18

*.z
!d

comprsd.l
comprsd.s
Uncompress
A COMPRESSED file has been compressed by the \
'compress' command to take up less space.

Working with Icons
and Backdrop Images

Making Icon Associations

To display an icon in a Front Panel control
• Specify the image name using the IMAGE field.
• If the control is a monitor _f il e type control, use the ALT _IMAGE field

to specify the image displayed when the file is not empty. For the mail
control, use ALT_IMAGE to specify the image used when the file gets larger.
You can also provide animation for buttons and drop zone controls.
Example

The following control changes appearance when a file named report
is placed in the / doc/ftp/pub/ directory. When the file is not there,
the NoReport. pm icon is displayed; when the file is there, Report. pm is
displayed.
CONTROL MonitorReport
{

TYPE
MONITOR_FILE
IMAGE
ALTERNATE_IMAGE

monitor_file
/doc/ftp/pub/report
NoReport.pm
Report.pm

}

See Also

• Chapter 17 provides the details for modifying Front Panel controls.
• "To animate a button" in Chapter 17

16-19

Working with Icons
and Backdrop Images
Making Icon Associations

To associate an icon with an application window
1. Set the clientlcon resource for Workspace Manager as follows:

Vuewm*ClientName*clientlcon:

IconFilename

2. Restart Workspace Manager. (Choose Restart Workspace Manager from the
Workspace Menu, then choose OK.)
The HP VUE Workspace Manager and the OSFlMotif Window Manager allow
only X bitmap images (XBM format) for window icons. So, IconFilename must
refer to an X bitmap image, not a multicolor X pixmap.
To determine the correct value for ClientName, execute the ListWinProps
action in the "Unsupported" directory of the General Toolbox. When you
select a window, its properties are listed. The WM_ CLASS property displays
the window's class name in quotes.
To verify that the icon has been recognized by Workspace Manager, minimize
the window whose icon you are trying to modify.

See Also

• Chapter 25 describes how to set X resources.

16-20

Working with Icons
and Backdrop Images
Making Icon Associations

To use File Manager as an icon browser
1. Copy the file /usr /vue/ examples/lconBro1iJse. vf into your
/ HomeDirectory/ . vue/types/ directory.

2. Reload the action database by executing the ReloadActions action in the
System_Admin toolbox within the General Toolbox.
When you change to a directory that contains icons ( . bm and . pm files),
each icon is displayed next to its name. For example, if you change to the
/usr/vue/icons/ directory, you'll see many of the HP VUE icons.

'--'

• WbeFl youenahle.icop bro\Ns;in~, FHe 'Mariager mustdoadotmore work to. display each

directory.
Onlo\iV rnemorvsyst~~s J,~ism~' cau~eAelays indjsplaYi~g;sprp~.9irectodes .•••';, ....'. ... .• i.: . . ;. . . . ".~,'
";.lmag~s.la[Qef. .than 256><~5:6.aFenot.~ispJayepit~thedeJ~ult;p;onliQuration('(Youcan'qvenid~;this,':
.defauJtJilnit.usjl)~tne;iI);st;al:ic;~~:<:;~I);I{~'*gltt.·and:~lUf;:t~ce~G9gW:~d:tlti~s;ciO,f~es;t
'::"~'~~:":'
~ ~'.<:
'" ,~~.,\,,, ~ p',~l:r:~~'
<~;;" ~ ~'. :'; :<,.~,,' ':,'><,,,',
;, <'~
, "'":-\', ~

0',

' ,:'~::<'~<

' ";-- ,'~>v': ,:,I:~"

',";

'.:;"

To disable icon browsing, remove your personal copy of the IconBro1iJse. vf
file, then load the action database again.
See Also

• Chapter 19

16-21

Icon Design Recommendations

Try to use a cornmon theme among related icons. For example, if you are
designing icons for an application, have purposeful similarities between the
application's icon and icons for data files.
Be sure the two-color version of any color icon you design is acceptable.
If the icon is displayed on a monochrome or grayscale display (or if there

are not enough colors available), the icon is automatically displayed in its
two-color form.

Color Usage
Icons used in HP VUE use a palette of 22 colors:
• Eight static grays.
• Eight static colors: red, blue, green, cyan, magenta, yellow, black, and
white.
• Six dynamic colors: foreground, background, top shadow, bottom shadow,
select, and transparent.
This palette is rich enough to create attractive, easy-to-read icons without
overtaking many color resources that may be needed by other applications.
Most icons provided with HP VUE use mostly grays with color for accent.
The dynamic colors are useful for icons that change color as different color
palettes are selected in Style Manager.
The transparent color is useful for creating icons that have the illusion of
being non-rectangular, since it allows the color behind the icon to show
through.

16-22

Working with Icons
and Backdrop Images
Icon Design Recommendations

Icon Size Recommendations
Following are the recommended sizes-in pixels, widthxheight-for creating
new icons.
File Icons:
Small: 18x 22
Large: 28 x 38
Directory Icons:
Small: 22x 18
Large: 38 x 28
Executable Icons:
Small: 22x 22
Large: 38 x 38
Minimized Application Windows:
50x50
Front Panel, High Resolution (l280x 1024 Screens):
Top row controls: 56x64
Bottom row controls: 22x52
Front Panel, Medium Resolution (l024x768 Screens):
Top row controls: 42 x 48
Bottom row controls: 17 x 42
Front Panel, Low Resolution (640x480 Screens):
Top row controls: 34 x 40
Bottom row controls: 13x34
Backdrop images can be any size. The pattern is repeated to fill the entire
workspace.

16-23

Working with Icons
and Backdrop Images
Icon Design Recommendations

Customizing the Front Panel

There are a number of ways you can customize the Front Panel:
• Adding and deleting controls in the top and bottom row.
• Adding and deleting subpanels.
• Adding and deleting controls in subpanels.
You can also change the number of rows. In networked environments, you
can distribute all or portions of a customized Front Panel to other users on
the same system or other systems.
See Also

• Chapter 18 covers configuring the Terminal Emulator, Mail, Editor, and
Printer controls.
• "Customizing HP VUE Lite Terminal Emulators" in Chapter 23 and "Mding
Applications and Utilities to HP VUE Lite" in Chapter 23 covers configuring
the controls unique to HP VUE Lite.

17-2

Modifying the Front Panel: An Introduction

The Front Panel is defined in a set of files:
• The top and bottom rows are defined in the Workspace Manager
configuration file:
o System file: /usr/vue/ config/sys. vuewmrc.
o Personal file: / HomeDirectory/. vue/vuewmrc.

• Each subpanel is defined it its own file.

To create a personal Workspace Manager configuration
file ('vuewmrc')
The Workspace Manager configuration file defines the structure of the Front
Panel.
Using ListVuewmrc

• Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This creates the personal Workspace Manager
configuration file (I HomeDirectory/ . vue/vuewmrc) and opens it for
editing. ListVuewrnrc uses the editor defined by the EDITOR environment
variable.
EditVuewrnrc checks to see if / HomeDirectory/ . vue/vuewmrc exists:
• If the file does not exist, it is created by copying

/usr/vue/config/sys. vuewmrc. The new file is given write
permission as is then opened for editing.
• If the file already exists, the existing file is opened for editing.

17-3

Customizing the Front Panel
Modifying the Front Panel: An Introduction

Manually creating the
file

• Copy /usr/vue/config/sys. vuewmrc to
/ HomeDirectory/ . vue/vuewmrc. Give the new file write
permission.
If a personal Workspace Manager configuration files does not exist, the system

file is used.
Previous HP VUE 2.01
users

If you used a personalize HP VUE 2.01 front panel,
/ HomeDirectory/ . vue/vuewmrc will be present. You can convert
this file to HP VUE 3.0 syntax or remove the file.

See Also

• "Moving an HP VUE 2.01 Front Panel to HP VUE 3.0" in Chapter 28 covers

converting an HP VUE 2.01 Front Panel to HP VUE 3.0.

How the Front Panel definition is organized
The Front Panel is defined as a set of constructs-panel, boxes, and controls.
The Front Panel definition uses these constructs to build the panel from the
outside in.
• The Front Panel, or "panel," is built from a set of boxes (rows).
• Each box is a container for a set of controls.
Panel definitions

There are two Front Panels defined in the Workspace Manager configuration
file. To find the one you want, search for:
PANEL jronLpaneLname
{

}

where front-paneL name is:
Name

Description

FrontPanel

Front Panel for regular HP VUE sessions.

LiteFrontPanel

HP VUE lite front panel.

17-4

Customizing the Front Panel

Modifying the Front Panel: An Introduction

The panel contains a set of boxes, one for each row.
Row definitions

Each row is a box containing a list of controls. To find the row you want,
search for:

CONTROL controLnarne
}

where box_name is:

Control definitions

Top

Top row of Front Panel for regular sessions.

Bottom

Bottom row for Front Panel for regular sessions.

LiteTop

Top row of HP VUE Lite Front Panel.

LiteBottom

Bottom row of HP VUE Lite Front Panel.

Controls contain a list of fields that describe the appearance and behavior of
the control.
CONTROL controLnarne
{

field
}

The controLname is the same in the row (BOX) definition and the control
definition. You can use the row definition as an "index" of control names to
help you find the control you want to edit.
Top-row controls have
subpanels

A subpanel is attached to a control on the top row by the control's
SUBPANEL field:
CONTROL controLnarne
{

SUBPANEL

subpaneLnarne

}

17-5

Customizing the Front Panel
Modifying the Front Panel: An Introduction

Subpanel files are
Each subpanel, and the controls it contains, is defined in a separate file. The
included into 'vuewmrc' Workspace Manager configuration file "includes" (reads in) the subpanel files:
INCLUDE
{

It/usr/vue/config/panel/fp.helplt
}

Subpanel definition

Each subpanel is a box containing its controls. For example,
/usr/vue/config/panels/fp.help contains the Help subpanel.
BOX HelpSubpanel
{

TYPE
CONTROL
}

17-6

subpanel
controLname

Modifying the 1bp or Bottom Row

You can add, delete, or modify controls in the top and bottom rows. You can
also rearrange the rows and move controls from one row to another.

N.OIE
Yoo .do not need· to edit controls .in. the 'Front. Panel to change your default tEmninal,printer, editof,or
maller.

To add or delete a control from the top or bottom row
1. Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HomeDirectory/ . vue/vUeliJIIlTc) for editing.
2. Locate the front panel to be edited using its name (PANEL paneLname).
3. Locate the description for the row to be edited: BOX Top (top row) or BOX
Bottom (bottom row).
4. Examine the list of controls in the box:
CONTROL controL name

• To delete a control, remove or comment out the line for that control.
• To add a control, insert a line for the control.
• To replace a control, replace controL name.
5. If you've added or replaced a control, define the control elsewhere in the
file (see "Defining Front Panel Controls").

17-7

Customizing the Front Panel
Modifying the Top or Bottom Row

6. Save the file and choose Restart Workspace Manager from the Workspace
Menu.
Example

To remove the logo from the bottom row, comment the Logo control.
BOX Bottom
{

TYPE
# CONTROL

CONTROL

secondary
Logo
Lock

}

Example

You want to deactivate the Trash drop zone to prevent users from removing
files. First, find the name of the control:
BOX Bottom
{

CONTROL

Trash

}

Next, find the control definition and edit the lines providing the
drop functionality. This example assumes you've created an action
DisplayTrashError that displays a message informing the user that the control
has been deactivated.
CONTROL Trash
{

# DROP_ACTION

DROP_ANIMATION

i.action DisplayTrashError # Displays error message
TrashDrop

}

See Also

• "Defining Front Panel Controls" explains how to define various types of
controls.
• "Reference: Front Panel" provides additional information about syntax and
keywords.
• "Example: Adding a control to the bottom row" is a step-by-step example
of creating a control.
• "Changing the Default Terminal, Editor, and Mailer" in Chapter 18 covers
how to modify those controls.
• "Customizing Printing" in Chapter 18 covers configuring the Printer
controls.
17-8

Customizing the Front Panel
Modifying the Top or Bottom Row

To modify a control in the top or bottom row
l. Find the control definition using its control name:
CONTROL controLna,me
{

}

If you don't know the control name, you can find it using the row

defintion.
BOX Top

BOX Bottom

{

CONTROL

controLna,me

}

2. Edit the control definition. You can add or remove fields, or simply change
the value of a field.
3. Save the file and choose Restart Workspace Manager from the Workspace
Menu.
You cannot change the position of the busy (logout) button. It must be on the
right side of the bottom (secondary) row.

Example: Adding a control to the bottom row
You want to add a button to the bottom row to start the Wingz application.
You want the button to be between the Terminal and TextEdit controls.
Ordinarily, the command line you use to start the application is:
Wingz

The icon you'll use for the new control is in file is in
/users/ anna/bi tmaps/Wingzlcon (/users/ anna is your home
directory).

17-9

Customizing the Front Panel
Modifying the Top or Bottom Row

Create the action Wingz 1. Double-click CreateAction in the Utilities subdirectory of the General

Toolbox.
2. Fill out the fields:
Name:
Command line:

StartWingz
Wingz

3. Select X Windows from the Window Type options menu.
4. Choose Apply, then Close.
Add the control to the
Front Panel

5. Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HameDirectory/ . vue/vuewmrc) for editing.
6. In vuewmrc find the definition for the bottom row and insert the control at
the proper place in the box:
BOX Bottom
{

TYPE

secondary

CONTROL
CONTROL
CONTROL

Terminal
'WingzControl
TextEdit

}

7. Insert the control definition elsewhere in the file:
CONTROL WingzControl
{

TYPE
HELP_STRING
PUSH_ACTION
IMAGE

button
"Start the Wingz" application.
f.action StartWingz
WingzIcon

}

8. Choose Restart Workspace Manager from the Workspace menu.

17-10

Creating and Modifying Subpanels

Th~re;are; s#e,qi~fproc~dures~;fOrcuhfjgtJri6g.· thePrintets' (regul~rHPVUE$essionil'and r~()rsjHP .VUE

;Lite)es~ionsl'~ubp~nels ; . > . y ·

.•..•. '.

A subpanel is "attached" to a control on the top row. There are two entries
in the Workspace Manager configuration file that attach the subpanel.
• The control definition contains a line:
SUBPANEL subpaneL name

that attaches the subpanel to the control.
• Since the subpanels are defined in other files, the Workspace Manager
configuration file must include those files:
INCLUDE
{

}

See Also

• "'Ib configure a control in the Printers subpanel" in Chapter 18

• "To add an application to the Tools subpanel" in Chapter 23

System subpanel configuration files
Subpanels and their controls are defined in these files in the
/usr/vue/ config/panels directory.

17-11

Customizing the Front Panel
Creating and Modifying Subpanels

fp.clock

Attached to Clock control. Default file is empty (no
subpanel).

fp. date

Attached to Date control. Default file is empty (no
subpanel).

fp.load

Attached to Load control. Default file is empty (no
subpanel).

fp.style

Attached to Style control. Default file is empty (no
subpanel).

fp.help

Help subpanel. Contains default help subpanel.

fp.printer

Printers subpanel. Contains configurable print controls.

fp.mail

Attached to Mail control. Default file is empty (no subpanel).

fp.home

Attached to Home control. Default file is empty (no
subpanel).

fp.toolbox

Toolboxes subpanel for regular HP VUE sessions. Contains
buttons for built-in toolboxes.

fp.tool

Tools subpanel for HP VUE lite sessions.

fp.trash

Trash subpanel. Default file is empty (no subpanel).

If the subpanel configuration file is non -empty, the control to which the

subpanel is attached has an up arrow for displaying the subpanel.

To edit a system-wide subpanel configuration file
l. Log in as root.

2. Open the file for editing.
3. Remove the paragraph near the top of the file containing the =@@= symbol.
This prevents a future update from automatically replacing the edited file.

17-12

Customizing the Front Panel
Creating and Modifying Subpanels

To create a personal subpanel configuration file
• Copy the system subpanel file in /usr/vue/config/panels to the
/ HorneDirectory/ . vue directory. Give the new file write permission.
• Edit the new subpanel configuration file to add or remove controls.
• Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (I HomeDirectory/ . vue/vuewmrc) for editing.
• Edit vuewmrc to include the new file by replacing the line that includes the
system subpanel file with a line that includes the new file.
INCLUDE
{

# Replaces path to system file.
}

Example

You want to "create" and use a personal subpanel that will be attached to the
Mail control:
l. Copy /usr/vue/config/panels/fp.mail to

/ HomeDirectory/ . vue/fp .mail. Give the file write permission.
2. Edit / HorneDirectory/. vue/fp .mail.
3. Double-click EditVuewmrc in the System_Admin subdirectory of the
General Toolbox to open your personal Workspace Manager configuration
file for editing.
4. Edit the line in vuewmrc that includes the fp .mail file so that it reads:
INCLUDE
{

$HOME/.vue/fp.mail
}

5. When you are done editing fp .mail, choose Restart Workspace Manager
from the Workspace menu.
See Also

• "To create a personal Workspace Manager configuration file ('vuewmrc')"
covers how to create vuewmrc.

17-13

Customizing the Front Panel
Creating and Modifying Subpanels

To add or remove a control from an existing subpanel
1. Open the configuration file for the subpanel:

• lusr/vue/config/panellfilename for system-wide changes (you must
be superuser).

• I HomeDirectoryl . vuel filename for personal changes.
2. To add or remove controls, edit the BOX definition for the subpanel.
BOX subpaneLname
{

TYPE
subpanel
CONTROL controLname
}

3. If you've added or replaced a control, define the control elsewhere in the
file.
4. Save the file and choose Restart Workspace Manager from the Workspace
Menu.
You cannot put the Switch control (the workspace switch) in a subpanel.
See Also

• "To create a personal subpanel configuration file" explains how to create a
personal configuration file for a subpanel.

To add a new subpanel
1. Open the configuration file for the subpanel:
• lusr I vuel conf ig/panel I filename for system-wide changes.
• I HomeDirectoryl . vuel filename for personal changes. (See "To create
a personal subpanel configuration file" for instructions on creating this
file.)

17-14

Customizing the Front Panel
Creating and Modifying Subpanels

2. Uncomment the lines that define the box, and edit the box definition to list
the controls that will be in the subpanel.
BOX subpaneLname
{

TYPE

subpanel

CONTROL controLname
}

3. Define each control.
4. Save the file and choose Restart Workspace Manager from the Workspace
Menu.
The subpanels shipped with HP VUE use the convention of repeating the
Front Panel primary control at the top of the subpanel. For example, you can
display the top level of help using either the Help control on the top row of
the Front Panel or the Top Level control in the Help subpanel.
When you are creating your own subpanel, you can choose to duplicate the
primary control in the subpanel unless the primary control is a client window
(for example, the Load control) or a one-instance control (such as the Style
Manager and Trash controls).
See Also

• General information about subpanels:
D "To create a personal subpanel configuration file") covers how to create a
personal subpanel configuration file.
D "Defining Front Panel Controls" describes how to create different types
of controls.
• Configuring special subpanels:
D "To configure a control in the Printers subpanel" in Chapter 18 covers
adding printers to the Printers subpanel.
D "To add a control to the Terminals subpanel" in Chapter 23 covers
modifying the Terminals subpanel for HP VUE Lite sessions.
D "To add an application to the Tools subpanel" in Chapter 23 covers
adding applications to the HP VUE Lite Tools subpanel.

17-15

Defining Front Panel Controls

Controls can have various behaviors:
• Push button.
• Drop zone.
• File monitor.
• Client window.
• One-instance (toggle) button, which allows only one process to be started.
To a certain extent, you can mix behaviors. For example, you can create a
control that is a push button, file monitor, and drop zone. However, you
cannot make a client window into a push button.

To create a push button for an application
• Use the PUSH_ACTION field to describe the behavior of the push button.
There are two ways to describe the command to be executed:
[] Use f . action to specify an action:
PUSH_ACTION

f . action action_name

If the action accepts a file argument, you can specify the file argument

using the syntax:
PUSH_ACTION f. action

action_name filename ' !

[] Use f . exec to specify a command line:
PUSH_ACTION

17-16

f . exec I!command ll

Customizing the Front Panel
Defining Front Panel Controls

Example

The following control runs a game the user has acquired:
CONTROL Ball
{

TYPE
HELP_STRING
IMAGE
PUSH_ACTION

button
"Choose this control to play Ball."
ball
f.exec "/users/anna/bin/games/Ball"

}

Example

This control starts an action named CutDisp.
CONTROL StartCutDisp
{

TYPE
HELP_STRING
IMAGE
PUSH_ACTION

button
"Choose this control to run cutdisp."
cutdisp
f.action CutDisp

}

Example

The following control starts '!ext Editor with the data file

/users/ellen/PhoneList.
CONTROL EditPhoneList
{

TYPE
IMAGE
PUSH_ACTION

button
PhoneBook
f.action "TextEditor /users/ellen/PhoneList"

}

See Also

• "PUSH_ACTION field" reference.

To create a push button and drop zone
1. Use the PUSH_ACTION field to describe the functionality of the push
button. Use f . act ion or f . exec to specify the command.
2. Use the DROP_ACTION field to describe the functionality of the drop zone.
You must use f . act ion for the command, and write the action so that it
accepts a file argument.

17-17

Customizing the Front Panel
Defining front Panel Controls

You can use the same action for the push and drop action.
Example

The following control runs the X client xliirud, which takes a file argument.
CONTROL Project1
{

IMAGE
PUSH_ACTION
DROP_ACTION

/usr/vue/icons/Project1.l.bm
f.action RunXwud
f.action RunXwud

}

To create the RunXuwd action, double-click CreateAction in the Utilities
subdirectory of the General Toolbox and supply values for the fields:
Name:
Command Line:
Window Type:
Filename Prompt:

See Also

RunXwud
xwud -in $1
X Windows
File to display:

• "PUSH_ACTION field" reference.
• "DROP _ACTION field" reference.

To create a control that monitors a file
There are two types of controls that monitor a file-monitor_file and mail.
Monitor empty file

This control type monitors a file, detecting whether it is empty or non-empty.
1. Use the TYPE field to specify type monitor_file.

2. Use the MONITOR_FILE field to specify the file to be monitored.
3. Use the IMAGE field to specify the icon used when the monitored file is
empty, or if the file doesn't exist.
4. Use the ALTERNATE_IMAGE field to specify the icon used when the file is
not empty_

17-18

Customizing the Front Panel
Defining Front Panel Controls

Monitor mail file

This control type monitors a file, changing appearance when information is
added to the file.
1. Use the TYPE field to specify type mail.
2. Use the MONITOR_FILE field to specify the file to be monitored.
3. Use the IMAGE field to specify the icon used when the monitored file is
unchanged since the last time it was opened.
4. Use the ALTERNATE_IMAGE field to specify the icon used when the file
gets larger. (The IMAGE icon is restored when you open the file-for
example, when you start the mail program.)

Example

The following control looks for the presence of a file named calendar that
you expect to be anonymously ftp-ed to your system.
CONTROL MonitorCalendar
{

TYPE
MONITOR_FILE
PUSH_ACTION
IMAGE
ALTERNATE_IMAGE

monitor_file
/users/ftp/calendar
f.exec "/usr/vue/bin/vuepad /users/ftp/calendar"
calendar_no
calendar_yes

}

See Also

• "MONITOR_FILE field" reference .
• "Reference: Front Panel" provides additional information about syntax and
keywords.

To create a one-instance (toggle) control
1. Use the PUSH_RECALL field to set push-recall to True.

2. Use the CLIENT_NAME to attach the client to the control. The
CLIENT_NAME you provide must match the window class name
(WM_CLASS) of the client (usually the same as the client name).
3. Use the PUSH_ACTION field to describe the functionality of the push
button.

17-19

Customizing the Front Panel

Defining Front Panel Controls

A one-instance control checks to see whether the process started by the
button is already running. If the process is not running, the push button
functionality is invoked. If the process is already running, the window is
moved to the top of the window stack in the current workspace.
Example

The following control runs one instance of the datebook application.
CONTROL
{

IMAGE
PUSH_RECALL
CLIENT_NAME
PUSH_ACTION

$HOME/.vue/icons/datebook
True
datebook
f.exec "/usr/local/bin/X11/datebook

}

See Also

• "PUSH_RECALL field" reference.
• "Reference: Front Panel" provides additional information about syntax and
keywords.
• The xprop(1) man page explains using xprop to obtain the WlvLCLASS of
a client.
• The xwininfo (1) man page covers how to find out the size of a window in
pixels.

To create a client window control
1. Use the TYPE field to specify that the control contain a client.
TYPE

client

2. Use the CLIENT_NAME field to specify the client to be started. Choose a
unique client name (note the name of the executable file).
CLIENT _NAME client-name

3. Optional: use the CLIENT_GEOMETRY field to specify the size of the
client window in pixels. If you do this, the LAYOUT_POLICY field must be
included, set to as_needed.
4. Save the configuration file and choose Restart Workspace Manager from the
Workspace menu.
17-20

Customizing the Front Panel
Defining Front Panel Controls

5. Start the client from a command line. The client is linked to the empty
client control through the clienL name:
e:xecutable -name clienL name
In order to place a client window in the Front Panel, the client must have a name command-line option.
Example

The following control displays a 30 x 20 pixel load meter.
CONTROL RemoteLoad
{

TYPE
client
CLIENT_NAME
ScribeLoad
CLIENT_GEOMETRY 30x20
f.exec

To start the xterm window, execute:
remsh hpllrite -n "/usr/bin/X11/xload -nolabel -name ScribeLoad" -display hphere:O
See Also

• "CLIENT _NAME field" reference.

To animate a button
1. Add the PUSH_ANIMATION and/or DROP _ANIMATION fields to the control
definition.
2. Specify the animation sequence using the ANIMATION construct.
Only buttons and drop zones can be animated.

17-21

Customizing the Front Panel
Defining Front Panel Controls

Example

The following lines animate a control that starts the Framemaker™
application. The time delay between icons is 300 milliseconds. The example
assumes you've create icon files frame1, frame2, etc.
CONTROL Frame
{

PUSH_ANIMATION FrameAnimation
}

ANIMATION FrameAnimation
{

frame!
frame2

300

}

See A!so

• Chapter 16 covers creating icons.
• "PUSH_ANIMATION field" reference.
• "DROP _ANIMATION field" reference.

Example: Creating a drop zone to start a terminal
This procedure creates a drop zone on the bottom row of the Front Panel.
Dropping a directory on the control opens a Terminal Emulator set to that
directory. If the user chooses (clicks) the control, it displays a prompt for the
directory name.
Locate the Front Panel
Description

1. Open the personal Workspace Manager configuration file
(/ HorneDirectory/ . vue/vuewmrc).
2. Locate the description of the Front Panel by searching for PANEL
FrontPanel.

17-22

Customizing the Front Panel
Defining Front Panel Controls

Add the control

3. Add the control to the bottom row box:
BOX Bottom
{

TYPE

secondary

CONTROL
CONTROL
CONTROL

TextEdit
DirectoryTerm
Busy

}

4. Create the control:
CONTROL DirectoryTerm
{

TYPE
IMAGE
DROP_ACTION
PUSH_ACTION

button
DirectoryTerm
f.action StartDirectoryTerminal
f.action StartDirectoryTerminal

}

5. Create the file / HomeDirectory/ . vue/types/DirTerm. vf and enter the
action. When you are done, save the file.
ACTION
ARG-TYPES
WINDOW-TYPE
EXEC-STRING
END

StartDirectoryTerminal
DIRECTORY
NO-STDIO
hpterm

6. If the pixmap doesn't exist, use the Icon Editor to create it.
Activate the changes

7. Save the file.
8. Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions.
9. Choose Restart Workspace Manager from the Workspace Menu.

See Also

• "To create a personal Workspace Manager configuration file ('vuewmrc')"
covers how to create vuewmrc.

17-23

General Front Panel Configuration

Front Panel syntax allows you to:
• To configure the workspace switch. This may be useful when you change
the number of workspaces.
• Change the location of the Front Panel.
• Change the color and tile of a row or subpanel.
• Include other files as part of the Front Panel definition.
The ability to include other files provides a convenient way to distribute new
controls from one system to another.

To change the number of workspaces
1. Log into the session (HP VUE or HP VUE Lite) for which you want to
change the number of resources.
2. Start the EditResources action:
• Double-click EditResources in the System_Admin subdirectory of the
General Toolbox.
• Or, execute vue act ion Edi tResources.

3. Add or edit the resource:
Vuewm*workspaceList:

name [name

]

where name is the workspace name. Enclose names containing spaces in
quotation marks.
4. Choose restart Workspace Manager from the Workspace Menu.

17-24

Customizing the Front Panel
General Front Panel Configuration

NOTE
Application windows use the workspace name to. appear in the proper workspac~. When you change
workspace names, you may need to move your applications to different workspaces.

Example

This line creates four workspaces with the names listed.
Vuewm*workspaceList:

Main Remote "Project 1" "Project 2"

To configure the workspace switch
1. To change the number of rows, edit the switch description:

switch

Switch

{
}

2. To change the width of the switch, use the LAYOUT_POLICY field:

switch

Switch

{

LAYOUT_POLICY
}

The default value for LAYOUT_POLICY (standard) creates a fixed switch
width. When LAYOUT_POLICY is set to as_needed, the workspace
buttons are set to a width that accommodates the longest workspace name.

17-25

Customizing the Front Panel

General Front Panel Configuration

To change the Front Panel location
Personal change

1. Make the Front Panel active (click on the frame or press
repeatedly).
2. Press @

(Space)

(Tab)

to display the Front Panel menu, then press (Enter ).

3. Move the panel using the mouse or arrow keys.
4. Click the mouse or press

(Enter).

The new position will be saved and restored by Session Manager.
System-wide change

Set the following resource in /usr/vue/app-defaults/Vue'i1I1l:
VUe'i1I1l*geometry: [±x-offset] [±y-offset]

To include other files
• Use INCLUDE syntax to source in other files:
INCLUDE
{

path/file- name
}

The included file must contain an entire panel, box, or control. The INCLUDE
section cannot be imbedded in existing panel, box, or control definitions.
If you specify a relative path in your personal vue'i1I1lrc file, the path is

interepreted as relative to the home directory.

17-26

Customizing the Front Panel
General Front Panel Configuration

Example

You've defined two controls named Graphics and Spreadsheet in the files
graphics. fp and spreadsheet. fp in / HorneDirectory/ . vue This is how
you would edit vuewmrc to add the controls to the bottom row.
BOX Bottom
{

CONTROL Graphics
CONTROL Spreadsheet
}

INCLUDE
{

$HOME/. vue/graphics. fp
$HOME/.vue/spreadsheet.fp
}

Example

You want to restrict individual users from editing the Top row. To do this:
1. Move the definition of the top row box from
/usr/vue/config/sys.vuewmrcto/usr/vue/config/fp.TopRow.
This is the portion of the file you would move:
BOX Top
{

TYPE

primary

}

2. Include the new file in sys . vuewmrc.
INCLUDE
{

"/usr/vue/config/fp.TopRow"
}

See Also

• "To include a remote file" explains how to use INCLUDE with networked
systems.

17-27

Customizing the Front Panel
General Front Panel Configuration

To create an entirely new front panel
1. Create the new Front Panel. Give it a unique name:
PANEL jronLpaneLname
{

BOX box_name
}

2. Create the new boxes and controls.
3. In your resource database use the name resource to specify the new front
panel.
Vuewm*frontPanel*name: jronLpaneLname

4. Choose Restart Workspace Manager from the Workspace menu to active the
changes.
Creating a new Front Panel may be preferable when you want to make
extensive changes. The new Front Panel can be:
• In / HomeDirectory/ . vue/vuewmrc.

• In another file included into vuewmrc.

You can also create an entirely new Workspace Manager configuration file. Use
the resource:
Vuewm*configFile:

path/filename

to specify the new configuration file.

17-28

Administering a Networked Front Panel

When systems are highly networked, it may be desirable to centralize Front
Panel customization. A new Front Panel or an individual control can be
created in one location and then made available to other systems.
See Also

• "Configuring Access to Remote Data" in Chapter 22 covers configuring
systems to access remote files.

To include a remote file
• If the file is available via an NFS mount, use the syntax:
INCLUDE
{

hostname: path/filename
}

• If the file is not available by an NFS mount, copy it to the other systems.
Example

A file /usr/local/vue/controls/CTerm on system central contains the
definition for a control named CentralTerminal. If central's file system is
NFS-mounted to all the systems that need the control, these lines include the
control:
INCLUDE
{

central:/usr/local/vue/controls/CTerm
}

17-29

Customizing the Front Panel
Administering a Networked Front Panel

Example: Distributing a control
You want to distribute a control that starts the emacs editor, either by
choosing the control or by dropping a file. Both the control and the action
will be created on the host appserver, which acts as application server.
This procedure assumes:
• The application server is configured to export actions to the recipient hosts.
• The recipient hosts is configured to import actions from the application
server.
• The application server's file system is available to the recipient hosts via
NFS mounts.
If these conditions are not met, the control must be distribed by copying the

files containing the control and action definitions.
On the application
server

1. Create the file /usr/vue/config/fp. emacs for the control definition:
CONTROL

EmacsButton

{

IMAGE
emacs
PUSH_ACTION f.action StartEmptyEmacs
DROP_ACTION f.action StartEmacsWithFile
}

2. Create the file /usr/vue/config/export/emacs. vf for the action
definitions:

17-30

ACTION
WINDOW_TYPE
EXEC-STRING
END

StartEmptyEmacs
NO-STDIO
/usr/local/bin/emacs

ACTION
WINDOW_TYPE
EXEC-STRING
END

StartEmacsWithFile
No-STDIO
/usr/local/bin/emacs %(File)Arg_1%

Customizing the Front Panel
Administering a Networked Front Panel

On each recipient
system

3. Add the control to the bottom row:
PANEL Bottom
{

CONTROL EmacsButton
}

4. Include the control in the Workspace Manager configuration file:
INCLUDE
{

appserver: /usr/vue/config/fp.emacs
}

5. Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions.
6. Choose Restart Workspace Manager from the Workspace Menu.

17-31

Reference: Front Panel

The front panel is built hierarchically, from the outside in.
• The panel is a set of boxes, and
• Each box contains a set of controls, and
• Each control is defined by a set of keywords describing its appearance and
behavior.
• Subpanels are boxes attached to controls. Only controls in the top
(primary) row can have subpanels, and there can be only one subpanel per
control.
• Definitions of the panel, boxes, controls, and subpanels consist of a series of
fields.

~--------~CD~----------------~

10 @l 0 0

__ __

~1C3W
~4 D_D______~®~

~ 01

_____~~4~1

The front panel consists of primary CD, secondary (2), and subpanel @ boxes containing
controls @).
The entire panel

The panel consists of a set of boxes, each representing a row. There may be
additional fields that define attributes of the entire Front Panel.
Panel

FronLpaneLname

{

BOX
BOX
other panel fields
}

17-32

Row_name
Row_name

Customizing the Front Panel
Reference: Front Panel

Rowand subpanel
boxes

Boxes consist of a TYPE field and a set of controls. The TYPE field describes
whether the box is a top row, bottom row, or subpanel. There may be
additional fields that define attributes of the entire box.

BOX

Box_name

{

TYPE
CONTROL
CONTROL
CONTROL

type-oj_box
controL name
controL name
controL name

Other box fields
}

Controls

Controls are defined by a series of fields:

CONTROL controLname
{

TYPE
KEYWORD
KEYWORD

controL type
value
value

}

Keywords are not case
sensitive

You can use upper- or lower-case letters in keywords-for example, CONTROL,
Control, or control.

17-33

Customizing the Front Panel
Reference: Front Panel

ALTERNATE_IMAGE field
• Control field.
• Specifies icon used for a control when:
o Button is pushed.
o File monitor detects a change in the monitored file.
• Allowed only for types monitor_file amd mail.
CONTROL

Example

MonitorErrorLog

{

TYPE
ALTERNATE_IMAGE

monitor_file
Errorchange

}

BACKGROUND_TILE field
•
•
•
•
Example

Box field.
Specifies the tiling used for the box background.
Default for top row and subpanels: no tiling
Default for bottom row: rib tiling.
BOX Bottom
{

BACKGROUND_TILE
}

17-34

50_foreground

Customizing the Front Panel
Reference: Front Panel

CLIENT_GEOMETRY field
•
•
•
•

Control field.
Specifies size of client window in pixels: widthxheight
Allowed only for type client.
Default is normal size of the control, based on resolution and location (top
row, bottom row, or subpanel).

If you specify a CLIENT_GEOMETRY, you must also use the LAYOUT _POLICY

field with a value of as_needed.
Example

CONTROL
{

TYPE
CLIENT_GEOMETRY
LAYOUT_POLICY

client
100x64
as_needed

}

CLIENT _NAME field
• Control field.
• Specifies a name used to associate the control with the executable.
• Required for types client and for buttons where PUSH_RECALL is set to
True.
Clients running in the Front Panel for regular HP VUE sessions are saved by
Session Manager.
For HP VUE Lite sessions, the client must be started from the startup script.

17-35

Customizing the Front Panel
Reference: Front Panel

CONTROL

Example

{

TYPE
CLIENT_NAME

client
panelterm

}

To start the terminal, execute (notice the same name, panel term, in the
control definition and command line):
xterm -name panelterm

DROP _ANIMATION field
•
•
•
•

Example

Control field.
Describes the set of files used to animate the drop action.
Not allowed for client-TYPE controls.
The control must have a DROP _ACTION field. The file you drop on the
control will be used as the argument for the action.
CONTROL
{

DROP_ACTION
i.action GraphicsEditor
DROP_ANIMATION OpenGraphicsEditor
}

ANIMATION OpenGraphicsEditor
graphicsedl
graphicsed2

17-36

Customizing the Front Panel
Reference: Front Panel

DROP _ACTION field
• Control field.
• Specifies the function invoked by dropping a file, usually:
f. action action_name

or
f . exec "command"
Example

CONTROL
{

DROP_ACTION

f.action StartVi

}

HELP _STRING field
• Specifies online help for the entire panel, entire box, or a single control.
• Control help takes precedence over box help, which takes precedence over
panel help.
Example

PANEL MyFrontPanel
{

HELP_STRING
BOX

"Use the Help subpanel for more help."
Top

}

BOX Top
{

HELP _STRING
CONTROL

"Choose an arrow button to display a subpanel. I'
Frame

}

CONTROL Frame
HELP _STRING

"Choose this control to start Framemaker. I'

17-37

Customizing the Front Panel
Reference: Front Panel

IMAGE field
• Control field.
• Specifies the control icon.
• If a relative path is used, the icon must reside in directories on the HP VUE
icon search path.
• Allowed for types button, monitor_file, mail, and busy.
If no image file is found, the control name is used as a label.
Example

CONTROL Frame
{

TYPE button
IMAGE frame
}

LABEL field
• Control field.
• Allowed for types button, monitor_file, mail, and busy.
Example

CONTROL Print_Deskjet
{

Label "Deskjet (dj3)"
}

LAYOUT _POLICY field
• BOX field.

17-38

Customizing the Front Panel
Reference: Front Panel

• Two values:
standard

The height of each control is determined by display
resolution.
The height of each control is determined by the image size
or the CLIENT_GEOMETRY field.

You must set LAYOUT _POLICY to as _needed if you want to put a client
window in the front panel with a non -default CLIENT_GEOMETRY.
See Also

• "CLIENT_GEOMETRY field"

MONITOR FILE field
• Control field.
• Specifies the file to be monitored.
• Allowed for types monitor _f ile and mail only.
monitor _file type

ALTERNATE_IMAGE icon is displayed when the monitored file is non-empty.
IMAGE is displayed if the file is empty or non-existent.

mail type

ALTERNATE_IMAGE icon is displayed when the file increases in size.

Example

CONTROL CheckForNewData
{

TYPE
MONITOR_FILE
IMAGE
ALTERNATE_IMAGE

monitor_file
/finance/accounts/July
NoData
DataArrived

}

17-39

Customizing the Front Panel
Reference: Front Panel

PUSH_ACTION field
• Control field.
• Allowed for types button, client, monitor_file, mail, and busy.
• Specifies the action or command invoked by choosing the control:
o To specify an action:
f. action action_name

o To specify a command:
f . exec 11commandl1

f.action Frame

Example
Example

PUSH_ACTION f.action "TextEditor /users/anna/folksongs/Lostine"
f.exec "/usr/bin/XU

Example

PUSH_ANIMATION field
• Control field.
• Specifies the icons to use when button is pushed.
• Allowed for types button, monitor_file, mail, and busy.

17-40

Customizing the Front Panel
Reference: Front Panel

CONTROL Frame

Example

{

PUSH_ANIMATION FrameAnimate
}

ANIMATION FrameAnimate
{

frame 1
frame2
}

PUSH_RECALL field
•
•
•
•
•

Control field.
Allowable values: True or False.
When True, specifies that only one process can be started by the control.
Allowed for types button, monitor_file, mail, and busy.
Default: True.

Set PUSH_RECALL to True to provide behavior like the Style Manager
button. The control must use the CLIENT _NAME field to specify the client
started. When first chosen, the button starts the process. Once the process is
running, choosing the control shuffles the control to the top of the window
stack, and, if necessary, moves it to the current workspace.
Example

PUSH_RECALL

True

17-41

Customizing the Front Panel
Reference: Front Panel

TYPE field
Boxes

• Allowable types:
Larger box, usually the top row. Primary boxes can have
attached subpanels.
Smaller box, usually the bottom row. No subpanels can be
atttached.
A box containing a subpanel.

primary
secondary

subpanel
• Default: secondary.
Controls

• Allowable types:
Space-holder control.
Busy light.
A push button. Buttons can also be drop zones.
A client window.
Front Panel clock.
Front Panel date.
Front Panel mail control. The icon changes when the
monitored mail file gets larger.
monitor_file A control that changes appearance when the contents of
a specified file switches from empty (or non-existent) to
non-empty.
• Default: button.
blank
busy
button
client
clock
date
mail

Example

BOX Top
{

TYPE

Primary

}

CONTROL
{

TYPE
}

17-42

monitor_file

. 'Tennina~", Mail'¢t;l:E~tQr; .

.,an.(it,]~r;i~tet.C;~>rj1j:gU~a1;ion
';-.'1,,;

,,/",

C'<

>~"

Terminal, Mailer, Editor, and Printer Configuration

The Front Panel provides access to a Terminal Emulator (hpterm), a mail
program (elm), and editor (Text Editor). You may want to substitute an
alternative application for one of these.
In addition, HP VUE provides access to a default local printer. However, in

many configurations, it is desirable to provide multiple printers and remote
printers. Furthermore, it may be desirable to configure the Printer control
in the Front panel to discern the type of file being printed and execute a
particular print command.
See Also

These topics cover modifying the controls specific to HP VUE Lite:
• "Customizing HP VUE Lite Terminal Emulators" in Chapter 23.
• "Adding Applications and Utilities to HP VUE Lite" in Chapter 23.

18-2

Changing the Default Terminal, Editor, and
Mailer

The functionality of the Terminal, Editor, and Mail controls are set by actions.
To make it easier to modify these controls, the actions they invoke are
grouped into a single file: /usr/vue/types/user-prefs. vf.
To customize
user·prefs.vf

The file can be copied to:
• For personal customizations: the / HomeDirectory/ . vue/types directory.
• For system-wide customizations: the /usr/vue/config/types directory.

user·prefs.vf maps the
The action definitions in user-prefs. vf are MAP-type actions. For example,
actions to other actions the Front Panel control that starts the mail program invokes an action called

"Mailer." The definition for the mailer in user-prefs . vf is:
ACTION Mailer
TYPE
MAP
END

Elm

The action definition maps the Mailer action to the Elm action. The Elm
action is defined in another file (lusr /vue/types/uxstd. vf).
Remapping actions

The easiest way to change the Mailer, Terminal, Editor, and Printer controls is
to remap the action in user-prefs to a new action that starts a mailer:
ACTION Mailer
TYPE
MAP
END

See Also

maiL action

• "Creating Actions Manually" in Chapter 21 and "Example: creating a MAP
action" in Chapter 21 describe creating MAP actions.

18-3

Terminal, Mailer, Editor, and Printer Configuration
Changing the Default Terminal, Editor, and Mailer

To change the default Terminal Emulator
1. If I HomeDirectoryl . vue/types/user-prefs. vf does not exist, create it
by copying lusr/vue/types/user-prefs. vf. Give the new file write
permission.

2. Remap the TERMINAL action in user-prefs. vf to a different action.
3. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.
Example

The following lines in I HomeDirectoryl . vue/types/user-prefs . vf set the
default terminal to xterm. (Hpterm is replaced with Xterm).
ACTION Terminal

TYPE

MAP

Xterm

END

See Also

• "Customizing HP VUE Lite Terminal Emulators" in Chapter 23 covers
configuring the Terminal button and subpanel for HP VUE lite .
• "Creating a Simple Action" in Chapter 19 covers how to use CreateAction.

To change the default editor
l. If I HomeDirectoryl . vue/types/user-prefs . vf does not exist, create it
by copying lusr Ivue/types/user-prefs . vf. Give the new file write
permission.

2. Remap the EditText action in user-prefs . vf to a different action.
3. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.

18-4

Terminal, Mailer, Editor, and Printer Configuration

Changing the Default Terminal, Editor, and Mailer

Remapping the editor also changes the editor started from the Open
command in File Manager's Actions menu when a data file is selected.
Example

The following lines in / HorneDirectory/ . vue/types/user-prefs. vf set the
default editor to vi. (TextEdi t is replaced with Vi).
ACTION EditText
TYPE
END

MAP

To change the default mailer
l. If / HorneDirectory/ . vue/types/user-prefs. vf does not exist, create it

by copying /usr/vue/types/user-prefs. vf. Give the new file write
permission.
2. Remap the MAILER action to a different action.
3. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.
Example

The following lines in / HorneDirectory/ . vue/types/user-prefs. vf change
the default mailer, assuming you've created an action named Mailx that
executes a mail program on your system. (Mailx replaces Elm)
ACTION Mailer
TYPE
END

MAP

Mailx

The Mailx action can created by starting CreateAction in the Utilties
subdirectory of the General Toolbox, and setting these fields:
Name: Mailx
Command Line: mailx
Window Type: Terminal

See Also

• "Creating a Simple Action" in Chapter 19 covers how to use Create Action.

18-5

Customizing Printing

HP VUE provides a number of printing features
• The Front Panel printer control (regular HP VUE sessions only) includes:
[J

A push button for displaying printer status.

A drop zone for printing a file.

A Printers subpanel for additional system printers.

• The Print command in the File Manager Actions menu.
• Printing within Help Manager
• Printing within applications.
Saa A!so

• Configuring printLng within an application is covered in the documentation
for the application.

To change the printer drop zone and File Manager
Print command
1. If / HomeDirectory/ . vue/types/user-prefs. vf does not exist, create it

by copying /usr/vue/types/user-prefs. vf. Give the new file write
permission.
2. Remap the the Print action in user-prefs. vf to a different action.
To change the drop zone behavior without affecting other print behavior, you
can directly edit the definition of the Printer control in vuewmrc.
Example

The following lines in / HomeDirectory/ . vue/types/user-prefs. vf
configure the Printer control in the top row to execute the following
command when a file is dropped:
Ip -dlj3 filename

18-6

Terminal, Mailer, Editor, and Printer Configuration
Customizing Printing

ACTION Print
TYPE
END

MAP

PrintLj3

The PrintLj3 action can be created by starting Create Action in the Utilties
subdirectory of the General Toolbox, and setting these fields:
Name:
Command Line:
Window Type:
Filename Prompt:

See Also

PrintLj3
lp -dlj3 $1
No Output
Raw file to print:

• "Creating a Simple Action" in Chapter 19 covers how to use CreateAction .
• "To create a push button and drop zone" in Chapter 17 explains how to
define a drop zone in the Front Panel.

To change the functionality of the printer push button
1. Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HameDirectory/ . vue/vuelNIIlrc) for editing.
2. Locate the definition of the Printer control:
CONTROL Printer
{

TYPE

button

}

3. Edit the PUSH_ACTION field.
4. Save the file and Choose Restart Workspace Manager from the Workspace
Menu.
Example

The following change to the PUSH_ACTION field changes the behavior of
the printer control. When pushed, the button will prompt for a file name to
print.
CONTROL Printer
{

18-7

Terminal, Mailer, Editor, and Printer Configuration

Customizing Printing

PUSH_ACTION

f.action Print

}

To configure a control in the Printers subpanel
To change the behavior
of a control

1. Copy /usr/vue/examples/printerNN. vf to:

• For system-wide configuration:
/usr/vue/config/types/printernn.vf.

• For personal configuration:
/ HomeDirectory/ . vue/types/printernn. vf.

where nn is the number of the control. The controls are numbered from
top to bottom; 01 is the control beneath the Default control.
2. Edit printernn. vf:

a. On the line:
set PRINTER_NUMBER=NN

change NN to the number of the control ( 01, 02, etc.).
b. On the line:
set PRINTER_NAME=name

replace name with the device name.
c. If necessary, edit the EXEC-STRING field. By default, it is set up to
execute the command:
lp -dname filename

3. Save the file.
4. Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions.

18-8

Terminal, Mailer, Editor, and Printer Configuration
Customizing Printing

NOTE

,'-

The!op:c~ntrOljnthe. subpanel.(Def~u1~ris configured to. dupli~ate,th~'prirn~rV,~co~trol

in tHe '.yip ,row'Qfthe Jront p;anet:. Yducarmot' changefhe' behavior of that ,control ,using', the . •.
pril}.7CerNN. v.;ffile.lfyou :wa,nt to change the behavioral this, control, yoU must .Sdit :the
controlriamed,pI'iIite~()jnthefp~pr~i:nte,r file;
, '

To configure the
appearance of a control

1. Open fp.printer:

• For system-wide changes: /usr /vue/ conf ig/panels/fp. printer
(you must be superuser) .
• For personal changes: create a personal fp. printer file (see "To create
a personal 'fp.printer' file").
2. In fp . printer, edit the LABEL or IMAGE field for the control.
3. Chooose Restart Workspace Manager from the Workspace Menu.

See Also

• "Where to put icon files" in Chapter 16

To create a personal 'fp.printer' file
1. Copy /usr /vue/ config/panels/fp. printer to the
/ HorneDirectory/ . vue directory. Give the file write permission.

2. Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HorneDirectory/ . vue/vuewmrc) for editing.
3. In vuewmrc, replace the line that includes
/usr /vue/ conf ig/fp . printer with a line that includes the
new file.

18-9

Terminal, Mailer, Editor, and Printer Configuration
Customizing Printing

INCLUDE
{

HomeDirectory/. vue/fp. printer
}

To add another printer control to the Printers subpanel
1. If the change is personal rather than system wide, create a personal
fp. printer file (see "To create a personal 'fp.printer' file".
2. Open fp .printer and add a control to the subpanel box.
BOX PrinterSubpanel
{

TYPE

subpanel

CONTROL

new_controLname

}

3. Add the definition for the new control to the file.
4. Save the file.
5. Create the printer action and reload the database (the database is
automatically reloaded if you use CreateAction).
6. Choose Restart Workspace Manager from the Workspace menu .
See Also

• "To create a personal subpanel configuration file" in Chapter 17 explains
how to create a personal fp. printer file .
• "Creating a Simple Action" in Chapter 19 covers creating actions with the
CreateAction utility.

18-10

Terminal, Mailer, Editor, and Printer Configuration

Customizing Printing

Example: Adding a printer control
to the Printers subpanel
These steps create a personal Printers subpanel with an additional control
that prints multiple copies of a file using the command:
Ip -nnumber -dlj3si filename

Assume your home directory is /users/tim.
Create a personal
'fp.printer' file

1. Copy /usr/vue/ config/panels/fp. printer to
/users/tim/ . vue/fp. printer. Give the new file write

permission.
2. Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HomeDirectory/ . vue/vuewmrc) for editing.
3. In vuewmrc edit the line that includes fp. printer:
INCLUDE
{

"/usr/vue/config/panels/fp.printer"

to include the personal file instead. Save the file.
Add the control to
'fp.printer'.

4. Open /users/tim/ . vue/fp. printer and add the new control to the
subpanel box:
BOX PrinterSubpanel
{

TYPE

subpanel

CONTROL

MultiplePrint

}

5. Add the control to the bottom of the file.
CONTROL MultiplePrint
{

TYPE
LABEL
IMAGE
PUSH_ACTION

button
"Print nil
Ijet
f.action PrintCopies

18-11

Terminal, Mailer, Editor, and Printer Configuration
Customizing Printing

DROP_ACTION
HELP _STRING

f.action PrintCopies
"This control multiple copies of a file '1

}

6. Save fp.printer.
Create a new action

The action is created manually in order to use a non-file argument (the
number of copies).
7. Create the file /users/tim/ . vue/types/PrintCopies. vf.
8. Add the action definition to the file:
ACTION
Print Copies
EXEC-STRING lp -n%IINumber of copies: 11% \
-dlj3si %(File)Arg_1 '1 File to print: "%
END

9. Save the file.
1O. Double-dick ReloadActions in the System_Admin subdirectory of the
General Toolbox.
Restart the Workspace
Manager

11. Choose Restart Workspace Manager from the Workspace menu.

To provide file-type dependent printing
1. Create the file type.
2. Create a special printing action for that file type. You must edit a database
configuration file to do this (you cannot use CreateAction).
3. Map the Print action to the new printing action for that file type.
The filetype-dependent printing will apply to:
• The drop zone in the Front Panel.
• The Print command in the File Manager actions menu.

18-12

Terminal, Mailer, Editor, and Printer Configuration

Customizing Printing

See Also

• "Example: provicling file-type dependent printing" is a step-by-step
example.
• "Creating Filetypes" in Chapter 20 explains how to create filetypes.
• "Creating Actions Manually" in Chapter 21
• "Example: creating a COMMAND action" in Chapter 21 and "Example:
creating a MAP action" in Chapter 21 show examples of creating actions.

Example: providing file-type dependent printing
Your current project is using the file naming convention
these files on a particular printer using the conunand:

* .glp.

You print all

Ip -dlj4 -oc filename

You want to be able to drop a project file on the Front Panel Printer control,
or choose Print from the Actions menu.
l. Open a new file / HomeDirectory/ . vue/types/GlpPrint . vf for editing.

2. Add this file type definition:
FILETYPE
FILE-PATTERN
DESCRIPTION
ACTIONS
END

Glp
*.glp
Data file for the GLP project.
Print

If you have icons for the filetype, you specify them using the L-ICON and

S-ICON fields.
3. Add this action definition:
ACTION
WINDOW-TYPE
EXEC-STRING
END

GlpPrint
NO-STDIO
lp -dlj4 -oc %(File)Arg_1%

4. Add the mapping action:
ACTION
ARG-TYPES
TYPE
END

Print
Glp
MAP

GlpPrint

18-13

Terminal, Mailer, Editor, and Printer Configuration
Customizing Printing

5. Save the file.
6. Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions.

To configure Help Manager printing
Resources for Help Manager let you change the destination printer used when
you print from Help Manager.
See Also

• "To choose a printer for yourself" in Chapter 4

18-14

Introduction to Actions and Filetypes

Actions make it easier to run applications by letting you represent the
application as an icon that you can manipulate. When you create an action,
you integrate the application into the HP VUE environment and "teach" HP
VUE how to run the application.
Filetypes provide the ability to provide different appearance and behavior for
different types of files. For example, you can create different filetypes for the
data for various applications.
There are two ways to create actions:
• Using the Create Action utility in the General Toolbox .
• Manually editing a database file.
Creating filetypes requires you to edit a database file.

19-2

Creating a Simple Action

Create Action creates an action for an application and adds the action to your
Personal toolbox.
The Create Action utility is located:
• HP VUE sessions: Initially, it is placed in your Personal Toolbox. There is
another copy in the Utilities subdirectory of the the General Toolbox.
• HP VUE Lite sessions: The Tools subpanel.

Use the Create Action utility to create new actions.
See Also

• "Limitations of Create Action"
• Chapter 6 explains how to use the toolboxes.

19-3

Introduction to Actions and Filetypes
Creating a Simple Action

• "Creating Actions Manually" in Chapter 21 covers writing actions by
editing the database directly.

What Create Action does
Use Create Action to define new actions. HP VUE uses actions to provide
icons representing applications or other utility programs and scripts.
Create Action automatically does these things:
• Displays the Create Action dialog that lets you create the definition for the
action. When you are done filling in the dialog, Create Action creates a file
containing your new action definition.
• Rereads the database so that the action takes effect immediately (regular
HP VUE sessions only).
• Creates an icon for the action in your Personal Toolbox (regular HP VUE
sessions only). You can double-click the icon to start your application.
Create Action is useful for creating new actions. It cannot be used to edit
existing actions.
See Also

• "Limitations of Create Action"

To use the Create Action utility

19-4

Introduction to Actions and Filetypes
Creating a Simple Action

Start Create Action

1. Double-click CreateAction in your Personal Toolbox, or in the Utilities
subdirectory of the General Toolbox.

Supply the required
information

2. In the Name field, type a unique name for the action. The name can't
include spaces. Try to keep the name under 11 characters long so that
the action will work on systems that do not support long file names.
3. In the Command Line field, type the command that starts the application.
Type the command exactly the way you would type it in a command line,
except that, where you would type a file name, substitute $n, where n is
an integer. Here are some sample command lines:
emacs
bitmap $1
diff $1 $2
lp -oraw $1

The command lines are not passed to a shell unless you explicitly specify
the use of a shell. These lines use use shell processing:
/bin/sh -c 'ps lip'
/bin/sh -c 'spell $1 I more'

4. Use the Window Type options menu to select how the action's output
will be displayed:
X Windows

The application creates it's own window.

No Output

The command has no display output.

Terminal

HP VUE will run the application in a
new Terminal Emulator window. The
window will remain open until you
explicitly close it.

Terminal (auto-close)

HP VUE runs the application in a
new Terminal Emulator window that
closes automatically when you exit the
application.

If you don't know which option to select, leave it set to the default
(Terminal) .
Supply a prompt for
data

5. If the command takes a data file (the Command Line contains $1), type
the text of the prompt into the Filename Prompt field. This is the text
that will be displayed when the action displays a dialog box requiring you
19-5

Introduction to Actions and Filetypes

Creating a Simple Action

to enter a file name. Leave this field empty if the command does not take
a data file.
Supply optional
information

6. If you have special icons for the action, type the filenames in the Large
Icon and Small Icon Fields. (You will have to supply the full path if the
icon file is not located in a directory on the icon search path.) These are
the icons that will be used for the action is the toolbox.
7. In the Description field, type the item ((£D) help for the action icon. You
can use (Enter) to wrap text to the next line in the text box.

Store the action

8. Choose Apply. A dialog box appears telling you the name of the database
file created for the new action, and the system is busy momentarily as
the database is reread. Do not close the Create Action window yet.
9. Open your Personal Toolbox. You should see an action icon for your new
action.

Test the action

10. Double-click the icon. If the action accepts file data, you can also drop a
data file onto it.
11. If necessary, edit the fields in Create Action and reApply the changes.
As long as the Create Action window is open, you can edit the action,
apply the changes, and test the modified action. Once Create Action is
closed, you cannot use it to edit the action-you must manually edit the
file created by Create Action for the action definition.
12. When the action behaves properly, choose Close in the Create Action
dialog.

See Also

• "Where to put icon files" in Chapter 16 explains where you should place
personal icons.
• "Limitations of Create Action" describes the types of actions you must
create by editing the database manually.
• "To provide shell capabilities in an action" in Chapter 21 explains how to
write actions that use shell processing.

19-6

Introduction to Actions and Filetypes
Creating a Simple Action

To use an action created with Create Action
Regular HP VUE
sessions

• To run an action that doesn't require file data, double-click the action icon.
• To run an action that requires file data:
D

Drop a data file on the action to run the application with that file.

Or, if you included a Filename Prompt when you defined the action, you

can double-click the action icon to prompt for the file name. Supply the
absolute path to the file, or a path relative to your home directory.
HP VUE Lite sessions

•

You can attach the action to the Tools control in the top row (see "To assign
an application to the HP VUE Lite Tools control" in Chapter 23).

• You can add the action to the Tools subpanel (see "To add an application to
the Tools subpanel" in Chapter 23).
See Also

• "To make a personal action more readily available" in Chapter 6 explains
copying action icons to other directories.

Limitations of Create Action
You cannot use Create Action to define an action if:
• The action is to be limited to a particular filetype.
• The action requires a non-file parameter. For example, you cannot use
Create Action to write an action for the command:
Ip -ddevice

where the user has to supply device each time the command is executed.
(You can manually create an action that does this.)
• The action uses complex shell syntax. Instead, you can:

19-7

Introduction to Actions and Filetypes

Creating a Simple Action

Write a shell script, and use Create Action to write an action that starts
the script.

Create the action manually by editing a database file .

• The action is a MAP-type action.
You can use Create Action to write actions that run applications on remote
systems by using remsh in the Command Line. However, actions using
remsh will not take advantage of the automatic xhosting mechanism provided
by actions written manually (see "To configure the local host for remote
execution" in Chapter 22) .
See Also

• "Creating Actions Manually" in Chapter 21 covers how to create actions by
editing a database file.

To make a general action with Create Action
1. Create the action using the Create Action utility. When you apply the
action, make note of the file to which the definition is saved.
2. Log in as root.
3. Copy the definition file to /usr/vue/config/types.
4. Create an action icon in the General Toolbox:
• Copy the action icon (( Ctrl ) + drag) from the Personal Toolbox to the
General Toolbox .
• Or, create a new file in /usr/vue/ config/types/tools with the

same name as the action name. Make the file executable.

19-8

Introduction to Actions and Filetypes
Creating a Simple Action

Example: Creating an action for an application
You want to create an action to start the Island Draw™ application on your
system and simutaneously opens a data file in appication. The command line
for this is:
IslandDraw filename
Start Create Action

1. Open the Utilities subdirectory of the General Toolbox.
2. Double-click CreateAction to display the Create Action dialog box.

Define the action

3. Fill out these required fields:
Name:
IslandDraw
Command Line: IslandDraw $1

4. Select X Windows from the Window Type options menu.
5. Supply a prompt for the data file:
Filename Prompt: IslandDraw data file:

Create and test the
action

6. Choose Apply. When the new action has been written to the database, a
message is displayed telling you the name of the file containing the new
definition.
7. Open the Personal Toolbox.
8. Doubleclick IslandDraw to display a prompt for a data file. Supply a data
file and choose OK.
9. When you are satisfied that IslandDraw is working properly, choose Close
in the Create Action dialog.

See Also

• "Adding Applications and Utilities to HP VUE Lite" in Chapter 23 explains
how to add an application to HP VUE lite.

19-9

Creating a Simple Filetype

Filetypes connect applications with their data. For example, you can create a
filetype for an application's data files. The filetype lets you define:
• A unique File Manager icon for the data files.
• Custom double-click behavior for the data files. For example, you
might want to be able to start the application with that data simply by
double-clicking the data file.
See Also

• "Creating Filetypes" in Chapter 20
• "Reference: Filetype Definitions" in Chapter 20

To create a simple filetype
1. Create a database file, or open an existing file, in
/ HomeDirectory/ . vue/types. The file name must end with
.vf.

2. Start the filetype definition by adding the line:
FILETYPE

uniquk5-name

3. Specify the icons for the filetype:
L-ICON
S-ICON

filename
filename

4. Set the file name criteria for typing the file:
FILE-PATTERN

pattern

"To specify the criteria for categorizing the file" in Chapter 20 introduces
how to use FILE-PATTERN.
5. Give the filetype its own item help.
DESCRIPTION

19-10

Introduction to Actions and Filetypes
Creating a Simple Filetype

6. Define the double-click behavior. (Any additional actions listed are added
to the Actions menu in the File Manager.)
ACTIONS

Action_name[,Action_name ... ]

7. End the filetype definition.

END
8. Save the database file.
9. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.

Example: Creating a personal action and filetype
You want to make it easier to run the xgif program, which displays "gif"
pictures. Ordinarily, you run the program by executing:
xgif filename

You want to be able to display "gif" pictures several ways:
• Using the Personal Toolbox: by double-clicking the application icon or
dropping a "gif" data file on it .
• Using File Manager: by double-clicking a "gif" data file, or selecting the
data file and choosing the application from the Actions menu.
Start Create Action

1. Open the Utilities subdirectory 'of the General Toolbox and double-click
Create Action.

Define the action

2. Fill out the required fields:
Name:
Command Line:

GifViewer
/usr/local/bin/X11/xgif $1

3. Select X Windows from the Window Type options menu.

19-11

Introduction to Actions and Filetypes
Creating a Simple Filetype

4. Fill out the optional fields
Filename Prompt: Gif file to view:
Description:
Gif viewer.
Double-click the icon or drop a gif file on it.
Create and test the
action

5. Choose Apply
6. Open the Personal Toolbox and double-click GifViewer. You should see a
prompt Gif file to view:. Supply a "gif" filename and choose OK. The
Gif Viewer should open.
7. Drop a "gif" file on GifViewer. The Gif Viewer should open.
8. When you are satisfied that GifViewer is working properly, choose Close
in the Create Action dialog.

Define the filetype

9. Open / HorneDirectory/ . vue/types/GifViewer. vf for editing.
10. Move to the bottom of the file and start the filetype definition:
FILETYPE

Gif

11. If necessary, create File Manager icons for the gif filetype in the
/ HorneDirectory/bi tmaps directory. Then, specify the icons in the
definition:
L-ICON
S-ICON

gif.1. bm
gif .s.bm

12. Provide item help on Gif file icons.
DESCRIPTION

Gif image file.

13. Specify the file naming criteria for the filetype:
FILE-PATTERN

*.gif

14. Define the Actions menu and default action.
ACTIONS

19-12

GifViewer

Introduction to Actions and Filetypes
Creating a Simple Filetype

15. End the definition. The entire definition looks like this:
FILETYPE
L-ICON
S-ICON
DESCRIPTION
FILE-PATTERN
ACTIONS
END
Update the database

Gif
gif.l.bm
gif.s.bm
Gif image file.
*.gif
GifViewer

16. Save the file gif . vf.
17. Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions to reread the database. The new filetype will
now be in effect.

Test the filetype

18. Select a "gif" file in File Manager.
19. Choose Gi:fViewer from the Actions menu. The Gif Viewer should display
the "gif" image.

19-13

General Action and Filetype Concepts

In many cases, Create Action will easily integrate your application into

HP VUE. However, the action and file type database provides additional
functionality. To take full advantage of its features, it is helpful to understand
some basic concepts. You can use these concepts to design how the
application will be integrated into HP VUE.

Basic concepts of actions and filetypes
Actions replace
command lines

Actions provide a visual representation of a command. The action definition
specifies the command to be executed when the action is invoked, and
connects the command with a visual representation (an icon). That icon
becomes a graphical user interface for the command.

Actions provide icons that start applications and execute commands.

19-14

Introduction to Actions and Filetypes
General Action and Filetype Concepts

Filetypes connect
applications with their
data

A filetype provides both a visual and behavioral distinction for data files:
• It defines a unique icon for the file in File Manager windows.

• It can have a custom Actions menu for tasks you do with the data files.
• It provides "context-sensitivity" for actions. For example, you can write
different versions of the Print action for different filetypes; this creates a
filetype-sensitive Printer control for the Front Panel.
Actions can be used
different ways

Once you've created an action for an application, you can set up your
environment to start the application from:
• A toolbox.
• The Front Panel or one of its subpanels.
• The Window and Workspace menus.
• By creating a filetype, you can start the application from a File Manager
view of one of the application's data files.

Actions and filetypes
have scope

Scope defines who can create and use actions and filetype:
• Personal actions and filetypes are configured in a subdirectory of the home
directory. Therefore, they can be created by an individual user and are
available only to that user.
• General (system-wide) actions and filetypes are created in a directory
generally restricted to system admininstrators (superusers). These are
available to all users on a system.
• Exported actions and filetypes are available to other systems. This allows
the system administrator to create and maintain one set of actions and
filetypes on a central host.

Actions are network
transparent

Actions let you start an application exactly the same way regardless of where
in the network it resides:
• An action definition specifies where to execute the application. The user
doesn't have to worry about such things as host permissions, remote sheils,
or proper search paths each time the application is started.
• The action can specify a remote directory as the default data location.

19-15

Introduction to Actions and Filetypes
General Action and Filetype Concepts

• Actions can be defined remotely. An application server can provide both
the application and the action, thus centralizing administration.
See Also

• "Creating a Simple Filetype" and "Creating Filetypes" in Chapter 20 covers
creating filetypes.
• "Creating Actions Manually" in Chapter 21 covers writing actions by
manually editing database files.
• These topics cover networking with actions:
[J "Using Actions to Run Remote Applications" in Chapter 22
o "Using Actions to Access Remote Data" in Chapter 22
o "Importing and Exporting Actions" in Chapter 22

Preparing to Integrate an Application Into HP VUE
Before writing filetypes and actions, there are some design issues to consider.
Defining the scope

The scope of the action is determined by the database in which it is defined:
• Personal database: for user-specific actions.
• General database: for system-wide actions.
• Exported database: for actions to be exported to other systems. Your
database can also include imported actions-actions located on remote
systems.

Connecting applications
with data

If an application uses data files, you may want to create a filetype for the
application. At the very least, the filetype can provide a unique icon in File
Manager.
The next thing you need to know is whether or not the application can be
started with a file argument. This depends on the syntax of the command to
start the application. For example, Text Editor can be started with an empty
tablet or with a file argument.
vuepad [filename]

19-16

Introduction to Actions and Filetypes
General Action and Filetype Concepts

Some applications require that data be loaded into the application after
the application is started. In this case, no file argument is allowed on the
command line.
Commands without file
arguments

You can provide these behaviors:
• The data file can have its own icon (file type ). Item help on the data file can
identify the application.
• The application can be started by double-clicking its icon in a toolbox.

Commands with file
arguments

You can provide these behaviors:
• The data file can have its own icon (filetype). You can add the applications
to the File Manager Actions menu for the filetype.
• The application can have an icon in a toolbox. The application can be
started by:

See Also

Double-clicking its icon in a toolbox or the Front Panel. The action
displays a prompt for the file argument.

Dragging a file of the correct filetype to the application icon.

Selecting a datafile and then choosing the application from the Action
menu.

• "The local database directories" covers the locations of local database files.
• These topics cover networking with actions:
D "Using Actions to Run Remote Applications" in Chapter 22
D "Using Actions to Access Remote Data" in Chapter 22
D "hnporting and Exporting Actions" in Chapter 22

19-17

The Actions and Filetype Database

Database files

Actions and filetypes are defined in a database that consists of a collection of
files. The files must:
• Have file names name. vf .
• Be located in directories along the specified search path.

Action icons and
toolboxes

Actions are represented visually by action icons. An action icon is simply an
executable file with the same name as the action. The contents of the file
doesn't matter-the file can be empty.
Action icons can be placed in any directory. However, special directories,
called toolboxes, are designed to act as a central, known location.
The default toolboxes are:
• Personal Toolbox.
• General Toolbox.
• Network Toolbox.

19-18

Introduction to Actions and Filetypes
The Actions and Filetype Database

Use the Tools control and Toolboxes subpanel to display the three toolboxes.

File Manager navigation within a toolbox is restricted to subdirectories of the
toolbox.

The local database directories
The database is created from definitions in these directories.
• / HomeDirectory/ . vue/types, the personal database.
• /usr/vue/config/types, the general database.
• /usr /vue/types, the built-in general database. These files may be
overwritten by subsequent updates.

Subdirectories of these directories are used for language-dependent
definitions.

19-19

Introduction to Actions and Filetypes

The Actions and Filetype Database

Precedence in the
database

Where duplicate definitions exists, the definition read first is used.
• Personal definitions are read before general definitions. Built-in definitions
are read last.
• Within a given directory, the

* .vf files are read in alphabetical order.

HP VUE 2.01 users

HP VUE 3.0 will continue to find action and filetype definitions created with
HP VUE 2.01. See "What happens to HP VUE 2.01 actions" in Chapter 28.

Example

The following list shows the order in which a hypothetical database would be
read.
1.
2.
3.
4.
5.

See Also

/lfomeLnrecwry/.vue/types/user-prefs.vf
/ lfomeLnrecwry/ . vue/types/vue. vf
/usr/vue/config/types/print.vf
/usr/vue/config/types/vue.vf
/usr/vue/types/laserrom.vf

• "Localizing actions and filetypes" in Chapter 27 describes the location for
local-language action and filetype definitions.

The location of the toolboxes
The toolboxes are special directories:
• Personal Toolbox: / HorneDirectory/ . vue/types/tools.
• General Toolbox: /usr/vue/config/types/tools.
• Network Toolbox: /usr/vue/config/imports. The imports directory
contains directory links to directories /usr /vue/ config/ export/tools
on other systems.
You can add an action icon to a toolbox from the command line by creating an
executable file with the action name in the toolbox directory. (You must be
superuser to write to subdirectories of /usr/vue.)

19-20

Introduction to Actions and Filetypes
The Actions and Filetype Database

See Also

• "To add a host to the Network Toolbox" in Chapter 22 describes how to
configure the Network Toolbox.

To add an action to a toolbox
• If the action was defined using the Create Action utility, the action icon is

automatically created. You can copy the icon to other directories.
• If the action was defined by editing a database file:

1. Create a file named Action_name in the toolbox.
2. Make the file executable.
Superuser permission is required to write to the system-wide database and
General Toolbox.
You can also create the action icon directly in the toolbox
directory-for example, by creating an executable file in

/ HomeDirectory/ . vue/types/tools.

To reload the database
• Open the System_Admin subdirectory of the General Toolbox and
double-click ReloadActions.
• Or, log out and back in.

You must reread the database after you've manually edited the database.
(The Create Action utility automatically rereads the database.)

19-21

Troubleshooting Actions and Filetypes

If an action or filetype fails to behave as expected, you should check to see

that you've used the correct syntax in the definition. HP VUE provides
several tools for helping you find the source of the problem.

To locate the problem in an action or filetype definition
1. Make sure you reloaded the database after creating the action. This
is done automatically when you use the Create Action utility. If you
create an action manually, you must double-click ReloadActions in the
System_Admin subdirectory of the General Toolbox, or log out and back in.
2. Check the HP VUE errorlog (see "To see database errors (errorlog)").
3. Use the ListVueTypes utility. It will list any errors found in the database
(see "To list database errors").
4. Correct any errors recorded in ListVueTypes, and then rerun
ListVueTypes. (You do not have to reload the database-ListVueTypes
reads the database files directly).
Testing Front Panel
actions

If you added the action to the Front Panel

• Make sure you've restarted the Workspace Manager (choose Restart
Workspace Manager from the Workspace Menu .
• You should test the action outside the Front Panel (from the Personal
Toolbox or by executing:
vueaction action_name
If the action runs correctly outside the Front Panel, then the problem is in

the definition of the Front Panel control.

19-22

Introduction to Actions and Filetypes
Troubleshooting Actions and Filetypes

Common Database Problems
• If the Conunand Line (EXEC-STRING) uses the executable name (rather

than the absolute path), substitute the absolute path to the executable-for
example, /usr/local/bin/ emacs rather than emacs. This will correct
the problem if the executable file is not in a directory specified by the PATH
environment variable.
• If you created the action manually, make sure you used proper syntax:
D

The action must begin with an ACTION field and end with an END field.

If a field continues to the next line, make sure you used \ to indicate the

field includes the next line.
D

Make sure you have not conunented partial lines. For example, the
following line is not valid syntax:
ACTION EditGraphics # Starts the editor for my graphics files.

• If the action executes an application on another system, make sure both

the local and application hosts are configured properly. See "Using Actions
to Run Remote Applications" in Chapter 22. If you are using remsh to start
the application, the execution host must have xhost permission to the local
display.
• If the action uses a data file located on another system, make sure the

systems are set up to access remote data. See "Using Actions to Access
Remote Data" in Chapter 22.
• If the action itself is defined locally, make sure your system and the system

containing the action are set up properly. See "Importing and Exporting
Actions" in Chapter 22.
• If your action specifies an ARG-TYPE, make sure the filetype is defined.
• If your action is mapped to another action, make sure the mapping is

defined properly. The action must eventually map to a COMMAND action.
See Also

• "To see database errors (errorlog)"
• "To list database errors"

19-23

Introduction to Actions and Filetypes
Troubleshooting Actions and Filetypes

To see database errors (errorlog)
• Read the contents of / H~eDirectory/ . vue/ errorlog
Any database errors that occur when the database is reloaded are written to
the errorlog. The database is reloaded when:
• You apply an action with Create Action.
• You manually reload the database with the ReloadActions action in the
System_Admin directory of the General Toolbox.
• You log out and back in.
• You restart the Workspace Manager.
The WatchErrors utility lets you monitor the errorlog continuously (see
"Monitoring errors" in Chapter 29).

To list database errors
• In regular HP VUE sessions, double-click ListVueTypes in the Unsupported
subdirectory of the General Toolbox.
• In HP VUE Lite sessions, execute one of the following commands:
vueaction ListVueTypes

or
vuetypes

to run the ListVueTypes action.
ListVueTypes lists the database search path and all the filetypes and actions
found along the search path.
To direct the database information to a file, rather than to the display, execute
the command:
vuetypes > filename

19-24

General Reference: Actions and Filetypes

These general topics apply to actions and filetypes:
• How the local database search path is determined and changed.
• Using string variables in definitions.
• Using environment variables in definitions.
See Also

• "Reference: Action Definitions" in Chapter 21
• "Reference: Filetype Definitions" in Chapter 20

Changing the local database search path
The default search path for action and filetype definitions includes these
directories, listed in the search order:
HomeDirectory/ . vue/types/ language
HomeDirectory/. vue/types
/usr/local/lib/X11/vue/types@local_apps
/usr/lib/X11/vue/types@system_apps
/usr/vue/config/types/language
/usr/vue/config/types
/usr/vue/types/language
/usr/vue/types

The linked directories (local_apps and system_apps) on the search path
are needed to find HP VUE 2.01 definitions.
To add a directory to the search path, set a value for
the VUEACTIONSEARCHPATH environment variable
in /usr/vue/config/Xsession (system-wide) or
/ HomeDirectory/ . vueprofile (personal). The order of directories in the
variable's value corresponds to the search order. Make sure you include all
the default search path directories in the value.

19-25

Introduction to Actions and Filetypes
General Reference: Actions and Filetypes

See Also

• "To configure the local (importing) host" in Chapter 22 explains how to add

a remote directory to the search path.

String variables in definitions
• Define the string variable in the file using that variable, Use the syntax:
set

variable_ name=value

• Reference the string variable using the syntax:
$ [{] variable_ name [} ]
The variable definition remains in effect from the location of the definition to
the end of the file. (There are no global string variables for the database.)
Variable names can contain any alphanumeric characters and underscore (_).
Each variable definition must be on a separate line.
Example

set Remote_Application_Server=hpapp
~et Remote_File_Server=hpdata
EXEC-HOST $Remote_Applicaton_Server
CWD
$Remote_File_Server:/doc/project

19-26

Introduction to Actions and Filetypes
General Reference: Actions and Filetypes

Environment variables in definitions
• Reference the variable using the syntax: $variable.
The variable is expanded (replaced by its value) when the database is loaded.
If a string variable and environment variable have the same name, the string

variable has precedence.
Example

This execution string prints a file with a banner containing the login name.
EXEC-STRING Ip -t$LOGNAME %(File)Arg_1%

See Also

• "How environment variables are handled during remote execution" in
Chapter 22 covers how to use environment variables with actions that run
remote applications.

19-27

Introduction to Actions and Filetypes
General Reference: Actions and Filetypes

More About Filetypes

You can think of filetypes, used in conjuction with actions, as HP VUE
components that create a grammar for your system. If you think of files
as nouns, then filetypes are the adjectives and actions are the verbs. Like
grammar, the pieces are related to one another. There are rules that govern
how you put them together and how they affect one another.
Filetypes are visual

The visual distinction between filetypes is provided by using a unique icon for
the filetype.

Filetypes are connected •
to actions

A file type can have a custom default (double-click) action and Actions
menu.

• Filetypes provide "context-sensitivity" for actions. For example, you can
write different versions of the PRINT action for different filetypes; this
creates a filetype-sensitive Print control for the Front Panel.
• Filetypes can restrict actions. You can write an action that accepts only a
particular filetype as data.
Criteria for filetypes

You can use any of the following criteria for assigning a file to a filetype:
• File name.
• File location (entire path).
• File content.

Example

The following definition creates a file type for the documents for a project
named "QS". The files are distinguished by filenames beginning with QS and
ending with . doc.
FILETYPE
FILE-PATTERN
DESCRIPTION
L-ICON
S-ICON
ACTIONS
END

20-2

QS_Doc
QS*.doc
This file contains a document for the QS project. \
Double-click the file to open it for editing.
Word_Doc. 1
Word_Doc.s

OPEN

Creating Filetypes

Creating a filetype involves:
• Choosing the criteria used to type the file.
• Defining the filetype in the database.
• Creating any necessary icons for the filetype.
See Also

• "To see database errors (errorlog)" in Chapter 19 and "To list database
errors" in Chapter 19 describe ways to correct errors in the filetypes
database.

To define a filetype in the database
1. Open an existing database file or create a new one. New database files
must use the naming convention filename. vf and be located in directories
on the database search path:
• /usr/vue/config/types for system-wide filetypes.

• / HomeDirectory/ . vue/types for personal filetypes.
• /usr/vue/config/export for filetypes to be exported to other

systems.
2. Add the new filetype definition to the file. Store the file.
3. If necessary, create the bitmaps for the filetype.
4. If necessary, create the actions listed in the ACTIONS field of the filetype
defintion.
5. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.

20-3

More About Filetypes
Creating Filetypes

See Also

• "Getting Started with Icon Editor" in Chapter 16 explains how to make
your own icons.

To specify the criteria for categorizing the file
• Choose from the following criteria:
Criteria

Description

File name

The filename must match a specified pattern. Use the
FILE-PATTERN field.

File location

The path must match a specified pattern. Use the
PATH-PATTERN field. Use the form hostname: I path.

File contents

A specified portion of the file's contents must match
specified data. Use the CONTENT field.

File mode

The file must possess the specified permissions (read,
write, execute, directory). Use the MODE field.

You can use more than one criteria for a filetype. However, you should not
use the FILE-PATTERN and PATH-PATTERN criteria in the same filetype.

20-4

More About Filetypes
Creating Filetypes

Example

The Executable_ObjecLFile filetype defined below applies to all files named
with.o extensions that are executable (x) and (&) non-directories (! d).
FILE TYPE
FILE-PATTERN
MODE

Executable_abject_File
*.0
x8t;!d

END
Example

The QS_Source_File filetype defined below applies to all files with. e
extensions in subdirectories of /proj eets/QS on any host.
FILETYPE
PATH-PATTERN

QS_Source_Files
*:/projects/QS/*/*.c

END
Example

The FinaLpcLgraphics filetype applies to all files named QS* . pel, located
on host hphere, that are read-only (!w) and (&) not directories (!d) and not
executable ( ! x).
FILETYPE
PATH-PATTERN
MODE

Final_pcl_graphics
hphere:*/QS*.pcl
!w8t;!d8t;!x

END
Example

The Wingz_data file type applies to all files with write permission containing
the string WNGZ in the first 100 bytes.
FILE TYPE
CONTENT
MODE

W"ritable_Wingz
a 100 string WNGZ
w8t;!d

END
See Also

•
•
•
•

"CONTENT field" reference.
"PATH-PATTERN field" reference.
"FILE-PATTERN field" reference.
"MODE field" reference.

20-5

More About Filetypes

Creating Filetypes

To associate actions with filetypes
1. Use the ACTIONS field in the filetype definition to list the actions that will
appear in the File Manager Actions menu. The first action in the list will
be the default (double-click) action.

2. Define the actions listed in the filetype definition. If you want the action
to apply only to that filetype, use the ARG-TYPES field in the action
definition.
Example

The following filetype definition creates a filetype for special "readme" files
created by your system administrator that use the naming convention * .rm.
FILETYPE SysReadMe
FILE-PATTERN *.rm
L-ICON
SysReadMe.l
S-ICON
SysReadMe.s
ACTIONS
Open ,Edit
END

A special Respond action is defined below for the file. It opens a writeable
copy of the file in Text Editor. When the files is saved and Text Editor
is exited, the file is mailed to the system administrator (mail address
sysadmin@utd).
ACTION Respond
SysReadMe
ARG-TYPES
EXEC-STRING /bin/sh -c 'cp i.(File)Arg_1i. $HOME/readme.temp;
chmod +w $HOME/readme.temp;
vuepad $HOME/readme.temp;
n
cat $HOME/readme.temp I /usr/bin/mailx sysadmin@utd;
rm $HOME/readme.temp'
WINDOW-TYPE
NO-STDIO
END

20-6

\
\
\
\

More About Filetypes
Creating Filetypes

Example: creating a personal filetype
The following steps create a personal filetype for graphics files for the QS
project. The typing criteria is based on the entire path- the files must be on
system hpaaa in subdirectories of / HomeDirectory/QS/ graphics and end in
*.tiff.
Example

1. Create the file / HomeDirectory/ . vue/types/Pro j ect_graphics . vf ,

containing:
FILETYPE
DEFINITION
L-ICON
S-ICON
PATH-PATTERN
ACTIONS

Project_Graphics
Graphics file for the QS project. Double-click the \
icon to see the graphic.
\
QSgraphics.l.bm
QSgraphics.s.bm
hpaaa:/$HOME/QS/graphics/*/*.tiff
View_Graphics

END

2. If necessary, create the two icons specified in the filetype defintion.
3. If necessary, create the View_Graphics action.
4. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.

20-7

More About Filetypes
Creating Filetypes

Example: creating a system-wide
content-based filetype
The following steps create system-wide filetype for shar-ed files.
1. Log in as root on your system.
2. Create the file usr/vue/config/types/Shar_file.vf, containing:
FILETYPE
DESCRIPTION
CONTENT
L-ICON
S-ICON
ACTIONS

Shar_file
This is a shar-ed file. To unpack it. \
double-click the icon.
0 80 string "# This is a shell archive."
shar.l.bm
shar.s.bm
Unpack

END

3. If necessary, create the two bitmaps specified in the file type definition.
4. If necessary, create the Unpack action.
5. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.

20-8

Reference: Filetype Definitions

Reference sections cover:
• General syntax.
• A sununary of fields.
• An alphabetical listing of all the fields.
See Also

• "General Reference: Actions and Filetypes" in Chapter 19
• "Reference: Action Definitions" in Chapter 21

General syntax for filetype definitions
Field structure

A filetype definition consists of a series of fields. The definition begins with
the mandatory FILETYPE field and ends with the keyword END. Each field
begins with a keyword and ends with a newline character:
FILETYPE
KEYWORD
KEYWORD

jiletype_name
value
value

END
Spaces

Leading spaces in a field are ignored. Therefore, you can use spaces to indent
lines for easier reading.

Fields longer than one
line

The \ character at the end of a line indicates that the field continues onto the
next line.

20-9

More About Filetypes
Reference: Filetype Definitions

Comments

To comment a line, use the # character at the beginning of the line. The #
can be proceeded by spaces. You cannot comment partial-lines.

Example

This filetype definition creates a filetype for read-only files whose filenames
follow the naming convention *. doc. It assumes that the View _Document
action is defined in the database.
FILETYPE
ReadOnlyDocument
DESCRIPTION
This document is not writable. Double-clicking \
runs your editor with a read-only copy of the file.
FILE-PATTERN *.doc
MODE
!d&!x&!w
# The file cannot be a directory, executable, or writeable.
L-ICON
read_only.l.bm
read_only.s.bm
S-ICON
View_Document
ACTIONS
END

Example

This definition creates a filetype for directories named Demo_n where n is 0
through 9.
FILE TYPE
DESCRIPTION
FILE-PATTERN
MODE
L-ICON
S-ICON
ACTIONS
END

Example

Double-click to open it.

control.l.bm
control.s.bm
OpenInPlace,OpenNewView

The following filetype applies to all files named chnn . .xxx where n is 0
through 9, and.xxx is any three-character dot extension. The filetype uses
the default icons.
FILETYPE
DESCRIPTION
FILE-PATTERN
ACTIONS
END

Example

Demo_directory
This is a directory.
Demo_ [0-9J

Chapter file for the project document.
ch[0-9J [0-9J . ???
Edit ,Print

This filetype creates a special icon for directories for which you lack both read
and write permission.
FILETYPE

20-10

More About Filetypes
Reference: Filetype Definitions

DESCRIPTION
MODE
L-ICON
S-ICON
ACTIONS
END
See Also

You cannot open this directory unless you are logged \
in as root.
d&!r&!w
admindirectory.l.bm
admindirectory.s.bm
OpenlnPlace,OpenNewView

• "FILE-PATTERN field" and "PATH-PATTERN field" describe the syntax for
pattern matching.

Summary of Filetype Fields
Required fields

Icons

File recognition fields

Field

Description

FILETYPE

Begins the definition, contains the filetype name.

END

Ends the definition.

Field

Description

L-ICON, S-ICON

Absolute path of the large (L) and small (S) icons in
File Manager. (Default is data file icon)

DESCRIPTION

A description of the filetype displayed when the user
obtains item help on the icon.

Field

Description

FILE-PATTERN

Describes the pattern for matching the file name.

PATH-PATTERN

Describes the pattern for matching the entire path.

MODE

Mode requirements for the file. Use characters d,
liiT, and x, for directory, readable, writable, and
executable. Use & or logical AND, ! for logical
NOT. (Default is non -directory, other permissions
irrelevant).

20-11

More About Filetypes

Reference: Filetype Definitions

Behavior field

CONTENT

Specifies the portion of the file to search and the
content to search for.

ACTIONS

List of the entries in the Actions menu, separated
by commas. The first action in the list is the default
(double-click) action.

ACTIONS field
• Lists the actions to be displayed in the Actions menu.
• Optional.
• Defaults to no actions. The Actions menu is inactive.
This field contains a list of actions displayed in the file manager Actions menu
when a file of this filetype is selected. Items in the list are separated by
commas. There can be no spaces in the list.
The first action in the list is the default action taken when the user
double-clicks the file icon.
Each action must have a corresponding entry in the action definition
database.
Example

The following ACTIONS field lists four actions for the Actions menu.
ACTIONS

Edit ,Print ,Compress ,Archive

CONTENT field
• Describes the content requirements for the filetype.
• Optional.
• Can be used in conjuction with FILE-PATH or FILE-PATTERN.

20-12

More About Filetypes
Reference: Filetype Definitions

Content-based file typing searches a specified portion of the file for the
existence of a particular string or number. The search starts at the position
starting_byte and ends at the position ending_byte.

NOTE
Wide-spread use of content-based filetyping. wn\ result in lower system performance. You should use
name- and location-based filetyping instead wherever possible.

String contents

Use the syntax:
CONTENT

Numeric contents

starting_byte ending_byte string "string"

Use one of the following syntaxes, depending on the type of number:
CONTENT starting_byte ending_byte byte hexadecimaL number
CONTENT starting_byte ending_byte short decimaL number
CONTENT starting_byte ending_byte long decimaL number

Search is conducted from the starting_byte to ending_byte.
Example

CONTENT Value

Interpretation

All files containing Chapter in the first 30
bytes.

30 string 'Chapter'

o 20

byte OxF

All files containing a byte F in the first 20
bytes.

20-13

More About Filetypes

Reference: Filetype Definitions

FILE-PATTERN field
• Specifies the filename requirements for the filetype.
• Optional.
• Defaults to *.
Use the FILE-PATTERN field to specify the filename criteria for the filetype.
Character
?

*[cc ...

]

[c-c]

Example

Meaning
Matches any
Matches any
Matches any
Matches any

single character.
sequence of characters (including a null string).
of the characters (c) enclosed in brackets.
of the characters in the range c through c.

FILE-PATTERN Value

Interpretation

*.c

All files ending with . c.

chapter?text

All files named chapterx. text, where x is
any character.

chapter[1-9].text

All files named chapterx. text, where x is
a character in the range 1 through 9.

L-ICON and S-ICON Fields for filetypes
• Specify the icons for the filetype.
o L-ICON: displayed in File Manager views By Name and Icon.
oS-ICON: displayed in File Manager views By Name and Small Icon.
The value for the L-ICON and S-ICON fields can be:
• The absolute path.
• A filename. The system searches the icon search path.
The default icons are in lusr Ivuel icons.

20-14

More About Filetypes
Reference: Filetype Definitions

Icon file names

There are no name requirements. You can use . bm or . pm extensions to
distinguish between bitmaps and pixmaps.

Icon sizes

Icons can be any size. These are the default sizes.
Icon Type
Data file L-ICON
Data file S-ICON
Executable file L-ICON
Executable file S-ICON
Directory L-ICON
Directory S-ICON

See Also

Icon
22 x
14 x
32 x
16 x
30 x
20 x

Size (WidthxHeight)
30 pixels
17 pixels
32 pixels
16 pixels
23 pixels
16 pixels

• "Where to put icon files" in Chapter 16 explains where the system looks for
icons when you use a filename for L-ICON or S-ICON.

MODE field
• Contains a boolean expression specifying the mode requirements for the
file.
• Optional.
• The default value is a non-directory, all other permissions are irrelevant.
The boolean expression is built from the following operators and values:
Character
&
d
r
tJ

Meaning
Logical operator NOT.
Logical operator AND.
The file is a directory.
The file is readable by the current user.
The file is writable by the current user.
The file is executable by the current user.

You can simulate a logical OR operator by defining the filetypes more than
once using different values in the MODE field.

20-15

Mare About Filetypes
Reference: Filetype Definitions

Example

The following MODE fields specify criteria for file typing.
Not a directory.
Non -directory, not executable by the user.
Non-directory, must be readable by the user.

!d
!d&!x
!d&r
Example

If the mode criteria involves a logical OR, you must define the filetype twice

using the two OR criteria. The filetype Doc_Utility, below, applies to an
executable or directory with the naming convention Doc*.
FILETYPE
FILE-PATTERN
MODE

Doc_Utility
Doc*
d

END
FILETYPE
FILE-PATTERN
MODE

Doc_Utility
Doc*
x

END

PATH-PATTERN field
• Describes the location (path) requirements for the filetype.
• Optional.
• Defaults to *.
PATH-PATTERN filetyping is based on the entire path to the file:
hostname: / path/filename.
Character

Meaning

Matches any single character.

Matches any sequence of characters (including a null string).

[cc ...

[c-cJ

20-16

Matches any of the characters (c) enclosed in brackets.
Matches any of the characters in the range c through c.

More About Filetypes
Reference: Filetype Definitions

Example

FILE-PATH Field Value

Interpretation

hpaaa:$HOME/templates/*

All files in the directory
$HOME/templates on system
hpaaa.
All files in any Mail directories and
their subdirectories on any system.

*:/doc/*/chapter[1-9] .text

All files in subdirectories of / doc
named chapterx. text on any
system.,

hpcvxlp:/doc/sysadm/*.b

All files ending in . b in the
/ doc/ sysadm directory or any of its
subdirectories on system hpcvxlp.

20-17

Mare About Filetypes
Reference: Filetype Definitions

More About Actions

Actions can be created two ways:
• Using the CreateAction utility.
• Manually editing the database.
You can use the CreateAction utility in the General Toolbox to create simple
actions that run local applications with or without file data.
You must create an action manually if you want to write an action that:
• Executes a remote application.
• Uses data other than a data file-for example, a device name.
• Maps to other actions.
• Is filetype-specific.
• Has other capabilities not supported by the CreateAction utility.
See Also

• "Creating a Simple Action" in Chapter 19 covers using the CreateAction
utility.

21-2

Creating Actions Manually

Creating an action manually (by editing a database file) gives you full access
to all the functionality of actions.
Types of actions

See Also

You can create two basic types of actions.
Action type

Description

COMMAND

An action that executes a command. A command action can
start an application or utility, run a shell script, or execute
an operating system command.

MAP

An action that is "mapped to" a command action. Mapping
provides the ability to "enrich" an action name by giving it
different functionality for different filetypes. You cannot use
Create Action to create MAP actions.

• "To see database errors (errorlog)" in Chapter 19 and "To list database
errors" in Chapter 19 describe ways to correct errors in the actions
database.

To create an action manually
1. Open an existing database file or create a new one. New database files
must use the naming convention filename. vf and be located in directories
on the database search path.
• /usr/vue/config/types for system-wide actions (you must be

superuser to create system-wide actions.

• / HameDirectory/ . vue/types for personal actions.
• /usr/vue/config/export for actions to be exported to other systems.

2. Add the new action definition to the file. Store the file.
3. If necessary, create the bitmaps for the action.
21-3

More About Actions
Creating Actions Manually

4. Open the Utilities subdirectory of the General Toolbox and double-click
ReloadActions.
5. Create an executable file with the same name as the action in the Personal
Toolbox or General Toolbox. This file becomes the action icon. The file
will use the icon and item help specified in the action definition.
See Also

• "Example: creating a COMMAND action" and "Example: creating a MAP
action" are step-by-step examples.
• "Building the Execution String for a COMMAND Action" explains how to
write an EXEC-STRING field.
• "General syntax for action definitions" covers the syntax of action
defintions.

Example: creating a COMMAND action
The following steps create an action that prints one or more PCL graphics file
to a printer named 1 j 3 .
1. Create the file / HameDirectory/ . vue/types/Print_actions. vf.

2. Put the following action definition into the file:
ACTION
Print_PCL_file
TYPE
COMMAND
DESCRIPTION Prints a PCL file.
WINDOW-TYPE NO-STDIO
EXEC-STRING /bin/sh -c 'lp -dlj3 -oraw \
%(File)Arg_1/1File(s) to print: "% %(File)Args%'
END

The syntax %(File)Arg_l/1File(s) to print: /1% %(File)Args%
accepts one or more dropped files, or prompts for the file argument if the
action icon is double-clicked.
3. Save the file.

21-4

More About Actions
Creating Actions Manually

4. If necessary, create the PCL file type. (You can use the same database file.)
FILETYPE
FILE-PATTERN
L-ICON
S-ICON
DESCRIPTION
ACTIONS
END

PCL
*.pcl
pcltype.l
pcltype.s
Pel-type file.
Print_PCL_file

Double-click to print.

5. Open the Utilities subdirectory of the General Toolbox and double-click
ReloadActions.
6. Open the Personal Toolbox and create an executable file named
Print_PeL_file.
The Print-PCL_file action can be invoked two ways using its action icon:
• Double-clicking the action icon displays a prompt for the file(s) to print.
• Dropping one or more files on the icon prints the file.
See Also

• "To create an action that accepts a dropped file or prompts for one" .
• "To write actions with multiple, interchangeable file arguments"

21-5

More About Actions
Creating Actions Manually

Example: creating a MAP action
The following steps create an action that "enriches" the Print action for
PCL-type files so that the drop zone in the Front Panel and the Print entry in
the Actions menu prints a PCL file properly.
Example

l. Create the file / HameDirectory/ . vue/types/Print_actions . vf.

2. Define an action PrinLPcLFile that prints a PCL graphics file (such an
action is defined in "Example: creating a COMMAND action").
3. Create an action that maps the Print action to the new PrinLPcLFile
action. Use the ARG-TYPES field to specify that the mapping applies only
to the PCL filetype.
ACTION
ARG-TYPES
TYPE
END

Print
PCL
MAP

4. Create the PCL filetype.
FILETYPE
FILE-PATTERN
L-ICON
S-ICON
DESCRIPTION
ACTIONS
END

PCL
*.pcl
pel type. 1
pcltype.s
Pel-type file.
Print

Double-click to print.

5. Open the Utilities subdirectory of the General Toolbox and double-click
ReloadActions.

21-6

Building the Execution String for a COMMAND
Action

The mandatory fields of a COMMAND action are:
ACTION action_name
EXEC-STRING execution_string
END

The execution string (EXEC-STRING) is generally the most complex field in
an action definition. It uses syntax similar to the command line you would
execute in a Terminal Emulator window, but includes additional syntax for
handling file and non-file arguments.
The execution string is executed directly, rather than through a shell.
However, you can explicitly invoke a shell in the execution string.
The EXEC·STRING uses If your application is located in a directory listed in the PATH variable, you
the PATH
can use the simple executable name. If the application is elsewhere, you must

use the absolute path to the executable file.
Example

This execution string starts the client xclock with a digital clock. The
command line requires no arguments or shell processing, so the execution
string is very simple:
EXEC-STRING xclock -digital

Example

Here is a more complex execution string that requires shell processing and
accepts a file argument.
EXEC-STRING /bin/sh -c 'troff -man %(File)Arg_1"Man Page To Print:"%'

To create an action that uses no data
• Use the same syntax for the EXEC-STRING as you would use to start the
application from a command line.

21-7

More About Actions
Building the Execution String for a COMMAND Action

Example

This execution string is part of an action that starts the X client xcutsel.
EXEC-STRING xcutsel

To create an action that accepts a dropped file
• Use this syntax for the file parameter:

'!.(File)Arg_n'!.
This syntax substitutes the nth file argument into the command line. The file
can be a local or remote file.
Example

This execution string executes xrdb -load using a dropped file as the -load
parameter.
EXEC-STRING xrdb -load %(File)Arg_1%

Example

This portion of an action definition shows that the action works only with
directories. When a directory is dropped on the action icon, the action
displays list of all the files in the directory with read-write permission.
ARG-TYPES

See Also

TERMINAL
vedit -R %(File)Arg_l%

• "ARG-COUNT field" reference.

How HP VUE chooses between two actions with the
same name
When an action is invoked, the system searches the database of available
actions for a name match. When more than one action exists with that name,
the one with the most specific ARG-TYPE or ARG-COUNT takes precedence.
If the actions cannot be distinguished by how specific they are, they are

distinguished by scope. The order of the search is: personal actions, general
actions (in /usr/vue/config/types), built-in actions (in /usr/vue/types);
the first action encountered in the search is used.

21-12

More About Actions
Building the Execution String for a COMMAND Action

Example

Consider the following portions of action definitions.
ACTION EditGraphics
# EditGraphics-l
ARG-TYPES
XWD
END
ACTION EditGraphics
# EditGraphics-2

ARG-COUNT

END
ACTION EditGraphics
# EditGraphics-3

ARG-TYPES

END

Double-clicking Edit Graphics starts EditGraphics-2, since ARG-COUNT 0 has
precedence. When an XWD-type file argument is provided, EditGraphics-1 is
used; EditGraphics-3 is used for all other file arguments.
See Also

• "ARG-COUNT field" reference.
• "ARG-TYPES field" reference.

21-13

Creating Actions With Multiple File Arguments

There are two ways to implement an action that accepts multiple file
arguments:
• The action can use two or more non-interchangeable file-arguments. For
example, the command:
xsetroot -cursor cursorfile maskfile

requires two unique files in a particular order.
• The action can perform the same command sequentially on each file
argument. For example, the command:
pr file (file

... ]

will print one or many files in one print job.

21-14

More About Actions
Creating Actions With Multiple File Arguments

To write an action for non-interchangeable arguments
• If you want the action to prompt for the file names, use this syntax for

each file argument:

%(File) 11 prompt"'!.
using different prompts for each argument.
• To accept dropped files, use this syntax for each file argument:

%(File)Arg_n%
using different values of n for each argument.
Example

This execution string prompts for two files.
EXEC-STRING xsetroot -cursor %(File)"Cursor bitmap:"% \
%(File) "Mask bitmap: "%

Example

This execution string accepts two dropped files. Since order is essential,
it may be necessary to reorder the files in the file manager before dragging
them to the action icon.
EXEC-STRING xsetroot -cursor %(File)Arg_1% \
%(File)Arg_2%

21-15

More About Actions
Creating Actions With Multiple File Arguments

To write actions with multiple,
interchangeable file arguments
• To create an action that accepts dropped files and issues a cormnand in the
form: cammand file l file 2 . . . ,use this syntax for the file arguments:

'/.(File)Args'/.
• To create an action that accepts dropped files or displays a prompt when
double-clicked, use this syntax for the file arguments.

'/. (File) Arg_ n"prampt"'/. '/. (File) Args'/.
The action will issue the cormnand in the form: command file file ... .
• To create an action that accepts multiple dropped files and issues a series of
cormnands in the form:
cammand file
cammand file

use this syntax for the file arguments:

'/.(File)Arg_1
Use this syntax when the command must be issued separately for each file
argument.
Example

This execution string creates an action that executes:
pr file

file

with multiple file arguments. The action has no double-click functionality
EXEC-STRING

Example

pr %(File)Args%

This execution string creates an action similar to the previous example,
except that the action displays a prompt when double-clicked (no file
arguments).
EXEC-STRING

21-16

pr %(File)Arg_l"File(s) to print:"% %(File)Args%

More About Actions
Creating Actions With Multiple File Arguments

Example

This execution string creates an action that executes:
xwud - in file

repeatedly if you supply multiple file arguments.
EXEC-STRING

xwud -in %(File)Arg_1%

To write an action for multiple dropped files
• To accept multiple file arguments that are dropped on the action,execute a
cormnand in the form:
command file file

use the syntax:

%(File)Args%
Example

This execution string executes a script named Checkout for multiple files.
EXEC-STRING /usr/local/bin/Checkout \
%(File)Arg_1"Check out what file?"% %(File)Args%

Example

This execution string performs the diff command on two files. None, one, or
both files can be supplied by dropping the file(s) on the action icon. A dialog
box with prompt(s) appears if no file or one file is dropped.
EXEC-STRING diff %(File)Arg_1"Original File:"% %(File)Arg_2"Altered File:"%

Example

This execution string executes Ip -oraw- with multiple files:
EXEC-STRING /usr/bin/lp -oraw %(File)Arg_1"File to print:"% %(File)Args%

21-17

Creating Special Actions with 'vueaction'

The vueaction utility in HP VUE starts an action. You can use vueaction
in the EXEC-STRING of an action to create special capabilities, including:
• Writing an action that executes a cormnand and then invokes another
action.
• Running an action as a different user.
• Playing back an audio file.

To write an action that invokes another action
• Use the syntax:
vueaction action_name [file_argument(s)]
Example

The following action uses the built-in action CheckSpelling. The new action
runs TextEditor and the spell checker at the same time, displaying the
spelling errors in a separate terminal window.
ACTION EditAndSpell
WINDOW-TYPE NO-STDIO
EXEC-STRING /bin/sh -c 'vueaction CheckSpelling %(File)Arg_1"File"%; \
vuepad %(File)Arg_1%'
END

21-18

More About Actions
Creating Special Actions with 'vueaction'

To create an action that runs as a different user
• Use the following syntax in the EXEC-STRING:

EXEC-STRING
Example

vueaction -user user_name action_name [file_argument]

The following two actions provide the ability to edit the system file
/usr/vue/config/Xsession.
# This action runs a second action, OpenXsessionEdit, as root.

ACTION EditXsession
WINDOW-TYPE NO-STDIO
EXEC-STRING vueaction -user root OpenXsessionEdit
END
# The following action makes Xsession writable, opens it for editing,
# and removes the write permission when the editing session is concluded.

ACTION
WINDOW-TYPE
EXEC-STRING

OpenXsessionEdit
NO-STDIO
/bin/sh -c 'chmod +w /usr/vue/config/Xsession \
vuepad /usr/vue/config/Xsession
\
chmod -w /usr/vue/config/Xsession'

END

21-19

More About Actions
Creating Special Actions with 'vueaction'

To attach audio playback to an action
• Use the following syntax in the EXEC-STRING:
EXEC-STRING vueaction -audio audio_file \
[-volume value] \
[action_name [file_argument] ]
Example

The built-in action that puts a file in the trash can when you drop a file on
the trash icon is named TrashFile. The following action definitions redefine
TrashFile to add audio playback when a file is dropped.
# This action is identical to the built-in TrashFile action, except it
# has been renamed.

ACTION NewTrashFile
TYPE
MESSAGE
MSG-TOOL
FILEMGR
REMOVE_TRASH
MSG-COMMAND
MSG-DATA
%Arg_1 "File To Trash: "% %Args%
DESCRIPTION
The NewTrashFile action places its argument \
in the HP VUE trash can.
END
# The TrashFile action will now play the audio file and invoke the

NewTrashFile action.
ACTION TrashFile
WINDOW-TYPE NO-STDIO
EXEC-STRING vueaction -audio /tmp/lid_open NewTrashFile %Args%
END
#

21-20

Reference: Action Definitions

Reference sections cover:
• General syntax.
• A summary of fields.
• An alphabetical listing of all the fields.
See Also

• "General Reference: Actions and Filetypes" in Chapter 19
• "Reference: Filetype Definitions" in Chapter 20

General syntax for action definitions
Field structure

An action definition consists of a series of fields. The definition begins with
the mandatory ACTION field and ends with the keyword END. Each field
begins with a keyword and ends with a newline character:
ACTION action_name
KEYWORD value
KEYWORD value

END
Spaces

Extra spaces at the beginning or end of lines are ignored, so you can use
spaces to indent lines for easier reading.

Fields longer than one
line

The \ character at the end of a line indicates that the field continues onto the
next line.

21-21

More About Actions
Reference: Action Definitions

Comments

To comment a line, use the # character at the beginning of the line. The #
can be preceded by spaces. You cannot comment partial-lines.

Example

The following lines define a COMMAND action named Xrdb_Merge_Nocpp.
Many fields are omitted because the default values are appropriate.
ACTION
DESCRIPTION
WINDOW-TYPE
EXEC-STRING
END

Example

The next action, IslandPaintOpenDoc, includes fields for custom action
bitmaps. It starts Island Paint™ with a file argument.
ACTION
L-ICON
S-ICON
WINDOW-TYPE
EXEC-HOST
EXEC-STRING
END

Example

Xrdb_Merge_Nocpp
Merges a file into your resource database
NO-STDIO
xrdb -nocpp -merge %(File)Arg_l%

IslandPaintOpenDoc
Ipaint.l.bm
Ipaint.s.bm
NO-STDIO
hpthere
/usr/bin/IslandPaint %(File)Arg_l"File to open:"%

This next action definition creates a synonym action for Open_gif.
ACTION
TYPE
END

Open_gif_file
MAP Open_gif

Summary of Fields for COMMAND Actions
Required Fields

Field

Description (Default)

ACTION

Begins the definition, contains the action name.

END

Ends the definition.

EXEC-STRING

Contains the command to be executed.

21-22

More About Actions
Reference: Action Definitions

Icons

Optional Fields

Field

Description (Default)

DESCRIPTION

A description of the action, displayed when the user
obtains item help on the action icon. (No help.)

L-ICON, S-ICON

Absolute path of the large (L) and small (S) action
icons in File Manager. (act ion. 1 and act ion. s .)

Field

Description (Default)

ARG-COUNT

The number of file arguments the action can have.

ARG-TYPES

Filetypes for which the action is valid (*, 0, or >1).

CWD

The current working directory.

EXEC-HOST

The name of the host on which the application or
command should be executed t.DatabaseHostt.,
%Loca1Host%, %DataHost%, hostname, "prompt").

TYPE

COMMAND.

WINDOW-TYPE

The windowing support required to run the action
(PERM-TERMINAL, TERMINAL, or NO-STDIO).

Summary of Fields for MAP Actions
Required Fields

Icons

Field

Description (Default)

ACTION

Begins the definition, contains the action name.

END

Ends the definition.

Field

Description (Default)

DESCRIPTION

A description of the action, displayed when the user
obtains item help on the action icon. (No help.)

L-ICON, S-ICON

Absolute path of the large (L) and small (S) action
icons in File Manager.

21-23

Mare About Actions
Reference: Action Definitions

ACTION field
• Begins the definition and specifies the action name.
• Required field for all actions.
The action name cannot contain spaces.
ACTION

Example

MergeResources

ARG-COUNT field
•
•
•
•

Specifies the number of arguments the action can accept.
Optional for COMMAND and MAP actions.
Defaults to * (zero or more arguments).
Allowable values:
o Zero arguments.
>1 More than one argument.
* Zero or more arguments.
Values of 0 and >1 have precedence over *.

Use the ARG-COUNT field to enrich an action with different drop and
double-click functionality. To do this, create two different actions with
different ARG-COUNT values and EXEC-STRINGs.
Do not use the ARG-COUNT field to specify that an action prompt
you for a file name when the action icon is double-clicked. This
functionality is provided automatically by using the EXEC-STRING syntax
%(File) Arg_n"prompt ll %for file arguments.
Precedence of actions
using ARG·COUNT

When two actions have the same name and different ARG-COUNT values, the
one with the more specific ARG-COUNT (0 or >1) has precedence over *.

21-24

More About Actions
Reference: Action Definitions

Example
See Also

ARG-COUNT >1

• "To provide different double-click and drop function for an action" explains
how to write an action that uses ARG-COUNT.
• "How HP VUE chooses between two actions with the same name" covers
using ARG-COUNT and ARG-TYPES together.

ARG-TYPES field
• Specifies the filetypes that can be used as data.
• Optional field for COMMAND or MAP actions.
• Defaults to * (all filetypes).
This field consists of a list of filetypes for which the action is valid. Items
in the list are separated by commas. No spaces are allowed in the list of
filetypes.
If this field contains only *, the action is valid for all filetypes.

You can create an action that behaves differently for different filetypes by
creating multiple action definitions, each of which specifies a different filetype.
Precedence of actions
using ARG·TYPES
Example
See Also

When two actions have the same name and different ARG-TYPES values, the
one with the more specific ARG-TYPE (not *) has precedence over *.
ARGTYPES

XWD,TIFF

• "How HP VUE chooses between two actions with the same name" covers
using ARG-COUNT and ARG-TYPES together.

21-25

More About Actions
Reference: Action Definitions

CWD field
•
•
•
•

Specifies the current working directory for the action.
Optional for COMMAND actions.
Cannot be used with MAP actions.
Uses the syntax:
[hostname: ] / path/filename

If hostname is omitted, the database host (host containing the action) is
used.
• Defaults to / HomeDirectory/ when an action is invoked by double-clicking.
Default current working If
directory

CWD is not set in the action definition:

• When the action is invoked by dropping a file argument, the
current-working directory is the directory containing the file.

• When the action is invoked by dropping a directory argument, the
argument becomes the current working directory.
• If the action has no file arguments:
[] If it is started from a toolbox, the home directory is the current working

directory.
[J

If it is started elsewhere, the directory containing the action icon

becomes the current working directory.
[] If the action starts a remote application, the home directory on the
local system becomes the current working diretory if the directory is

NFS-mounted onto the execution host. Otherwise, the home directory on
the execution host becomes the current working directory.
Example

CWD $HOME/project1

21-26

More About Actions
Reference: Action Definitions

DESCRIPTION Field
•
•
•
•

Provides item help for the action icon.
Optional field.
Defaults to NULL (nothing).
Can be used in COMMAND and MAP actions.

The field can contain any characters but newline ((Return )). Line breaks are
automatically inserted to wrap the text to fit in the item help box. Extra
spaces between words are ignored.
Example
DESCRIPTION

Converts an xwd or tiff graphics file to pcl format.
the action by dropping a graphics file on it or by
double-clicking the action icon.

Start \
\

EXEC-HOST field
•
•
•
•

Specifies the host where the command will be executed.
Optional for COMMAND actions.
Cannot be used for MAP actions.
Defaults to the host containing the action (%DatabaseHost'/o).

This field specifies which system in the network will execute the command.
EXEC-HOST Value

Description

'/oDatabaseHost'/o

The host where the action definition resides.

'/oLocalHostY.

The host where HP VUE is running.

%DataHostY.

The host containing the first file argument.

hostname

The named host.

%lJpromptlJ'!o

Prompts the user for the host name each time
the action is invoked.

21-27

More About Actions
Reference: Action Definitions

Example
See Also

EXEC-HOST %DataHost%

• "Using Actions to Run Remote Applications" in Chapter 22 explains how to
write actions that run remote applications.

EXEC-STRING field
• Contains the command executed by the action.
• Required field for COMMAND actions.
• Cannot be used in MAP action.
Syntax for arguments

Keyword

%(File)Arg_n%

Meaning

Substitute the nth file argument.
If the argument uses the syntax

remote_hostname: / path/filename,
the argument is converted to the form
/ nf s / remote_hostname/ path/filename.
Substitute the nth file argument. Do
not translate names from the form
remote_hostname: / path/filename
to the form
/nf s / remote_hostname/ path/filename.
Substitute the nth file argument. If
it is not found, prompt the user for a
file name and substitute the response.
If the argument uses the syntax
remote_hostname: / path/filename,
the argument is converted to the form
/ nf s / remote_hostname/ path/filename.

%(File) "prompt"'!.

21-28

Prompt the user for a file name
and substitute the response. If
the argument uses the syntax
remote_hostname: / path/filename,

More About Actions
Reference: Action Definitions

the argument is converted to the fonn
I nf s I rernote_hostnamel pathlfilename.

Syntax to a invoke shell

See Also

'!.(File)Args'!.

Substitute all of the remaining arguments.

%II prompt'l '!.

Prompt the user and substitute the response.
Do not use this syntax when prompting for a
file name.

Ibinl sh -c 'string'

Invokes csh. The string can be the shell
script or the filename of a shell script.

Ibin/ksh -c 'string'

Invokes ksh. The string can be the shell
script or the filename of a shell script.

• "Environment variables in definitions" in Chapter 19 covers using
environment variables for actions.
• "Building the Execution String for a COMMAND Action" explains how to
write an execution string.
• "To provide shell capabilities in an action" covers writing execution strings
that invoke shells.

L-ICON and S-ICON fields for actions
• Specify the icons for the action.
D L-ICON: displayed in File Manager views By Name and Icon.
oS-ICON: displayed in File Manager views By Name and Small Icon.
• Default: action.l, action.s
The value for the L-ICON and S-ICON fields can be:
• The absolute path.
• A filename. The system searches the icon search path. If the action or
filetype is defined on a remote system, the remote system's search path is
used.

21-29

More About Actions
Reference: Action Definitions

Icon file names

There are no name requirements. You can use . bm or . pm extensions to
distinguish between bitmaps and pixmaps.

Icon sizes

Icons can be any size. These are the default sizes.
Icon Type
L-ICON
S-ICON

Example

See Also

Icon Size (WidthxHeight)
32 x 32 pixels
16 x 16 pixels

L-ICON frame.l.pm
S-ICON frame.s.pm

• "Where to put icon files" in Chapter 16 explains where the system looks for
icons when you use a filename for L-ICON or S-ICON.

The TYPE field
• Describes whether the action contains a command or is mapped to another
action.
• Allowable values: COMMAND or MAP.
• Defaults to COMMAND.
COMMAND type

Example

A COMMAND-type action is a command that will be executed. The action
definition for a COMMAND action must include the execution string for the
command (EXEC-STRING field).
ACTION Remote_PCL_Print
TYPE COMMAND
EXEC-HOST
hpthere
EXEC-STRING /bin/sh -c 'cat %(FiIe)Arg_1"File to convert: '1 % I \
/usr/bin/X11/xwd2sb I \
/usr/bin/pcltrans -s -R -e%"magnification"% > \
%(File) "Destination: 11%'
END

21-30

More About Actions
Reference: Action Definitions

MAP type

ACTION PRINT
ARGTYPES
MAP

XWD
PRINT_XWD

ACTION PRINT
ARGTYPES
MAP

TIFF
PRINT_TIFF

The WINDOW-TYPE Field
•
•
•
•

Example

Specifies the windowing support required by the command.
Optional for COMMAND actions.
Cannot be used with MAP actions.
Defaults to PERM-TERMINAL.

PERM -TERMINAL

The command must be executed in a permanent
terminal emulation window (the window is not closed
when the command terminates). Use with commands
that take some input, produce some output, then
terminate.

TERMINAL

The command must be executed in a terminal window.
The window is closed when the command is exited.
Use with full-screen commands (for example, vi).

NO-STDIO

No windowing support is reQuired. Use with
applications and X clients create their own windows, or
with commands that produce no displayed output (for
example, print commands).

WINDOW-TYPE NO-STDIO

21-31

More About Actions
Reference: Action Definitions

Networking and Distributed Computing

HP VUE is designed to work in a highly networked environment. This is
especially the case with HP VUE actions, which are designed to provide
"network transparency" for the user.
• An action defined locally can run an application on a remote host, or
application server.

Data files
&
Application

I!!!!! I!!!!!

Local
System

Application
Server

A local action can run a remote application.

22-2

Networking and Distributed Computing

• The data can be located on a remote file server. For example, an action
defined locally can use an application on one remote system, which in tum
uses data on another remote system.

File server

I 1
Application

111111

Local
System

Appl ication
Server

A remote application can access data from a file server.

22-3

Networking and Distributed Computing

• An action can be defined remotely and used just as though it were defined
on your system. Thus, you can use a host in your network as an action
server.

File server

Action
&

Application

••
Local
System

Application
Server

An action can be defined on a remote system.

Thus, when you discuss networked actions, there may be several hosts
involved:
local host

The host from which the action is invoked.

execution host

The host where the application invoked by the action runs.

data host

The host where the data is located.

database host

The host where the action is defined.

In X-terminal configurations, an additional host runs the X server.

22-4

Using Actions to Run Remote Applications

In order for a local action to run a remote applicatation:
• The local and remote hosts must be properly configured.
• The action must be writen to invoke the application on the desired host.
You must create the action manually by editing a *. vi file; you cannot use
the Create Action utility.

NorE
You can write actions that run remote applications by usingremshin the command line. However,
actions using remsh will nottake advantage of automaticxhosting mechanism provided by actions
written using the EXEC-HOST field to specify the remote host.

To configure the local host for remote execution
• HP VUE must be installed and running.
• Configure the hostname properly:
o

hostname and network address must be specified in / etc/hosts,

o Or, the operating system name server mechanism may be used.

• Install and configure the standard inetd process. (This should be done
automatically when you install HP VUE. See the inetd(1m) man page for
more information).
• Provide NFS access to the /tmp directory of the execution host. (Mount /
if / and tmp are on the same disk.) These file systems must be mounted

22-5

Networking and Distributed Computing
Using Actions to Run Remote Applications

under Infslexecution_hostltmp (for Itmp) , or Infslexecution_host (for
I). (See "To NFS-mount a remote file system (HP-UX only)".)
• Optional: you can specify the Terminal Emulator used for terminal-based
applications invoked using an action. (The default depends on the
operating system of the machine containing the action definition; hpterm
for HP-UX systems and xterm for other operating systems.) Use the
resource:
*remoteTerminals:

hosLname:term_path [,

...

]

where tenrLpath is the absolute path to the terminal executable on the
remote system.
Automatic xhosting

When the action is executed, HP VUE automatically provides xhost
permission on the display host for the execution host.

Example

The following resource sets terminal emulators for remote applications on two
systems.
remoteTerminals:

cv_sun:/usr/bin/xterm,cv_dec:/usr/bin/X11/decterm

To configure the remote execution host
• Install all of HP VUE, or just the BMS fileset and lusr/vue/bin/vueexec.
• Configure the hostname properly:
[J

hostname and network address must be specified in I etc/hosts,

Or, the operating system name server mechanism may be used.

• Install and configure the standard inetd process. (This should be done
automatically when you install HP VUE. See the inetd (1m) man page for
more information).
• Edit Iusr I adml inetd. sec to allow the local host (the host invoking the
action) to connect to the SpeD service. Use the syntax:
spc allow

22-6

locaL host

Networking and Distributed Computing

Using Actions to Run Remote Applications

• Provide the user (the person invoking the action) with a valid login
(username and password). The user should have the same user-id (uid) as
on the local system.
• If the data resides elsewhere, provide NFS-access to the data.

The current working
directory for remote
applications

When an action executes a remote application, it sets the current working
directory for execution of the application as follows:
• If the user's local home directory is NFS-mounted to the execution host, it
becomes the current working directory.
• If the execution host cannot access the user's local home directory,

the user's home directory on the execution host becomes the current
working directory. In addition, the following error message is written to
/ HomeDirectory/ . vue/ errorlog:
SPCD: Can't connect to hostname.

No mount point.

For example, suppose you have an action that executes Framemaker™ on
remote host hphost. If your local home directory is mounted on hphost, the
application will behave as though you ran it from your local home directory.
Otherwise, the application behaves as though you started it from your home
directory on hphost.
See Also

• "To limit execution access to the system" covers restricting access to the
BMS and SPCD.
• "To configure the execution host to access remote data" desribes how
provide NFS-access to data.

To specify the remote execution host
• In the action definition, use the EXEC-HOST field in the action definition to
specify the host where the command should be executed.
When the EXEC-HOST field is omitted, it is assumed to be the database host
(the host containing the action definition).

22-7

Networking and Distributed Computing

Using Actions to Run Remote Applications

Example

EXEC-HOST Value

Description

%DatabaseHost%

(The default). The host where the action is
defined.

hostname

The named host. Use this value for environments
in which the action should always be invoked on
one particular host.

%LocalHost%

The host where the action is invoked.

%DataHost%

The host containing the data. If the data is on
more than one host, the first file argument is used.

%II prompt II %

Prompts the user for the host name each time the
action is invoked.

EXEC-HOST
EXEC-HOST
EXEC-HOST

hpthere
%"Host containing application:"%
%DataHost%

Execution host is hpthere
Prompts for host
Execution host is same as data
host.

Example: Creating a system-wide action
for a remote application
The application Framemaker™ resides on remote host hpthere. Generally,
it is started from local host "hphere" by executing the command:
remsh hpthere -n /usr/bin/maker -display hphere:O

Create the database file

l. Create the file Iusr Ivuel conf ig/types/FrameMaker . vf. Open the file

for editing.
Define the action

2. Start the action definition:
ACTION

FrameMaker

3. Add a field to provide item help on the FrameMaker application icon in
the toolbox.
DESCRIPTION

22-8

Double-click to start FrameMaker.

Networking and Distributed Computing
Using Actions to Run Remote Applications

4. Specify that the application creates its own window and therefore does
not need to run in a terminal emulator.
WINDOW-TYPE

NO-STDIO

5. Specify that the application runs on host hpthere.
EXEC-HOST

hpthere

6. Add the command executed by the application.
EXEC-STRING

/usr/bin/maker

7. End the definition with the END field. The entire definition looks like '
this:
ACTION
DESCRIPTION
WINDOW-TYPE
EXEC-HOST
EXEC-STRING
END
Define the filetype

FrameMaker
Double-click to start Frame.
NO-STDIO
hpthere
/usr/bin/maker

8. Add a few emply lines for readability and start the filetype definition:
FILETYPE

9. Specify the file naming criteria for the filetype:
FILE-PATTERN

*.fm

10. If necessary, create File Manager icons for the filetype in the directory
lusr Ivuel icons. Then, specify the icons in the definition:
L-ICON
S-ICON

frame.l
frame.s

11. Use the Actions field to specify the contents of the Action menu.
ACTIONS

FrameMaker

By adding this field, you will be able to start Framemaker by
double-clicking a data file.
12. End the definition. The entire definition looks like this:
FILETYPE
FILE-PATTERN
L-ICON
S-ICON
ACTIONS
END

Frame_Data
*.fm
frame.l
frame.s
FrameMaker

22-9

Networking and Distributed Computing
Using Actions to Run Remote Applications

Update the database
and toolbox

13. Save the file FrameMaker . vf.
14. Double-click ReloadActions in the System_Admin subdirectory of the
General Toolbox.
15. Open the Applications subdirectory in the General Toolbox and create an
executable file named FrameMaker.

See Also

• "Where to put icon files" in Chapter 16 explains the directories you should
use to store icons.

How environment variables are handled during
remote execution
Environment variables are acquired as follows:
1. The local environment is transferred to the remote execution host.

2. The local file /usr/softbench/config/softenv is read. Variables
defined there override previous values.
3. $HOME/. softenv is read. Variables defined there override existing values.
4. The environment is further modified according to
/usr/softbench/config/softenv, then $HOME/.softenv
on the remote host.
The DISPLAY variable

If DISPLAY is set to local: n, unix: n, or : n, then it is translated to
hostname: n before being placed in the remote environment.

Variable expansion

Expanding a variable substitutes its value:
• To expand the variable when the database is read, use the form $variable.
• To expand the variable when the execution string is executed, use the form
echo \$variable. This must be done within a shell .

.'22-10

Networking and Distributed Computing
Using Actions to Run Remote Applications

Example

The following execution string does not expand the environment variable
until the action is run. Thus, if the action invokes the application on a remote
system, $HOME will be the value of HOME on the remote system.
EXEC-STRING /bin/sh -c 'cat echo 1\$HOME I /%(File)Arg_1 I Filename:"%'

See Also

• "Environment variables in definitions" in Chapter 19.

22-11

Using Actions to Access Remote Data

Remote data is data that resides elsewhere than on the execution host.
In order to use remote data:
• The execution host must be properly configured to find the data.
• If the data is elsewhere than on the execution host, the user must specify

the host where the data is located.

To configure the execution host to access remote data
• Mount the data host to the execution host. The mount point for the remote
file system must be:
/ nf s / data_host

• If the data host is in a different domain than the execution host, you
must use the fully-qualified domain name of the data host (for example,
pronto. dom .hp. com).

Each user must have the same user id on all machines accessed via NFS.

22-12

Networking and Distributed Computing
Using Actions to Access Remote Data

NOTE

It is .recommended thatalHj.'esystems on· the remote· data host be mounted .to the execution host

See Also

• "To NFS-mount a remote file system (HP-UX only)".

To specify remote data
• When you drop a file on an action icon, the data host is known
automatically.
• When prompted for the filename, use the syntax:
data_host: / path/filename
If data_host is remote, then data_host: is replaced with /nfs/ data_host/.

For example, hpcvxba: /tmp/ data1 becomes /nfs/hpcvxba/tmp/ data1.
• The action definition can specify the current working directory using the
CWD field. If you then respond to a prompt with the filename or a relative
path, the action will use the current working directory.
Example

Suppose the following action is defined and invoked from local host here.
The action will execute the xsetrootgif command locally. If the user
supplies a relative path in reponse to the prompt, the command will look for
the data in /usr /local/ gif on host paecom.
ACTION
CWD
EXEC-STRING
END

Use_gif_Backdrop
paecom:/usr/local/gif
/usr/local/bin/xsetrootgif -gif %(File)Arg_1"gif file:"%

22-13

Networking and Distributed Computing
Using Actions to Access Remote Data

Example

Like the previous example, this action is invoked from host here and gets
its data from paecorn if the user specifies a relative path. However, the
application is located on host ellcorn.
ACTION
CWD
EXEC-HOST
EXEC-STRING
END

Edit_QS_document
paecom:/QSproject/documents/
ellcom
/usr/local/bin/IslandWrite %(File)Arg_1"Document:"%

Configuring diskless clusters for remote data access

• Only a cluster server can export its file system for NFS mounting.
Therefore, the cluster server's file system must be mounted to the
execution host.
• If the execution host is another machine in the same cluster, one of the

following configurations must be used:
[J

Use a symbolic link to mimic NFS m9unting the file system onto itself.
To create this symbolic link, execute:
In -s / /nfs/execution_cnode

• The cluster server's file system can be mounted on to itself. However, this
method is not recommended.

22-14

Networking and Distributed Computing
Using Actions to Access Remote Data

Example

A cluster with cluster server hphusker is to be configured so that its nodes
can use actions that specify the cnode hpabcd as the execution host. The
root directory of hphusker should be linked as follows:
In -s / /nfs/hpabcd

Specifying remote data on a diskless cluster
For context-dependent files:
• When the user supplies the file location in response to a prompt, the
cluster server should be used as the data host.
[J

To specify data on the cluster server, use:
cluster_server: / path/filename

o If /nfs is a context-dependent directory, to specify data on a particular

node, use:
cluster_server: / path/filename+ / node
• If the execution host is another machine in the same cluster, and the

cluster server's file system is NFS-mounted to itself, the cluster server
should be the data host.
• If the execution host is another machine in the same cluster, and symbolic

links are used instead of NFS mounds, context-dependent files are accessed
using the context of the execution host rather than the server.
Example

This location specifies data on remote cluster server hphusker.
hphusker:/etc/inittab

Example

This location specifies data for node hpthere located in remote cluster
hpthere.
hpthere:/etc/inittab

22-15

Networking and Distributed Computing
Using Actions to Access Remote Data

Example

Cluster server hphusker uses symbolic links, rather than NFS mounts, to
provide remote execution within the cluster. Suppose app1 is executing on
node1, and app2 is executing on node2. Then, data specified as:
hphusker:/etc/inittab

refers to hphusker/ ete/ini ttab+/node1 on node1, and
hphusker/ ete/ini ttab+/node2 on node2.
See Also

• The edf (4) man page explains how to access context-dependent files using
an explicit path

22-16

Importing and Exporting Actions

HP VUE allows local systems to access actions defined on remote hosts. The
remote host containing the action definition is called the database host or
the action server. The database host "exports" its actions to other systems,
which, in turn, "import" the action.
For example, a system administrator installing an application on a remote
execution host may find it desirable to define the action for the application on
the same host. Since that action can be made available to the other systems
on the network, it is not necessary to copy the definition from system to
system.
In a diskless cluster, actions imported by the cluster server are available to all
cnodes.
In order for a system to use an action defined remotely:
• The database host must be configured to export the actions to other hosts.
• The local system must be configured to import the remote actions.

To configure the database (exporting) host
1. Place the files (the *. vf files) containing the definitions for the actions to
be exported in /usr/vue/config/export.

2. Create action icons for the actions by placing an executable file for each
action in /usr /vue/ config/ export/tools or one of its subdirectories.
3. Edit / etc/ export to include all hosts who will be using the actions. They
must be allowed to NFS-mount /tmp and /usr/vue/config/export.
4. Edit /usr/adrn/inetd. sec to allow all the hosts using the actions to use
the database host's spc.
5. Perform any additional configuration for remote application and data
access:

22-17

Networking and Distributed Computing
Importing and Exporting Actions

• If the application and data reside on the database host, no additional

configuration is necessary.
• If the application resides elsewhere, then the database host and
execution host must be configured for remote execution.
• If the data resides elsewhere than with the application, then the
database host must be configured for remote data access.
See Also

• "Using Actions to Run Remote Applications" covers configuring the hosts so
that actions can execute remote applications.
• "Using Actions to Access Remote Data" covers configuring the hosts so that
actions can use remote data.

To configure the local (importing) host
l. NFS-mount the file system of the database host to provide access to /tmp

and /usr/vue/config/export. The mount point must be:
/ nf s / database_host

2. Create the directory /usr/vue/config/import if it does not yet exist.
3. Edit /usr/vue/config/Xsession. Add or modify the line that sets the
VUEACTIONREMOTEHOSTS environment variable, which specifies the
remote hosts whose actions will be imported:
VUEACTIONREMOTEHOSTS=remote_host, remote_host

...

4. Add the remote host to the Network Toolbox (see "To add a host to the
Network Toolbox").
5. Log out and back in.
See Also

• "To NFS-mount a remote file system (HP-UX only)" explains how to set up
NFS mounts.
• "To reread Login Manager configuration files" in Chapter 12 explains how
to reread Xsession.

22-18

Networking and Distributed Computing
Importing and Exporting Actions

To add a host to the Network Toolbox
1. Configure the local host to import the actions (see "To configure the local

(importing) host").
2. Configure the remote host to export its actions (see "To configure the
database (exporting) host").
3. Create a link between the Network Toolbox and the remote host (database
host) toolbox:
In -s /nfs/ database_host/usr /vue/ conf ig/ export/tools \
/usr /vue/ config/import/ database_host

This creates the host icon in the top level of the Network Toolbox.

Example: Exporting and Importing an Action
The application Interface Architect on host appserver is used by numerous
systems in the network. It is desirable to create one action for the
application, and export that action to all the systems that use it. Thus,
appserver becomes both the application server and the database (action)
host.
On host 'appserver'

1. Create the file /usr/vue/config/export/architect. vf and define the

action:

ACTION
WINDOW-TYPE
EXEC-STRING
END

Architect

NO-STDIO
/usr/architect/bin/architect

2. Create an action icon by creating an executable file
/usr/vue/config/export/tools/Architect.
3. Edit / etc/ export to include all the hosts that will use the Architect
action.

22-19

Networking and Distributed Computing
Importing and Exporting Actions

4. Edit Iusr I adml inetd. sec to include all the hosts that will use the
Architect action.
On each importing host

l. NFS-mount the file system of appserver.

2. Execute the following command to add the imported actions to the
Network Toolbox on the local hosts.
In -s /nis/appserver/usr/vue/coniig/export/tools /usr/vue/coniig/import/appserver

3. Edit lusr/vuel config/Xsession to add appserver to the local host's
search path using the environment variable VUEACTIONREMOTEHOST:
VUEACTIONREMOTEHOSTS=appserver ~ another_rerrwte-"wst ...

4. Log out and back in.

22-20

Configuring Network Security

There are several security considerations in HP VUE, determining:
• Which users can unlock the display.
• Which systems can NFS-mount local files.
• Which systems can run applications using actions.
• Which systems can access the local display.

To configure who can unlock the display
• Use the Session Manager keys resource to specify who can unlock the
display:
vuesession*keys: user[,user ... ]

The default is the login user and root. Regardless of the value of the resource,
root can always unlock the display.
Example

This resource specifies the users who can unlock the display.
vuesession*keys:

kreta,ellen,dex,anna

To limit access to the local file system (NFS security)
• Edit / etc/ export to provide NFS security. It contains a list of the remote
systems that are permitted to NFS-mount local disk volumes:

jiuLsystem

remote_host

22-21

Networking and Distributed Computing
Configuring Network Security

Example

This entry in I etcl export permits remote host hpthere to mount volume
Idoc.
/doc

hpthere

To limit execution access to the system
1. Edit I etcl services, if necessary. The spc service must be listed.

2. Edit lusr/adm/inetd. sec to include the hosts that should have access
to the local SPCD. You should keep the access list as small as possible,
since these services allow access to the machine by anyone connecting
to the port. To add a complete network, include the network or subnet
component of the address.
The Sub-Process Control Daemon (SPCD or softspcd) supports remote
execution. When an action on a local host invokes an application on a remote
host, the local HP VUE sends a message to the remote SPCD specifing the
execution string for the application. For security reasons, the SPCD does not
allow root to perform remote execution; root can't perform the file-based
authentication over NFS.
By default, the mserve (Message Server) and spc (Sub-Process Control)
services provided by HP VUE are restricted in lusr I adml inetd. sec to:
• The host name of the system .
• The nodes in the cluster, if it is a cluster system. On a diskless cluster,
lusr I adm is a context-dependent directory. Thus, lusr I adml inetd. sec
is not shared automatically within the cluster.

22-22

Networking and Distributed Computing
Configuring Network Security

Example

The following lines in /usr/adm/inetd. sec specify the hosts permitted to
access the local host's BMS: hostA, hostB, haste, and all hosts on subnet
192.6.36.
mserve
spc

See Also

allow
allow

hostA hostB hoste 192.6.36.*
hostA hostB hoste 192.6.36.*

• The inetd. sec (4) man page contains additional information.

To limit remote access to a system's display
The mechanism for restricting access to the local display depends on
whether the display connection is requested by an action or by some other
mechanism.
Display access with
actions

When an action executes a remote application, the application server is
automatically given permission to connect to the local display (the xhost
command is executed automatically).
To turn off automatic authorization, use the resource
[client] *autoXhosting: false

Display access by other
mechanisms

When a remote application is started in ways other than by actions, the
remote host must have explicit permission to connect to the local display.
There are two ways to provide (and limit) remote access to a local display:
• Authorization by host name. This is the default authorization system used
by HP VUE. It involves maintaining a list of all the remote hosts that have
permission to use the local server to display clients. Authorization by host
name is implemented by the / etc/X* .hosts file, where * is the display
(for example, XO .hosts for display 0) or by the xhost command.
• Authorization by user. This feature is provided by the R4 and R5 X servers.

22-23

Configuring Access to Remote Data

In HP VUE, remote data files are accessed using NFS mounts.

Once the remote file systems are mounted, File Manager provides theses
mechanisms for accessing remote files:
• Using the Remote Systems directory.
• Using fully-qualified file names.

To add a host to the Remote Systems (nfs) directory
1. Configure the remote host to allow NFS-access by the local host
(fetc/export).

2. NFS-mount the remote host's file system to the local host. The mount
point for the remote file system must be /nfs/remote_hostname.
The user can can browse files on the remote system by using the
hostname: /path to specify a directory, or by choosing Remote
Systems from the File Manager Directory menu. The Remote Systems
directory is /nfs.

To NFS-mount a remote file system (HP-UX only)
File Manager and actions use NFS mounts to provide easy access to
remote data files. Usually, the remote system files are mounted under
/nf s / hostname.

22-24

Networking and Distributed Computing

Configuring Access to Remote Data

NOTE
This procedure applies to HP-UX systems only.

On the data host

The data host is the system whose files are being accessed.
1. Log in as root.

2. Run SAM. (If the system is running HP VUE, you can run SAM using the
action in the System_Admin subdirectory of the General Toolbox.)
3. In SAM, select:
• For HP-UX 9.0:

Networking/Communications -)
Networked File Systems (NFS) -)
Local File Systems Exported -)
• For HP-UX 8.0:

Networking/Communications -)
LAN Hardware and Software (Cards and Services) -)
NFS (Network File System) Configuration -)
4. Choose Add from the Actions menu.
5. Follow SAM's on-line help to provide permission for the local system
to mount the file system on the data host. The local host must have
permission to mount /tmp. It also must be able to mount directories
containing the data files it needs to access.
On the local system

1. Log in as root.
2. Double-click Sam in the System_Admin subdirectory of the General
Toolbox to run Sam.
3. In SAM, select:
• For HP-UX 9.0:

22-25

Networking and Distributed Computing
Configuring Access to Remote Data

Networking/Communications -)
Networked File Systems (NFS) -)
Remote File System Mounted -)
• For HP-UX 8.0:

Networking/Communications -)
LAN Hardware and Software (Cards and Services) -)
NFS (Network File System) Configuration -)
4. Select Add Remote Directory from the Actions menu.
5. Follow SAM's on-line help to mount the data host's file system under
/nfs/ hostname.
See Also

• The documentation on Networked File Systems contains additional
infonnation about NFS mounting.

If you try to access data not correctly mounted
If the user tries to access a remote directory that is not correctly

NFS-mounted, an error message is displayed telling the user that
the attempt failed. In addition, the following message is written to
/ HomeDirectory/ . vue/ errorlog:
vuefile: Can't connect to hostnanw.

22-26

No mount point.

Changing the System Hostname

If your system uses /usr/adm/inetd.sec to enforce security by listing

specific hosts that are allowed, then the entry for your local host must be
changed to your new host name. For example, if you change the name of
your host from oldname to newname, then you must alter lines of the form:
mserve
spc

allow
allow

oldname host2
oldname host2

by replacing oldname with newname.

22-27

Providing Networked Sessions

A networked session is managed across multiple systems. The networked
session files are located on one system, called the session server. The files
are distributed to other systems using NFS mounts and symbolic links.
For example, suppose you commonly use one of three systems-systemA,
systemB, and systemC. If you provide a networked session:
• All the systems share a single home directory.
• A session saved when you log out on systemA will be restored when you
log into systemB or systemC.
• Personal customizations made on one system are distributed to other
systems-for example, personal filetypes, actions, and Front Panel.
See Also

• "Customizing Sessions" in Chapter 15 describes other aspects of configuring
sessions.

To configure the session server
1. Provide a valid login and password for each user.
2. Edit / etc/ export to list all the hosts using the networked session.
3. For each user:
a. If a display-dependent session exists, remove or move it.
b. Log in and out to create a display-independent session
(I HomeDirectory/ . vue/sessions).
A display-dependent session is a session stored in a
subdirectory of / HomeDirectory/ . vue/ display; for example,
/users/george/.vue/hpaaaa:O/current).

22-28

Networking and Distributed Computing
Providing Networked Sessions

See Also

• "To limit access to the local file system (NFS security)" describes
/ete/export .

• "To create a display-independent session" in Chapter 28.

To configure the local systems
1. Provide NFS access to the home directory on the session server (see "To

NFS-mount a remote file system (HP-UX only)").
2. Move the user's home directory to / HomeDirectory. old/
3. Create a new home directory that is a link to the home directory on the
session server. Use the home directory location specified in / ete/passwd
4. Merge any customizations in /HomeDirectory/ .old into the new linked
home directory.
These steps create a single home directory for the user, regardless of which
system the user logs into.

Example: Configuring networked sessions
System hpaa is the session server for two users.

User
ellen
kreta

$HOME on hpaa
/users2/ellen
/users3/kreta

$HOME on hpbb
/users1/ellen
/users1/kreta

$HOME on hpee
/users/ellen
/users/kreta

22-29

Networking and Distributed Computing
Providing Networked Sessions

On session server
('hpaa')

1. Provide a valid login and password for users ellen and kreta.

2. Edit fete/export to include hosts hpbb and hpee.
/users2
/users3

hpbb hpcc
hpbb hpcc

3. If present, remove or rename these display-dependent sessions:
• /users2/ellen/.vue/hpaa:O.
• /users3/kreta/.vue/hpaa:O.
4. Create these display-independent sessions by having each user log in and

out.
• /users2/ellen/.vue/sessions.
• /users3/kreta/.vue/sessions.
On system 'hpbb"

1. NFS-mount the home directories of hpaa to create:

• /nfs/hpaa/users2
• /nfs/hpaa/users3

2. Move the home directories to a temporary location:
mv /users1/eIIen /users1/eIIen.old
mv /users1/kreta /users1/kreta.old

3. Create new home directories that are links to the home directories on on
hpaa.
In -s /nfs/hpaa/users2/eIIen /users1/eIIen
In -s /nfs/hpaa/users3/kreta /users1/kreta

4. Copy the customizations you want to preserve from the subdirectories of
/users 1/ login_name. old to the new directories.
On system 'hpcc"

1. NFS-mount the home directories of hpaa to create:
• /nfs/hpaa/users2
• /nfs/hpaa/users3

2. Move the home directories to a temporary location:
mv /users/eIIen /users1/eIIen.old
mv /users/kreta /users1/kreta.old

3. Create new home directories that are links to the home directories on
hpaa:
22-30

Networking and Distributed Computing
Providing Networked Sessions

In -s /nfs/hpaa/users2/eIIen /users/eIIen
In -s /nfs/hpaa/users3/kreta /users/kreta

4. Copy the customizations you want to preserve from the subdirectories of
/users/ login_name. old to the new directories.

22-31

Networking and Distributed Computing
Providing Networked Sessions

Customizing HP VUE Lite

The major configuration differences beween regular HP VUE sessions and HP
VUE Lite are:
• Session Manager uses different configuration files for HP VUE Lite, and
session is started from an editable startup script .
• HP VUE Lite has a different Front Panel:
[J

The Front Panel terminal button has a configurable subpanel for starting
other Terminal Emulators.

The Tools control for HP VUE Lite can be configured to start the
application of you choice. The Tools subpanel provides a place to put
controls for starting othre applications.

Since HP VUE Lite does not use File Manager, there are no drop zone
controls (such as the Printer and Trash Can in regular HP VUE sessions).

23-2

Administering HP VUE Lite Sessions

HP VUE Lite sessions are started from a session startup script, which is
responsible for starting clients. Thus, the same clients are started at the
beginning of each session (unlike regular HP VUE sessions, which restores
clients running at the end of the previous session).
Resources are saved and restored from one HP VUE Lite session to another.

To make HP VUE Lite the only session available
1. Log in as root.
2. Set the vuelite resource to true in /usr/vue/config/Xconfig:
Vuelogin*vuelite: true

3. Reread the Login Manager configuration files.
When the vueli te resource is set to true, the user is unable to log into a
regular HP VUE session on that system .
See Also

• "To reread Login Manager configuration files" in Chapter 12 covers how to
reread Xconfig.

23-3

Customizing HP VUE Lite
Administering HP VUE Lite Sessions

To customize HP VUE Lite session startup
System-wide

l. Log in as root.

2. Edit /usr/vue/config/sys. ses .lite to contain a command line
for each client you want to start. All the clients must be started in the
background (each command line must end with &).
This file is used if the user has not created a personal startup script
/ HomeDirectory/ . vue/sessions/lite/vue. session.
Personal

l. If HomeDirectory/ . vue/sessions/Ii te/vue. session does not already
exist, create it by copying /usr/vue/config/sys. ses .lite. Give the

new file write permission.
2. Edit vue. session to include a command line for each client you want to
start. Run the clients in the background (each command line must end
with &).
Example

The following lines start two Terminal Emulator windows: a console in a
workspace named One, and an additional terminal in workspaces One and
Two.
hpterm -C -Is -xrm '*workspaceList: One' &
hpterm -Is -name Terminal -xrm '*workspaceList: One Two' &

To start clients in different workspaces
• If the client has the -workspaceList option, use this syntax for the

command:
command -workspaceList workspace_name [workspace_name ... ]
• If the client lacks the -workspaceList option but has the -xrm option,

use this syntax for the command:

23-4

Customizing HP VUE Lite
Administering HP VUE Lite Sessions

command -xrm '*workspaceList: workspace_name workspace_name . .. J'
If workspaceList is not specified, the application window is placed in the

workspace displayed at the end of the previous session.
Example

The following command line starts an xterm window in two workspaces
named proj ect1 and extra space.
xterm

-xrm '*workspaceList: project1 "extra space'"

To set resources for the first HP VUE Lite session
1. Before running the first HP VUE Lite session, log into No Windows mode
or a fail-safe session.
2. Log in as root.
3. Edit /usr/vue/config/sys.res.lite

At logout, resources are saved to
/ HomeDirectory/ sessions/Ii te/vue. resources. They are
restored at the next session.
Resources are saved and restored separately for HP VUE lite sessions and
regular HP VUE sessions. Therefore, changes you make to an HP VUE lite
session have no effect on the next regular session.
See Also

• "Syntax of resource specifications" in Chapter 25

To set resources during an HP VUE Lite session
Change the resources using:
• Style Manager.
• Or, manually setting the resources.

23-5

Customizing HP VUE Lite
Administering HP VUE lite Sessions

Resources changed during an HP VUE Lite session are saved at logout, and
restored at the beginning of the next HP VUE Lite session .
See Also

• Chapter 25.

How HP VUE Lite sessions are started
HP VUE Lite does not use the same Session Manager as regular HP VUE
sessions. In most cases, logging in and out is faster with HP VUE Lite.
When the user has been validated, HP VUE Lite Session Manager executes
the shell script lusr Ivue/bin/vueli tesess ion. The script:
1. Loads resources from the appropriate resource file:
• If / HorneDirectory/ . vue/ sessions/lite/vue. resources exists, it is

used.
• Otherwise, the system default /usr/vue/config/sys.res.lite is
used.
2. Executes vueheIIo, which displays the greeting screen.
3. Starts the color server.
4. Starts the window manager (vuewm).
5. Executes the HP VUE lite session startup script to start applications:
• If executable file / HorneDirec-

tory/ . vue/sessions/Iite/vue. sessions exists, it is
used.
• Otherwise, the system default /usr/vue/config/sys.ses.lite is
used.
When the user logs out:
1. The Window Manager halts.
2. Session resources are saved into
/HorneDirectory/.vue/sessions/lite/vue.resources.

23-6

Customizing HP VUE Lite Terminal Emulators

You can customize Terminal Emulators by:
• Switching to a different terminal emulator client.
• Customizing the Terminal button and Terminals subpanel.

To use a different terminal emulator in HP VUE Lite
1. If / HmneDirectory/ . vue/types/user-prefs. vf does not exist, create it
by copying /usr/vue/types/user-prefs. vf. Give the new file write

permission.
2. Remap the Terminal action to a different action.
3. Choose Restart Workspace Manager from the Workspace menu.
If the actions to which the remote terminals are mapped do not already exist,

you will have to create them.
Example

The following lines in HmneDirectory/ . vue/types/user-prefs. vf set the
default terminal to xterm. (Xterm is the name of a built-in action.)
ACTION Terminal

TYPE

MAP

Xterm

END
See Also

• "Creating a Simple Action" in Chapter 19 explains how to use Create
Action to create new actions.

23-7

Customizing HP VUE Lite
Customizing HP VUE Lite Terminal Emulators

To customize the remote terminal buttons
1. If / HomeDirectory/ . vue/types/user-prefs. vf does not exist, create it
by copying /usr/vue/types/user-prefs. vf. Give the new file write

permission.
2. Remap the the RemoteHpterm or RemoteXterm actions to different actions.
3. Choose Restart Workspace Manager from the Workspace Menu.
If the actions to which the remote terminals are mapped do not already exist,
you will have to create them.
See Also

• "Creating a Simple Action" in Chapter 19 explains how to use Create
Action to create new actions.

To add a control to the Terminals subpanel
1. If the change is personal rather than system wide, create a personal
fp. terminal file (see "To create a personal Terminals subpanel
configuration file").
2. Open fp. terminal and add a control to the subpanel box.
BOX TerminalSubpanel
{

TYPE

subpanel

CONTROL

new_controL name

}

3. Add the definition for the new control to the file.
4. Save the file.
5. Create the terminal action.
6. Choose Restart Workspace Manager from the Workspace menu.

23-8

Customizing HP VUE Lite

Customizing HP VUE Lite Terminal Emulators

See Also

• "Example: Adding a terminal to the Terminals subpanel" is a step-by-step
example.
• "To create a personal subpanel configuration file" in Chapter 17 explains
how to create a personal fp. terminal file.
• "To use Create Action in HP VUE Lite" covers creating actions with the
Create Action utility.

To create a personal Terminals subpanel
configuration file
• Copy /usr/vue/config/panels/fp. terminal to the
/ HomeDirectory/ . vue directory. Give the new file write permission.
• Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (I HomeDirectory/ . vue/vuewmrc) for editing.
• Edit vue1iJmrc to include the new file by replacing the line that includes the
system subpanel file with a line that includes the new file.
INCLUDE
{

"HomeDirectory/ . vue/fp. terminal"
}

Example: Adding a terminal to the Terminals subpanel
These steps create a personal Terminals subpanel with an additional control
that starts an hpterm window with scrollbars. Assume your home directory
is /users/tim.

23-9

Customizing HP VUE Lite
Customizing HP VUE Lite Terminal Emulators

Create a personal
'fp.terminal' file

l. Copy /usr/vue/config/panels/fp. terminal to

/users/tim/ . vue/fp. terminal. Give the new file write

permission.
2. If /users/tim/ . vue/vueliJIIlrc doesn't already exist, create it by
copying /usr /vue/ config/ sys . vueliJIIlrc and giving the new file write
permission.
3. In vueliJIIlrc edit the line that includes fp. terminal:
INCLUDE
{

"/usr/vue/config/panels/fp.terminal"
}

to include the personal file instead. Save the file.
Add the control to

'ip.ierminai'.

4. Open /users/tim/ . vue/fp . terminal and add the new control to the
subpanel box:
BOX TerminalSubpanel
{
TY~E

subpanel

CONTROL

HpTermScroll

}

5. Add the control to the bottom of the file.
CONTROL HpTermscroll
{

TYPE
button
LABEL
"Scrollable hpterm"
IMAGE
termina
PUSH_ACTION f.action HptermSrollBar
HELP_STRING "This control opens an hpterm window with scrollbars. II
}

6. Save fp. terminal.
Create a new action

7. Choose Create Action in the Tools subpanel to open the Create Action
dialog box.
8. Provide values for these fields:
Name: HptermScrollBar
Command Line: hpterm -sb

23-10

Customizing HP VUE Lite
Customizing HP VUE Lite Terminal Emulators

Window Type: X Windows

9. Choose Apply, then Close.
Restart the workspace
manager

10. Choose Restart Workspace Manager from the Workspace menu.

23-11

Adding Applications and Utilities to HP VUE
Lite

The Tools control in the HP VUE Lite Front Panel provides easy access to
applications and utilities. You can:
• Configure the HP VUE Lite Tools control in the top row of the Front Panel
to start an application.
• Add applications to the Tools subpanel.
• Create your own actions, which can then be added to the Front Panel.
See Also

• "To start an application or utility in HP VUE Lite" in Chapter 6 explains
how to start applications in HP VUE Lite.

To assign an application to the
HP VUE Lite Tools control

You can configure the Tools control

CD to start the application of your choice.

• Choose Create Action in the Tools subpanel to display the Create Action
dialog box.
• Fill in the required fields. Name the action MainTool
• If desired, fill in the optional fields.

• Choose Apply to save the action, then Close.
• Choose Restart Workspace Manager from the Workspace Menu.

23-12

Customizing HP VUE Lite
Adding Applications and Utilities to HP VUE Lite

The action name MainTool attaches the new action to the Tools control on
the top row.
See Also

• "To use Create Action in HP VUE Lite" explains how to use Create Action.

Example: Assigning an application to the HP VUE Lite
Tools control
You frequently use the application IslandPaint™ and want to be able to start
it by choosing the Tools control. The command to start the application is
IslandPaint filename
Define the action

1. Choose Create Action in the Tools subpanel to open the Create Action
dialog box.
2. Supply these values to the fields:
Name:
Command Line:
Window Type:
Filename Prompt:

MainTool
IslandPaint
X Windows
IslandPaint data file:

If IslandPaint is not located along the PATH search path, you must use the

absolute path to the executable file.
3. Choose Apply, then Close.
4. Choose Restart Workspace Manager from the Workspace Menu.

To add an application to the Tools subpanel
1. If the change is personal rather than system wide, create a personal
fp. tool file (see "To create a personal Tools subpanel file").

23-13

Customizing HP VUE Lite
Adding Applications and Utilities to HP VUE Lite

If the change is system-wide, use the system file

/usr/vue/ config/panels/fp. tool (you must be superuser).

2. Open fp. tool and add a control to the subpanel box.
BOX ToolsSubpanel
{

TYPE

subpanel

CONTROL new_controL name
}

3. Add the definition for the new control to the file.
4. Save the file.
5. Create the action for the application.
6. Choose Restart Workspace Manager from the Workspace menu.
See Also

• "Example: Adding an Action to the Tools subpanel" is a step-by-step
example.
• "To create a personal subpanel configuration file" in Chapter 17 explains
how to create a personal fp . tool file.
• "Creating a Simple Action" in Chapter 19 covers creating actions with the
Create Action utility.

To create a personal Tools subpanel file
• Copy the /usr /vue/ conf ig/panels . fp . tool to the
/ HameDirectory/ . vue directory. Give the new file write permission.
• Edit the new file to add or remove controls.
• Double-click EditVuewmrc in the System_Admin subdirectory of
the General Toolbox. This opens your personal Workspace Manager
configuration file (/ HameDirectory/ . vue/vueliJl1lrc) for editing.
• Edit vueliJl1lrc to include the new file by replacing the line that includes the
system subpanel file with a line that includes the new file.
INCLUDE

23-14

Customizing HP VUE Lite
Adding Applications and Utilities to HP VUE Lite

{

/ HomeDirectory/ . vue/fp. tool
}

Example: Adding an Action to the Tools subpanel
The action ChangePassword is built into HP VUE. You want to add it to the
Tools subpanel. Assume your home directory is /users/tim.
Create a personal
'fp.tool' file

1. Copy /usr/vue/config/panels/fp. tool to
/users/tim/ . vue/fp . tool. Give the new file write

permission.
2. If /users/tim/ . vue/vuewmrc doesn't already exist, create it by
copying /usr/vue/config/sys. vuewmrc and giving the new file write
permission.
3. In vuewmrc edit the line that includes fp. tool:
INCLUDE
{

"/usr/vue/config/panels/fp.tool"

to include the personal file instead. Save the file.
Add the control to
'fp.tool'.

4. Open /users/tim/ . vue/fp. tool and add the new control to the
subpanel box:
BOX ToolsSubpanel
{
TY~E

subpanel

CONTROL

Password

}

5. Add the control to the bottom of the file.
CONTROL Password
{

TYPE

button

23-15

Customizing HP VUE Lite
Adding Applications and Utilities to HP VUE Lite

LABEL
PUSH_ACTION
HELP_STRING

"Change Password"
f.action ChangePassword
"This control runs the utility for changing your password."

}

6. Save fp. tool.
Restart the workspace
manager

7. Choose Restart Workspace Manager from the Workspace menu.

To use Create Action in HP VUE Lite
Start Create Action

1. Choose Create Action in the Tools subpanel.

Supply the required
information

2. In the Name field, type a unique name for the action.
3. In the Command Line field, type the command to start the application.
Type the command exactly the way you would type it in a command line,
except that, where you would type a file name, substitute $n, where n is
an integer. Here are some example command lines:
emacs
bitmap $1
diff $1 $2
lp -oraw $1

4. Use the Window Type options menu to select how the action's output
will be displayed:
X Windows

The application creates it's own window.

No Output

The command has no display output.

Terminal

The application runs in a terminal emulator
window. You want to keep the terminal
emulator running until you explicitly close it.

Terminal (auto-close)

The application runs in a terminal emulator
window. You want the terminal emulator
window to close when you exit the application.

23-16

Customizing HP VUE Lite
Adding Applications and Utilities to HP VUE Lite

Supply a prompt for
data

5. If the command takes a data file (the Command Line contains $1), type
the text of the prompt into the Filename Prompt field. Leave this field
empty if the command does not take a data file.

Supply optional
information

6. In the Description field, type the item help for the action icon. Press
(Enter) to wrap text to the next line in the text box. The newline
characters will be ignored.
7. If the action is to be used only in HP VUE Lite, leave the Large Icon and
Small Icon fields empty.

Store the action

8. Choose Apply. A dialog box appears telling you the name of the database
file created for the new action, and the system is busy momentarily as
the database is reread.
9. If the action has been successfully created, choose Close.

Make the new action
available

10. If the action is used in the Front Panel, choose Restart Workspace
Manager from the Workspace menu.
A new action definition takes effect:
• When the application that uses it (for example, the Workspace Manager) is
restarted.
• Or, when the user logs out and back in.

You can use Create Action to create actions that execute local applications.
More complex actions are created manually in a database configuration file.
See Also

• "Creating Actions Manually" in Chapter 21 covers creating actions by
editing a database file.

23-17

Customizing HP VUE Lite

Adding Applications and Utilities to HP VUE Lite

To make a system-wide action in HP VUE Lite with
Create Action
1. Create the action using the Create Action utility. When you apply the
action, make note of the file to which the definition is saved.
2. Log in as root.
3. Copy the definition file to /usr/vue/config/types.
The action can now be used in a system-wide Front Panel control.
See Also

• "To use Create Action in HP VUE Lite"

To run an action from the command line
• In a Terminal Emulator window, execute:
vueaction action_name

The vueaction utility lets you run an action without adding it to the Tools
subpanel.
Example

You can use the built-in EditResources action to change resources:
1. Execute:
vueaction EditResources

Your resources will be displayed using your chosen editor. (If your editor
users its own window, two windows will be opened-one for your editor,
and a Terminal Emulator window. You can ignore the terminal window.)
2. Edit your resources and save the file.
3. Close the window containing the editor. Your resources will automatically
be written to your resource database.

23-18

Customizing Workspace Manager

Workspace Manager controls how items on the screen look and behave, and
how they respond to input from the mouse or keyboard. You can extensively
customize most features, including:
• The number and appearance of the workspaces.
• The appearance of windows and icons in the workspace.
• The appearance and contents of the Front Panel
• Mouse and keyboard actions.
• Workspace and menu button menus
Many of these can be changed with Style Manager. Style Manager is able
to make often-used changes quickly, with little effort on your part. Other
resources must be set manually.
The HP VUE Workspace Manager is vuewm. It is based on the OSFlMotif
Window Manager.
See Also

• Refer to the vuewm man page for a complete list of resources.
• Chapter 9 explains using Style Manager
• Chapter 25 explains when and where to specify resources.

24-2

Workspace Manager Configuration File

Workspace Manager gets information about the Front Panel, window menus,
workspace menus, button bindings, and key bindings from a resource file.
sys.vuewmrc

This file contains the system-wide default values for
the window manager features. This file is shipped
with HP VUE. Located in the /usr/vue/ config/
directory.

vuewmrc

A personal version of sys . vuewmrc. This
file is used if you want to change anything in
the sys . vuewmrc file. It is located in your
HomeDirectory/ . vue/ directory.

If your vuewmrc exists, HP VUE uses it, otherwise HP VUE uses
sys. vuewmrc.

To edit vuewmrc
1. Execute the EditVuewmrc action in the System_Admin subdirectory of the
General Toolbox.
(In HP VUE Lite, execute vue act ion Edi tVuewmrc.)
If you already have a personal vuewmrc file, it is loaded into the editor. If

not, sys. vuewmrc is copied to vuewmrc, which is then loaded into the
editor.
2. Edit the file.
3. Exit the editor. The file is saved as your personal vuewmrc, regardless of
its original source.

24-3

Customizing Workspace Manager
Workspace Manager Configuration File

To include other files in vuewmrc
l. Use the EditVuewmrc action to open an editor containing your vuewmrc

file.
2. Add include statements at the appropriate locations within the vuewmrc
file.
3. Exit the editor.
4. Choose Restart Workspace Manager from the Workspace menu.
The syntax for include statements is:
include
{

iJle
}

The included file must contain an entire panel, menu, box, or control. The
include command cannot be imbedded in existing definitions.
Menus, button, boxes, or controls described in included files are used in the
same manner as those items described within the vuewmrc file.
Example

A file named mymenu in the users/ ellen/ directory contains the following:
Menu MyLittleMenu
{

"Little Menu"
"Refresh Screen"
"Restart Workspace Manager"

f.title
f.refresh
f . restart

}

The vuewmrc file contains the following lines. They could be placed
anywhere in the file, but locating them with the other menu descriptions is
best.
include
{

/users/ellen/mymenu

24-4

Customizing Workspace Manager
Workspace Manager Configuration File

The following button mapping, also in vuewmrc, displays mymenu when
button 3 is pressed and the default menu when button 1 is pressed.

root
root

f.menu
f.menu

VueRootMenu
MyLittleMenu

This menu is displayed when button 3 is pressed.

24-5

Customizing Workspaces

The default HP VUE configuration provides six workspaces. The default HP
VUE Lite configurations provides four workspaces. You can add additional or
remove workspaces, or change the appearance of any workspace.

To customize backdrops
1. Create a directory for your backdrop bitmaps.
2. Create a subdirectory named Color for backdrop pixmaps.
3. Create a symbolic link between your new bitmap directory and the HP
VUE backdrops by executing:
In -s /usr/vue/icons/Vuebackdrops/* yourLnrecwry

4. Create a symbolic link between your new pixmap directory, Color, and
the HP VUE backdrops by executing:
In -s /usr/vue/icons/Vuebackdrops/Color/* yourLnrecwry/Color

5. Use the EditResources action to change the backdropDirectory resource
to use your directory.
*backdropDirectory:

yourLnrectory

6. Create your bitmap files in your directory.
7. Create your pixmap files in your new Color subdirectory.
8. Choose Restart Workspace Manager from the Workspace menu.
9. Restart Style Manager by clicking the Style Manager control.
The default HP VUE backdrop images are in the
/usr/vue/icons/Vuebackdrops directory. Once you change the
backdropDirectory resource, backdrops in the default directory will not be
available unless you link them to your directory.

24-6

Customizing Workspace Manager
Customizing Workspaces

The custom backdrop appears in the Backdrop Dialog.
See Also

• "Where to put backdrop image files" in Chapter 16 explains Icon Editor and
more about these directories.

To make a "deep" backdrop
1. Issue the following command in the directory you use for custom
backdrops:
In -s backdrop deepbackdrop

2. Restart Style Manager by clicking on the Style Manager control.
3. Choose Restart Workspace Manager from the Workspace menu.
The "deep" backdrop is a series of concentric borders that gives the
impression of depth. You can combine this feaature with any other backdrop.
The second file name in the link must begin with deep.
Both names appear in the list of backdrops. You can select the original
version of the backdrop or the version with the deep border around it.

24-7

Customizing Workspace Manager
Customizing Workspaces

Example

The following line provides a border around a backdrop named "bigV":
In -s bigV.bm deepbigV.bm

The deep backdrop can be combined with other backdrops.

To display the root window in a workspace
• Select "NoBackdrop" in Style Manager's Backdrop dialog.
In HP VUE, the root window is the window behind the workspace backdrops.

Ordinarily, the root window is completely obscured by the backdrops.
"NoBackdrop" creates a transparent backdrop that allows you to see the root
window.
xsetroot

The xsetroot client allows you to set colors and bitmaps for the root
window, for instance:
xsetroot -bitmap /users/eIIen/bitmaps/bigV

tiles the root window with the specified bitmap. This differs from setting a
backdrop in that no resources are updated, nor does the root window color or
bitmap show in Style Manager's Workspaces dialog.
24-8

Customizing Workspace Manager
Customizing Workspaces

xsetrootgif

If you have the xsetrootgif client, you can display . gif images in the root

window, effectively using the image as a backdrop:
xsetroot -gif myfamily.gif

See Also

• Refer to the xsetroot or xsetrootgif man pages for details about how
to use these clients.

24-9

Customizing Window Components

Frame Elements

You can customize the appearance of the frame which surrounds your
windows:
• Components included in the frame.
• Colors used in the frame.
• Placement of the window.

Icon elements

An icon is used to represent a window that has been minimized. You can
customize icon:
• Appearance
• Location

.;'

Ifvou.us~ .resourgesfo.set ·frameor.iconc(jI~TS, th8s~!.elercnents. are. not.dynamic~

. change whenyoumake a new color selection' with Style Manager.' ..

See Also

that:is:theyvvin.not
. .. . .
. . ...

• The vuewm man page has a complete list of the icon resources.
• Chapter 25 provides information about how and where to set resources.

24-10

Customizing Workspace Manager
Customizing Window Components

To specify window frame components
1. Use the EditResources action to set the value of the clientDecorations
resource for the front panel to all:
Vuewm*FrontPanel*clientDecorations:

all

2. Choose Restart Workspace Manager from the Workspace menu.
A window frame is composed of several elements.

There are several components in a window frame.

where:
Window menu button.
Title bar.
Minimize button.
Maximize button.
Resize handles.
Two resources allow you to specify what components you want in your
window frames:
clientDecoration

Specify components for all windows.

transientDecoration

Specify components for short-lived windows,
such as dialog boxes.

24-11

Customizing Workspace Manager

Customizing Window Components

You can specify the decoration for all clients, or specific ones. (Refer to
"Reference: Workspace Manager" for information about the correct format for
each style.)
These resources can take the following values.
starts with a plus (+), the workspace manager
and adds the ones you specify. If the first item
window manager starts with a complete frame,
specify.

Example

If the first item in the list
starts with no frame elements
starts with a minus (-), the
and removes the elements you

all

Include all frame elements (default value).

none

Include no window frame elements.

±border

Include or exclude border.

±maximize

Include or exclude the maximize button. The title bar is
shown if this button is included.

±minimize

Include or exclude the minimize button. The title bar is
shown if this button is included.

±resizeh

Include the resize border handles. The border is shown if
this element is included.

±menu

Include the menu button. The title bar is shown if this
button is included.

±title

Include the title bar.

To remove the maximize button and resize handles from all client windows:
Vuewm*clientDecoration:

-maximize-resize

To specify only a title bar and menu button for a client named scribe:
Vuewm*scribe*clientDecoration: +menu

See Also

• "Reference: Workspace Manager" has information the formats to use in
specifying Workspace Manager resources .
• Chapter 25 explains where and how to specify resources.

24-12

Customizing Workspace Manager

Customizing Window Components

To set Front Panel decorations
1. Use the EditResources action to set the value of the clientDecorations
resource for the front panel to all:
Vuewm*FrontPanel*clientDecorations:

all

2. Choose Restart Workspace Manager from the Workspace menu.
By default, the decoration for the Front Panel is turned off. By setting
the decoration to all, you allow all legal Front Panel components to be
displayed. For instance, the Front Panel is not resizable, so no resize handles
are shown.
See Also

• Chapter 25 explains where and how to specify resources.

To set subpanel decorations
1. Use the EditResources action to set the value of the
subpanelDecorat ions resource.
2. Choose Restart Workspace Manager from the Workspace menu.
The subpanelDecorat ions resource sets the default subpanel decoration. It
can take the following values:
all

Include all frame elements (default value).

none

Include no window frame elements.

±border

Include or exclude border.

±maximize

Include or exclude the maximize button. The title bar is
shown if this button is included.

±minimize

Include or exclude the minimize button. The title bar is
shown if this button is included.

±resizeh

Include the resize border handles. The border is shown if
this element is included.
24-13

Customizing Workspace Manager
Customizing Window Components

±menu

Include the menu button. The title bar is shown if this
button is included.

±title

Include the title bar.

This resource sets the default subpanel decoration. You can specify
decorations for individual subpanels by allocating them directly:
Vuewm*subpanel*clientDecorat ion:

See Also

value

• Chapter 25 explains where and how to specify resources.

To manually set window frame color
Each palette shown in the Color Dialog box has up to eight color sets within
it. These resources specify which color set is to be used for active and
inactive windows. These resources can be set either manually or through the
Color Dialog Box.
activeColorSetId

Active window frames. The default color set is 1.

inactiveColorSetId

Inactive window frames, menus, dialog boxes, and
icons. The default color set is 2.

For example, the following lines set the active windows to the colors in color
set 3 and the inactive windows to the colors in color set 4.
Vuewm*activeColorSetld:
Vuewm*inactiveColorSetld:

See Also

3
4

• Chapter 25 for how and where to set resources.

24-14

Customizing Workspace Manager
Customizing Window Components

To change icon appearance
This section covers icon bitmaps and labels. For other icon customization,
refer to the vuewm man page.

An icon is composed of three parts.

where:

Icon image

Frame.

(£)

Image.

Label.

To specify a bitmap to use within the icon, either:
1. Create the bitmap.
2. Use the EditResource action to set the iconlmage resource.
3. Choose Restart Workspace Manager from the Workspace menu.
The iconlmage bitmap is specified in relation to the bi tmapDirectory
resource. The syntax is:
Vuewrn*client* iconlrnage :

path/bitmap

where client is:

client class

The class of the client.

client name

The name of the client.

default

To be used when the client doesn't specify an icon.

24-15

Customizing Workspace Manager
Customizing Window Components

The bi tmapDirectory resource specifies the path to the directory
containing the bitmaps you want to use. The default directory is
/usr/include/X11/bitmaps/. If you use custom bitmaps, either
• Specify the complete path name of the bitmap in the iconlmage resource.
This method allows you to continue to use the default bitmaps.
• Change the bi tmapDirectory resource to your bitmap directory.
This method does not use the default bitmaps unless you copy them into
your own directory.
Example

This example assignes a bitmap named "bigV" located in the
/users/ ellen/bi tmaps directory as the icon image to be used if the
application doesn't supply an image.
Vuewm*default*iconlmage:

/users/ellen/bitmaps/bigV

This custom icon replaces the default icon.
Icon label

Use the iconDecoration resource to specify the part of an icon to be
displayed:
label

Label only.

image

Image only.

label image

Both label and image.

label acti velabel

An untruncated active label.

For example, the following line specifies a default decoration of an image and
label, with an untruncated label when the icon is active.
Vuewm*icon*iconlmage:

See Also

label activelabel image

• Chapter 25 explains how and where to specify resources.
• Chapter 16 explains how to change images within the icons.

24-16

Workspace Manager Menus

Workspace Manager has two default menus. You can add others.
The workspace menu

Sometimes called the "root menu". The HP VUE
default button bindings display this menu when
mouse button 1 or 3 is pressed on the backdrop.
The menu is associated with those buttons through
button bindings.

The window menu

The menu displayed by pressing the menu button in
a window's frame, or mouse button 3 at any point
on the window frame. The menu is associated with
the button by the windolNMenu resource.

NOTE
To keep window operation consistent between applications, modify. only the workspace menu.

Workspace Manager menus are defined in

vuewmrc.

24-17

Customizing Workspace Manager
Workspace Manager Menus

Workspace Manager menu syntax
Syntax

Workspace Manager menus have the syntax:
Menu MenuName
{

selectionl [mne11Wnic] [accelerator] junction [argument]
selection2 [mne11Wnic] [accelerator] junction [argument]
selectionn [mne11Wnic] [accelerator] junction [argument]
}

where:

Selection

selection

The text or bitmap that appears on the menu.

mnemonic

A single character that acts as a keyboard shortcut to this
selection when the menu is displayed. It is specified in the
form: _character.

accelerator

A key or set of keys that can be pressed to make this
selection even when the menu is not visible.

junction

The function to be performed when this selection is made.
Refer to the vuewmrc man page for a list of functions.

arguments

Function arguments if the function needs them. Refer to the
vuewmrc man page for more details.

The item which appears on the menu can be either text or a bitmap.
If text is used:

• Multiple word text must be enclosed in quotation marks if it contains
spaces, for example "Raise window".
• Single word text does not have to be enclosed in quotation marks. Either
"Raise" or Raise is valid.
• The underscore character can be used to replace spaces. Either
"Raise_ window" or Raise_window is valid.
If a bitmap is used:

• The path must be preceeded by a
24-18

"@"

sign.

Customizing Workspace Manager
Workspace Manager Menus

Accelerator

Accelerators are in the form:
rrwdifier Keyname

where modifier is a modifier key:
Ctrl

The CTRL key.

Shift

The Caps key.

See Also

• Chapter 25 has information about how and where to change resources.

24-27

Customizing Key Bindings

A keyboard binding, also known as a key binding, associates combination
of keys with workspace manager functions. Key bindings apply to all
workspaces.
Key bindings describe the keys pressed, where the keyboard focus is when
the keys are pressed, and what action takes place when the keys are pressed.

NOT,E
Beeareful about using an existi~g,keYGombinationas}. keyboardbindi~g. For.' example, (Shift 1~l
normally puts, the lett~r 'W', into. your currentwindo\llllfygu.bound. (Shift l®to,. a function; you
,'. wQuldlosgits norm,al. u~,ag,eandc~IVlJaysperformJbatJ4ncti9nwhen (ShiftlfE)yvasenterep.·

Default key bindings

The HP VUE default key bindings are located in the VueKeyBindings section
of the vuewmrc file.
Keys

Action (keyboard focus)

@!) (Menu)

Toggles Workspace Manager between iconified and
restored state. (icon, window, none)

(Shift) (Escape)

Displays window menu. (window, icon)

@!) (Space)

Displays window menu. (window, icon)

@!) (Tab)

Switches keyboard focus to the next window or icon.
(window, icon, none)
Switches keyboard focus to the previous window or
icon. (window, icon, none)
Switches keyboard focus to the next window or icon.
(window, icon, none)
Switches keyboard focus to the previous window or
icon. (window, icon, none)

24-28

Customizing Workspace Manager
Customizing Key Bindings

Puts the top window on the bottom of the stack.
(icon, window, none)
Puts the bottom window on the top of the stack.
(icon, window, none)
Switches keyboard focus to the next transient
window in an application. (window)
Restarts vueliil1Il with the default behavior. (window,
icon, none)

Keyboard binding syntax
The syntax for keyboard bindings is:
Keys
{

KeyBindingSetName
key context junction [argument]
key context junction [argument]
key context junction [argument]

}

where:

key

The modifier and key to which the function is mapped, using
the form "Modifierkeynarne".

context

The element which must have the keyboard focus for this
action to be effective. These can be concatenated together
if the binding applies to more than one context. Multiple
contexts are separated by the" I " character.

junction

A window manager function. Refer to the vueliml man page
for a list of valid functions.

argument

Any window manager function arguments that are required.
Refer to the vueliml man page for details.

24-29

Customizing Workspace Manager
Customizing Key Bindings

Modifiers

Key names

Ctrl

The CTRL key.

Shift

The Caps key.

See Also

• "System resource files" lists the different resource files and when they take
effect.
• Client man pages list the resources available for that client.
• Chapter 9 gives information about how to use Style Manager to customize
HPVUE.

25-3

Setting Personal Resources for an Application

Resources can be changed or specified in several ways (listed in order of
preference) :
Style Manager

You can use Syle Manager to change resources interactively.
This is the easiest method provided the resource is covered by Style Manager.

EditResources action

The EditResources action lets you add, change, or delete current resources
using a text editor, or make a backup file of the current resources.

xrdb client

You can use the xrdb client to load or merge new resources into the current
resources.
You can add resources individually, or from a resource file.
This method allows you to easily add resources, but you must create an
intermediate resource file if you want to change or delete a resource.

Command·line options

This method is the most specific, and allows you to start an application
with exactly the resources you want, without affecting other versions of
that application you might be running. (Refer to "Specifying resources in a
command line" for more information.)

25-4

Using Resources
Setting Personal Resources for an Application

To change resources with Style Manager
1. Click on the Style Manager control in the front panel.

2. Click on the Style Manager component you want to change.
3. Make and save the changes as directed in the component's dialog box.
4. Close the Style Manager component window.

5. Exit Style Manager.
The Style Manager can be used to change resources if the resource in
question is one that Style Manager handles. Not all features handled by Style
Manager involve resources. Additionally, there is usually a larger range of
resources for a particular feature than are managed with Style Manager (for
instance, Fonts). However, Style Manager does handle the most popular
customization features.
The TJri teXrdblmmediate resource determines when new values for color,
fonts, and mouse double-click speed are available. The default value is True.
Value

Description

True

Changes you make using Style Manager take effect in
HP VUE windows and cooperating clients immediately if
possible, or the next time the client is started. This is the
default value.

False

The changes take effect at the beginning of the next session.

If the value is False, you do not see the font or click-speed changes you
make during your current session, even if you start new applications during

the session.

To set resources using the EditResources action
1. Double-click EditResources in the System_Admin subdirectory of the
General Toolbox.

25-5

Using Resources
Setting Personal Resources for an Application

(In HP VUE Lite, execute vueact ion Edi tResources.)
A list of your resources is loaded into a text file.
The editor used is the one specified in your EDITOR enviroment variable.
If you use an editor that opens its own window, you will see an extra

terminal window. Ignore it or close it. It will disappear when you close
the editor window.
2. Edit the file. You can add, edit, or remove resources from the file.
3. Store the edited file.
4. Close the editor window.
5. Restart Workspace Manager.
The EditResources action uses the xrdb client to store the current
resources in a temporary file for editing, then to load that file back into the
RESOURCE_MANAGER property.
If you want to change the editor used to edit the temporary file, either:

• Change the EDITOR environment variable. This is the preferred method.
• Change the EditResources action.
See Also

• Chapter 14 describes environment variables.
• Chapter 19 describes actions.

To create a backup resource file
EditResoureces action

1. Use the EditResources action to display your current resources in an editor
window.
2. Use the feature of your editor which allows you to save the contents under
a different name.

25-6

Using Resources
Setting Personal Resources for an Application

xrdb

• Issue the following command to create a file containing the current
resources:
xrdb -edit filename

To add resources using xrdb
Interactively

1. Execute
xrdb -merge -nocpp

2. Type in resource names and values. Each resource must be on a separate
line.
3. When you've entered all the resources, press

(CTRL)

@) twice.

4. Choose Restart Workspace Manager from the Workspace menu.
Resource file

1. Create a temporary file containing your new resources.
2. Execute
xrdb -merge -nocpp filename

3. Choose Restart Workspace Manager from the Workspace menu.
The -merge option indicates that the resources in the file will be added to the
current resources.
Example

This example shows three resources commonly set by users. The first line
indicates that scrollbars should appear on all hpterm windows. The second
line sets "tty modes" to override the default terminal settings. The third line
establishes four workspaces, named Home, Mail, Sheets, and Edit.
hpterm*scrollBar:
*ttyModes:
Vuewm*workspaceList:

True
erase AH intr AC kill AU start AQ stop AS swtch A@
HomeMail Sheets Edit

25-7

Using Resources
Setting Personal Resources for an Application

See Also

• "Syntax of resource specifications" has information about how to specify
resources.
• Using the X Window System has information about the xrdb client.
• The xrdb man page explains all the options for xrdb.

To replace current resources using xrdb
1. Create a temporary file containing the current resources:
xrdb -edit filename

2. Edit filename.
3. Execute
xrdb -nocpp filename

4. Choose Restart Workspace Manager from the Workspace menu.
The resource values in the file replace the existing current resources.
xrdb -nocpp filename is the same as xrdb -load -nocpp filename. -load
is the default option, and directs xrdb to replace the current resources
(-merge directs xrdb to add the new resources to the current ones).
Example

This example loads a backup file named myresources, overwriting the
current resources.
xrdb -nocpp myresources

See Also

• Using the X Window System has information about the xrdb client.
• The xrdb man page explains all the options.

25-8

Using Resources
Setting Personal Resources for an Application

To delete resources
1. Use the EditResources action to remove the resource from the list.
2. Choose Restart Workspace Manager from the Workspace menu.
When a resource is "deleted", it is removed from the Resource_Manager
property.

25-9

Setting System-wide Resources

If you are administering a system, you can establish resources that will be in

effect when a new user starts HP VUE for the first time. After the first time,
the system-wide resources files are ignored in favor of session-specific files.
The file used depends on whether the session is HP VUE or HP VUE Lite.

To set sys. resources for first session
1. Logon to the system as superuser.

2. Edit /usr/vue/config/sys .resources.
When a new HP VUE user starts the first session, resources are copied from
the sys . resources file into the users's RESOURCE_MANAGER property.
When the session is ended, the RESOURCE_MANAGER property is copied to
1iorneDirectory/.vue/sessions/current/vue.resources. Subsequent
sessions use this vue. resources file.

NOTE
Changes to the sys. resources file may be overwritten by future HP VUE releases.

25-10

Using Resources
Setting System-wide Resources

To set sys.res.lite for VUE Lite
1. Logon to the system as superuser.
2. Edit /usr/vue/config/sys .res .lite.
When a user starts the first HP VUE Lite session, resources are copied from
the sys . res .li te file into the user's RESOURCE_MANAGER property.
When the session is ended, the RESOURCE_MANAGER property is copied to
HomeDirectory/. vue/sessions/lite/vue .resources. Subsequent HP
VUE Lite sessions use this resource file.

NOT E
Changes to the sys. res .lite file may be overwritten by future HP VUE releases.

25-11

Reference: Resources

Syntax of resource specifications
The general syntax for defining resources for a client is:
client*[client components*Jresource:

value

where:
client

can be either the actual client name or the class to
which the client belongs.

client components

allow you to define the resource to specific parts of
the client.

resource

can be either the resource name or class.

Resource files, including the RESOURCE_MANAGER property are text files
and must obey the following rules:
• Each resource specification must be on a separate line. Use the backslash
character (\) to continue a resource onto the next line if necessary.
• Any text to the right of an exclamation mark (!) is treated as a comment.
This is a way to comment partial lines.
• A pound sign (#) in the first column makes the entire line a comment. (Use
the xrdb option -nocpp to avoid it being interpreted as a preprocessor
directive. )
• The resource name is separated from the value by a colon (:) and optional
spaces or tabs.
• Do not have extra spaces or tabs after the value.

25-12

Using Resources

Reference: Resources

Example

The following lines set the background for all hpterm windows to blue, but
the background for the scrollbar part of the window to yellow.
hpterm*background:
hpterm*scrollBar:
hpterm*scrollBar*background:

See Also

blue
True
yellow

• Client man pages for specific client components.

How clients get resources
The X11 Resource Manager is built into HP VUE clients. It automatically
merges together resource specifications from a variety of sources. The
following list shows possible sources of resources in order of precedence; that
is, categories at the top take precedence over those lower down. For instance,
if a resource is specified on both the command line and in an app-defaul ts
file, the value from the command line is used.
command-line options

Many resources can be specified in the command
used to start an application. A command-line option
is equivalent to a client. resource line in a resource
file.
The options apply to only that single instance of the
application.

Xdefaults

This file in your home directory is not read with the
default HP VUE configuration. It was used in earlier
HP VUE releases and in non -HP VUE systems. Refer
to "To integrate XII resource files into HP VUE"
in Chapter 28 for information on how to include
Xdefaul t file resources into HP VUE.
This file applies to individual users.

RESOURCE_MANAGER The general client resources are managed by this
property
root window property on the server.
This property applies to individual users.

25-13

Using Resources
Reference: Resources

user-specific files

Files on the local host describing resources for a
specific client class. These can be personal versions
of system-wide app-defaul ts files or other
personal files. These files can be changed by the
user.
These files apply to individual users.

app-defaul ts files

Files on the local host describing resources for a
specific client class, usually by application. These
files should not be changed by the user.
These files apply to all users on the system.

built-in defaults

Resource default values can be defined in the client
code.
These values apply to all users of the application.

See Also

• man pages for specific clients list the command line options and resources
for that client.
• X Toolkit Intrinsics documentation contains detailed information
about how these different sources for resources are used. Refer to the
XtDisplaylni tialize function.

25-14

Using Resources
Reference: Resources

Scope of resources
You can specify the scope of a resource value, that is, how generally or
specifically the resource is applied. Scope of the customization is determined
by:
• Using names or classes of clients.
• Using names or classes of resources.
• Specifying particular areas of a client.
• Using wildcards in the resource string.
The more specific resources take precedence over the more general resources.
Client names and
classes

Every client has a name and a class. The name defines the client, while the
class categorizes it. The class is more general than the name.
Often, the class and the name are similar, differing only in capitalization. For
example, the client named vuestyle belongs to class Vuestyle.
Resources specified by client name take precedence over those specified by
client class.
You can assign a name to a particular instance of a client, allowing you to
refer to the client by name, client name, or class.
For example, if you have the following as a current resource ...
localTerminal*scrollBar:

True

and issued the following command to start an hpterm window ...
hpterm -name localTerminal

then that hpterm window will have a scroll bar in it.
Resource names and
classes

Resources have both a name and a class. An individual resource name begins
with a lower-case letter, such as foreground. A resource class begins with
an upper-case letter, such as Foreground. The man page for each client lists
the individual resources for that client and the resource class to which each
belongs.
For instance,

25-15

Using Resources
Reference: Resources

*foreground:

blue

sets all foregrounds to blue. However,
*Foreground:

blue

sets all foregrounds to blue and any other resources that have a class of
foreground (such as cursorColor) are also set to blue.
Using wildcards

The asterisk (*) character is a wild card providing resource generality.

Examples

The first line is the most general, and directs that all foreground resources
be white. The second line indicates that the foreground resource for hpterm
windows only be set to yellow, with all the rest left white. The third line
is the most specific and indicates that the foreground for softkeys within
hpterm windows be set to red.
*foreground:
*hpterm*foreground:
*hpterm*softkey*foreground:

System resource files

25-16

white
yellow
red

Using Resources

Reference: Resources

HP VUE Files

Session Manager maintains a number of resource files.
• /usr/vue/config/sys.resources

• HomeDirectory/. vue/sessions/current/vue . resources
• HomeDirectory/.vue/sessions/home/vue.resources
• HomeDirectory/. vue/ host: display/ current/vue. resources
• HomeDirectory/. vue/ host:display/home/vue . resources
The sys . resources file contains system-wide resources. The first time you
login to an HP VUE session, this file is read into the RESOURCE_MANAGER
property. When the session ends, the RESOURCE_MANAGER property
is stored in vue. resources in the appropriate directory, including any
resource changes you made during the session. When the next session is
begun, Session Manager copies the appropriate vue. resources file to the
RESOURCE_MANAGER property.
HP VUE Lite Files

The Lite Session Manager maintains the following HP VUE Lite resource files.
• /usr/vue/config/sys.res.lite

• HomeDirectory/. vue/sessions/Iite/vue.resources
The sys. res .Iite file contains system-wide resources. The first
time you login to an HP VUE Lite session, this file is read into
the RESOURCE_MANAGER property. When the session ends, the
RESOURCE_MANAGER property is stored in the vue. resources file,
including any resource changes you made during the session. When the next
HP VUE Lite session is started, Session Manager copies the vue. resources
file to the RESOURCE_MANAGER property.
If you want to change these HP VUE resource files:

• Refer to "Setting System-wide Resources" for information about setting
sys.resources.
• Refer to "Setting Personal Resources for an Application" for information
about changing resources during a session.
app·default files

Many clients (including HP VUE) provide files with resources to be used by
just that client. These files should not be changed by the user.

25-17

Using Resources
Reference: Resources

• HP VUE default files are located in the /usr /vue/ app-defaul ts
directory.
• Non-HP VUE application default files are in the /usr/Iib/X11/appdefaults directory.
The entries in an app-defaults file are equivalent to a Class *resource entry
in the RESOURCE_MANAGER property.

Personal resource files
You can have personal resource files, which apply only to your sessions, and
which you can change.

NOTE
Generall\S it· is better. to load these files into theRESOURCL MANAGER property, and· manage the
resources through normal HP VUE processes than to force HP VUE to use them as separate files .
...

Personal app·defaults
files

If you want to override values in the system app-defaul ts files, do one of

the following:
1. Use the EditResources action to update the current resources with the
resource to be overridden.
2. Create your personal app-def aul ts file:
a. Copy the app-defaul ts file to your home directory, using the same
name. For example, /users/ eIIen/XCIock.
b. Edit the file.
3. Choose Restart Workspace Manager from the Workspace menu.

25-18

Using Resources
Reference: Resources

The resource is now specified in two places: the the RESOURCE_MANAGER
property and the app-defaults file. Current resources in the
RESOURCE_MANAGER property take precedence, so it is the value used.
Temporary or backup
files

When you are making many changes to your current resources, it is a good
idea to save the original set of resources in a backup file in case the changes
don't work the way you planned:
To store your current resources, execute:
xrdb -edit filename

Xdefaults

Xdefaul ts is a resource file that is used extensively in the X Window

System, but not by HP VUE. In the default HP VUE configuration, it is
ignored.
If you have an Xdefaults file from a previous HP VUE installation or X

Windows environment, and want to use those resource values in your current
environment, load the contents of Xdef aul ts into the current resources.
(Refer to "To integrate XII resource files into HP VUE" in Chapter 28.)
The XENVIRONMENT environment variable determines if an Xdefaul ts
file will be read. If you must use the Xdefaul ts file, refer to the Using
the X Window System manual for more information about setting the
XENVIRONMENT environment variable.
Loading personal files
automatically

If you have personal resource files other than personal app-defaul ts files,

you should use the normal HP VUE processes to load the resource values into
the current resources.
HP VUE loads personal resources files at the start of each session, depending
on the values of the XUSERFILESEARCHPATH enviromnent variable and
the XAPPLRESDIR environment variable. Refer to the Using the X Window
System manual or an Xt Intrinsics programming manual for information about
how to set and use these environment variables.

25-19

Using Resources
Reference: Resources

The RESOURCE_MANAGER property
The RESOURCE_MANAGER is a property of the root window. HP VUE uses
the RESOURCE_MANAGER property to describe all resources that are not set
to their default values.
There are several ways that resources are loaded into the
RESOURCE_MANAGER property:
• Session Manager automatically loads resources from its saved session files
at the start of a new session, and stores resources at the end of a session.
• You may add to or modify the RESOURCE_MANAGER property using Style
Manager during a session.
• You may add to or modify the RESOURCE_MANAGER property using the
EditResources action during a session.
• You may add to or modify the RESOURCE_MANAGER property using the
xrdb client during a session.
Changes made during a session using xrdb are not retroactively effective, but
apply to any new clients or processes started after the change.
Changes made with Style Manager may be written to the
RESOURCE_MANAGER property immediately or at logout depending on the
value of the Vuestyle*wri teXrdbImmediate resource.

Specifying resources in a command line
Most clients allow you to specify resource values on the command line used to
invoke the client. The value is good only for that one instance of the client.
If you use the client often and you want the resource used each time, add it
to your current resources.
A command line option is equivalent to a client. resource line in a resource
file.

25-20

Using Resources
Reference: Resources

Not every command-line option has an associated resource. However, by
using the -xrm option, any resource can be specified on the command line.
If you save a session while the client is still running, HP VUE saves the
command line so that the client will appear in the next session with the

correct options.
Example

The following line starts a single hpterm window with the foreground and
background colors reversed:
hpterm -reverse

The following line also starts a single hpterm window with colors reversed,
but uses the -xrm option to set the resource directly:
hpterm -xrm "*reverseVideo:

True"

The following line in a resource file means that every hpterm window will
use reverse colors:
hpterm*reverseVideo:

True

Resources and cached clients
Resource changes made to applications do not take effect until the client is
restarted.
However, certain HP VUE applications started from Workspace Manager
are "cached", that is, they may be running but not mapped to the display.
Closing these applications simply unmaps them from the display, but does not
end the application. They are not ended until the user logs out or ends them
with a kill command.
Examples of cached applications are Help Manager and File Manager.
Terminal emulator windows started from the front panel or as part of the
session start-up procedure are also cached.
Resource changes for cached applications do not take effect until the
application is killed and restarted or the current session is ended and a new
one begun.

25-21

Using Resources
Reference: Resources

:,Fi;)pt;< pelotj arid

·~AitRlic~tion Re;sburc~s
~>'

' , : ./'

"~f,

-'.,

:~':'

Font, Color, and Application Resources

HP VUE allows you a wide range of colors and fonts to use in your display.
While the simplest method of changing these resources is to use Style
Manager, there are additional font and color resources you can customize.
See Also

• Chapter 9 for information about how to use Style Manager.
• Chapter 25 for details about how and where to specify the resources
mentioned here.
• Using the X Window System explains fonts and colors in more detail.

26-2

Managing Fonts

Using Style Manager's Font dialog box, you can select the size font you want
for all your applications.
You can specify fonts on the cormnand line or using resources to:
• Set font resources for individual applications.
• Assign different fonts to be used by the Fonts dialog box.
A font is a type style in which text characters are printed. HP VUE includes
a variety of fonts in different styles and sizes.
A bitmapped font is made from a matrix of dots. The font is completely
contained in one file. Many files are needed to have a complete range of sizes,
slants, and weights.
The scalable typefaces are defined by a file containing a mathematical
outline used by the system to create a bitmapped font of a particular size,
weight, or slant. Only one "master" file is needed, but it can provide fonts
customized as much as you need.
Fonts are specified as values of resources and as parameters to cormnands.
The X Logical Font Description (xlfd) name is the method by which a desired
font is requested. The system finds the font that best matches the description
it was given.
See Also

• "To select a font size" in Chapter 9 explains how to use the Fonts dialog
box in Style Manager.
• Chapter 25 explains how and when to set resources.

To set HP VUE font resources
The Style Manger Font Dialog lets you set fonts for text entry, labels, and so
on. A selection of up to seven sizes is presented.

26-3

Font, Color, and Application Resources
Managing Fonts

Set by Font Dialog

A selection in the Font Dialog chooses two fonts. Samples of each are shown
in the Font Dialog.

The Font Dialog shows two fonts.

CD SystemFont This font is used for system areas, such as menu bars, menu
panes, pushbuttons, toggle buttons, and labels.
@UserFont

This font is used for text entered into windows.

When a font is selected, the following resources are written to the
RESOURCE_MANAGER property:
• The following resources are set to SystemFont:
FontList

Displayed in system areas of HP VUE clients and other
clients created using the OSFlMotif toolkit.

• The following resources are set to User Font :

Used by Font dialog

Font

General user font for clients.

XmText*FontList

Displayed in text entry boxes.

XmTextField*FontList

Displayed in text entry boxes.

The fonts used for each selection in the Font Dialog Box are specified in the
/usr/vue/app-defaults/Vuestyle resource file. Up to seven sizes can be
specified.
NumFonts

26-4

The number of font sizes presented in the Font
Dialog Box.

Font, Color, and Application Resources
Managing Fonts

SystemFont [1-7J

Up to seven resources assigning a specific font to a
Font Dialog box selection for SystemFont.

UserFont [1-7J

Up to seven resources assigning a specific font to a
Font Dialog Box selection for UserFont.

NOTE
The default fonts for these resources have been carefully chosen to be easy to read on each type of
display. Generally,. if you want a specific font for an application, you should set it with an application
font. resource. rather than changing these HP VUE fonts.

If you change one of these fonts, use all 14 field separators (-). You can use

wild cards for the field itself, but do not combine fields with wild cards. For
bitmap fonts, you need to provide a value for the pixel size field. For scalable
typefaces, you need to provide a value for the point size field.
See Also

• Chapter 25 for information about how and where to specify resources.

To list available fonts
• Execute
xlsfonts [-optionsJ [-fn patternJ

A list of xlfd names and alias names available on your system is produced.
Bitmap fonts show values in all 14 xlfd fields. Scalable typefaces show zeros
in the PizelSize, Point Size, ResolutionX, and ResolutionY fields.
If you have many fonts on your system, the list could be long. You can check
for specific fonts by using the pattern-matching capability of xlsfonts. Use

wild cards to replace the part of the pattern you are not trying to match.

26-5

Font, Color, and Application Resources

Managing Fonts

If xlsfonts lists only three fonts, your font path is not including the HP VUE

fonts. Type the following command to include the HP VUE fonts into your
available fonts:
xset fp default

Example

This command ...
xlsfonts -fn "*bitstream*"

... displayed this list of all fonts on the system with "bitstream" somewhere
in their xlfd names.

'xlsfonts' displays all fonts available to you.
See Also

• xlsfonts man page for a list of the options available.
• Using the X Window System explains font alias names and the xset client.

To specify fonts on the command line
• The -fn command line option allows you to specify a font for a specific
client.

26-6

Font, Color, and Application Resources

Managing Fonts

Example
xfd -fn "*bitstream.-charter-medium-r-normal-8-88-75-75-p-45-iso8859-1"

The X Logical Font Description (xlfd)
A font is specified by listing 14 different characteristics, separated by dashes
(-). This is called the X Logical Font Description (xlfd). In some cases, a
property in the list can be replaced by a "*,, wild card, and a character
within a property can be replaced by a "?" wild card.
The form of the property string specification is:
FontNameRegistry-Foundry-FamilyName- WeightNameSlant-SetwidwthName-AddStyleName-PixelSizeFbintSize-ResolutionX- ResolutionY- SpacingAverage Width- CharSetRegistry- CharSetCoding"
II

where:
FontNameRegistry

A string identifying the authority that registered the
font.

Foundry

A string identifying the font designer.

FamilyName

A string identifying the trademarked commercial
name of the font.

WeightName

A string giving the relative weight of the font, such
as bold.

Slant

A code describing the direction of slant.
R

Roman (no slant)

Italic (slant right)

Oblique (slant left)

Reverse Italic (slant left)

Reverse Oblique (slant right)

26-7

Font, Color, and Application Resources

Managing Fonts

Example

SetwidthName

A string describing the width, such as compressed or
expanded.

AddStyleName

A string providing any additional information needed
to uniquely identify the font.

PixelSize

An integer giving the size of an em-square in pixels.

PointSize

An integer giving the size of an em -square in
decipoints.

ResolutionX

An integer giving the horizontal resolution in pixels.

Resolution Y

An integer giving the vertical resolution in pixels.

Spacing

A code specifying the spacing between units.
M

Monospace (fixed pitch).

Proportional space (variable pitch).

Character cell.

Average Width

An integer giving the average width in III Oth pixels.

CharSetRegistry

A string identifying the registration authority that
has registered the font encoding.

CharSetEncoding

A string identifying the character set within the
specified registry.

The following xlfd name:
*-bitstream-charter-medium-r-normal--8-80-75-75-p-45-iso8859-1

Describes a font named "charter" made by Bitstream and registered with
IS08859-1 standard. It is medium weight, no special slanting, and normal
width. The font is proportional, with an em-square box of 8 pixels (or 8.8
points). The horizontal and vertical resolution are both 75 pixels. The
average width of a character is 45 III Oths pixels.
Parts of this string can be replaced by wild cards. The system uses the first
font it finds that matches the parts you have specified.
If all you want is an 8-pixel "charter" font, you could use:

26-8

Managing Colors

You can color your display through two mechanisms:
• Style Manger color allocation.
You can dynamically change color for HP VUE applications and other
cooperating applications.
The foreground and background colors set by Style Manager are
available to non -cooperating applications.
• Directly setting a color resource for an application.
You can set color resources through resource files, xrdb, or command line
arguments.
Use this method when a specific color is needed for an element of an
application, regardless of the current palette.
HP VUE provides palettes of pre-defined colors. The number of colors in a
palette depends on the type of display you have.
For a client to respond to Style Manager color changes, the following must be
true:
• The client must be an HP VUE client or an HP aSF /Motif 1.1 client.
Clients written with other toolkits cannot change color dynamically in
response to Style Manager changes. Color changes do not take effect until
the client is restarted.
• There must be no other specific color resources applied for the client. This
includes user-specified resources, app-defaults, and resources built into the
application.
Any colors specifically given in resources are not changed in response to
Style Manager changes.
Clients can specify special resources to use certain colors within an HP VUE
palette.
See Also

• "Setting Personal Resources for an Application" in Chapter 25 for
information about checking and setting resources.
• Chapter 9 covers how to change color or add palettes using Style Manager.

26-9

Font, Color, and Application Resources
Managing Colors

To set palettes
• Use the Style Manager Color dialog to add, delete, or change color palettes.
A palette consists of up to eight color sets. The number of color sets is
determined by the colorUse resource. (Refer to "To set the colorUse
resource" .)
The Style Manager's Color Palette dialog box shows the name of the selected
palette and a button showing the background color for each color set within
the palette. You can use this dialog box to add palettes or change color sets
within a palette.

Use the Color Dialog to select and display palettes.

where:
Palette names.
Background color of the colorsets within the chosen palette.
A file exists for each palette. The paletteDirectories resource specifies
the directories containing palette files. By default, this resource contains:
26-10

Font, Color, and Application Resources
Managing Colors

• /usr/vue/palettes contains files for the palettes shipped with HP VUE.

• / HomeDirectory/ . vue/palettes contains palettes you create or modify.

When you select a palette with Style Manager, a resource is written to your
current resources in the RESOURCE_MANAGER property. Session Manager
uses this resource to restore the current palette at the beginning of the next
session. If the colorUse resource value is B_W, the palette resource is
monochromePalette, otherwise the palette resource is colorPalette.
See Also

• "Customizing Screen Appearance" in Chapter 9 for information about
adding or changing palettes and color sets.

Color sets
A color set is composed of up to five colors. Each color set is represented by
a color button in the Style Manager Color dialog (showing the background
color). These five colors represent the following display component resources:
foreground

The foreground of an application window or window
frame. It is always black or white. This is generally
used for text within windows and titles.

background

The background of the application controls and the
window frame.

topShadowColor

The color of the top and left bevels of application
controls (such as push buttons) and window frames.

bottomShadowColor

The color of the bottom and right bevels of
application controls and window frames.

selectColor

The color of certain controls, such as depressed
buttons, editable areas, and scroll bars.

When a palette is selected, the foreground and background resources are
written to the RESOURCE_MANAGER property. Non-HP VUE applications
can access the new value the next time they are started.

26-11

Font, Color, and Application Resources
Managing Colors

To set the colorUse resource
1. Click the Style Manager control on the front panel.
2. Click the Color Icon.
3. Click the HP VUE Color Use button.
The colorUse resource configures how many colors HP VUE uses.

Control the number of colors HP VUE uses with the Color Use Dialog.

The "default" value of the resource is determined based on the type of
display you have. The value of this resource affects the number of colorsets
in a palette. Other resources affect the number of colors used to make
shadows.
The value of the colorUse resource also affects whether you can use
multi-color icons.
Value

Description
monochrome displays (1-3 color planes)
number of color sets: 2
maximum number of colors: 2
default number of colors: 2
no multi-color icons

26-12

Font, Color, and Application Resources

Managing Colors

LOW_COLOR

low-resolution displays (4-5 color planes)
number of color sets: 2
maximum number of colors: 12
default number of colors: 8
no multi-color icons

MEDIUM_COLOR

medium-resolution displays (6 color planes)
number of color sets: 4
maximum number of colors: 22
default number of colors: 22
no multi-color icons

HIGH_COLOR

high-resolution displays (7 or more color planes)
number of color sets: 8
maximum number of colors: 42
default number of colors: 42
multi -color icons allowed

The "default" choice allows the most display-independence, that is, you need
not reset the colorUse resource when you run on other displays. HP VUE
chooses the correct value for that display.
Multi-color icons use additonal colors.
See Also

• "Getting Started with Icon Editor" in Chapter 16 for information about
creating and using multi-color icons.

To set pixmap shadows
l. Use EditResources action to set the shadowPixmaps resource.

2. Choose Restart Workspace Manager from the Workspace menu.
Shadow pixmaps create shades of colors without adding additional colors to
the color map. Shadow pixmaps can be used as a tile that provide a visual
texture by "mixing" the background and foreground (black or white) colors
into a color pattern.

26-13

Font, Color, and Application Resources
Managing Colors

The shadowPixmaps resource directs HP VUE to replace the two shadow
colors with pixmaps. Pixmaps use combinations of the foreground and
background colors, thereby reducing the number of needed colors by two.
Value

Description

True

HP VUE creates a topShadoliJPixmap and
bottomShadowPixmap to use instead of the shadow colors.

False

topShadoliJColor and bottomShadowColor from the

palette are used.
The default value for shadoliJPixmaps depends on the colorUse resource
you have.

See Also

Display

Default value

B_W

True

LOW_COLOR

True

MEDIUM_COLOR

False

HIGH_COLOR

False

• Chapter 25 for information about how and where to set resources.

To set the foreground color
• Use the EditResources action to set the foregroundColor resource.
The foregroundColor resource specifies how the foreground resource is
configured in a palette.
White

foreground is set to white.

Black

foreground is set to black.

Dynamic

foreground is set to either black or white, depending on
the value of background. For instance, white letters on a

yellow background would be hard to read, so the system
chooses black.

26-14

Font, Color, and Application Resources
Managing Colors

If foregroundColor is set to either Black or White, the number of colors in

the color set is reduced by 1, and the foreground will not change in response
to changes in the background color.
The default value for foregroundColor is Dynamic, except where the value
of colorUse is B_ W.
See Also

• Chapter 25 for information about how and where to set resources.

To use dynamic color
1. Use the EditResources action to set the dynamicColor resource to True.
2. Choose Restart Workspace Manager from the Workspace menu.

The dynamicColor resource controls whether applications change color
dynamically, that is, the clients change color when you switch palettes.
Value

Description

True

Clients change color when a new palette is selected. This is
the default value.

False

Clients do not change color. Any new client started after the
new palette uses the new colors, but already- running clients
do not change.

Clients that cannot change colors dynamically (for instance, if a color was
specified in the command line) allocate different cells in the color map than
clients that can change colors dynamically, even if you see the same color.
Setting dynamicColor to False can reduce the number of colors your
display must manage, since all clients can share the same color cells.
A client willing to dynamically change color can either specify no color
resources or map specific color sets to special resources.

26-15

Font, Color, and Application Resources
Managing Colors

See Also

• Chapter 25 for information about how and where to set resources.

To compute number of colors a palette uses
1. Multiply the number of color sets in the palette by the number of colors
within each color set.
2. Add 2 (for black and white).
The minimum number of colors used by Style Manager is the number of
colors used by a palette. This number depends on the values for these
resources:
• colorUse (Refer to "To set the colorUse resource".)
• shadolNPixmaps (Refer to "To set pixmap shadows".)
• foregroundColor (Refer to "To set the foreground color".)
• dynamicColor (Refer to "To use dynamic color" .)

The following table shows the maximum number of colors for each type of
display:
B_W

2 (foreground and background only)

LOW_COLOR

12 (2 color sets times 5 colors plus black and white).

MEDIUM_COLOR

22 (4 color sets times 5 colors plus black and white).

HIGH_COLOR

42 (8 color sets times 5 colors plus black and white).

However, with the following configuration ...
*colorUse:
*shadowPixmaps:
*foregroundColor:

MEDIUM_COLOR
True
White

then you would have only 10 colors in your palette: 4 color sets times 2
colors in each set (background and selectColor) plus black and white.
If you had the following configuration ...
*colorUse:
*shadowPixmaps:

26-16

MEDIUM_COLOR
False

Font, Color, and Application Resources

Managing Colors

*foregroundColor:

Dynamic

and used the same color for the two shadow colors, you would have 18 colors
in your palette (4 color sets bmes 4 colors in each set plus black and white).

To limit the number of colors
To limit the number of colors HP VUE uses, you can do one of the following:
• Let Style Manager handle color resources as much as possible. Limit client
color resource specifications in resource files.
• Change the colorUse resource to a lower-resolution value. (Refer to "To
set the colorUse resource" .)
• Replace the top and bottom shadow colors with pixmaps using the
shadowPixmaps resource. (Refer to "To set pixmap shadows".)
• Set the foreground color to White or Black using the foregroundColor
resource, rather than computing it dynamically. (Refer to "To set the
foreground color" .)
• Tum off dynamic color allocation for applications using the dynamicColor
resource. (Refer to "To use dynamic color".)

To map color to screen elements
1. Use the EditResources action to set the color set ill resources.
2. Choose Restart Workspace Manager from the Workspace menu.

26-17

Font, Color, and Application Resources
Managing Colors

The Color Dialog shows color sets.

shows the palette selected.

shows the color sets within that palette, sets 1 through 4 on the top
line and sets 5 through 8 on the bottom line.

Color sets are mapped to various display elements through resources. HP
VUE makes the following assignments:
Resource

Display element (default color set)

activeColorSetld

active frame color (1)

inactiveFrameColorld

inactive frame color (2)

primaryColorSetld

application's main background areas (3)

secondaryColorSetld

application's menu bar, menus, and dialog
boxes (4)

Applications are color-coded through the primaryColorSetld and
secondaryColorSetld values, so that it is easy to tell which window
a dialog box is associated with, for instance. HP VUE uses the same
primaryColorSetld for its clients, but provides client-specific
secondaryColorSetld values.

26-18

Font, Color, and Application Resources
Managing Colors

HP VUE client

Secondary Color Set ID

File Manager

Style Manager

Vue ico n

Vuepad

Coloring display elements with color set ill's allows the element to change to
the new color scheme when a new palette is selected with Style Manager.
Example

The following line shows how you would group all hpt erm windows by using
color set 8 for their primary color.
hpterm*primaryColorSetld:

See Also

• Chapter 25 for information about how and where to specify resources.

How colors are specified
Colors can be directly specified in either of two ways:
• Name
• rgb value
Style Manager uses the rgb value of colors it specifies. If you set a color
resource directly, you can use either method.
Color name

The file /usr/lib/X11/rgb. txt lists all the named colors. These names can
be used whenever a color is specified. There are many more possible colors
than have names, however.
For example,
Vuewm*hpterm*iconlmageBackground:

DarkSlateGrey

26-19

Font, Color, and Application Resources

Managing Colors

Rgb value

The syntax for rgb numbers is:
#RedGreenBlue

Green, and Blue are hexadecimal numbers, each 1 to 4 digits long,
which indicate the amount of that primary color used. There must be the
same number of digits for each of the primary colors. Thus, valid color values
consist of 3, 6, 9, or 12 hexadecimal digits.

Red,

Style Manager uses rgb values when writing color information to its palette
files.
For example, black can be specified in any of the following ways:
#fff
#ffffff
#fffffffff
#fffffffffffff

26-20

Geometry Resources

The geometry of a window is its size and location. A window has a default
size (set by the application) and position (set by vuewm). You can directly
specify the size or location for an application's windows by specifying a
geometry resource for the application.
The geometry resource has the following syntax:
[widthxheight][±column][±rowj

where:
width

The width in characters (for terminal windows) or
pixels (for other applications).

height

The height in lines (for terminal windows) or pixels
(for other applications).

±column±row

The column and row location in pixels. Plus values
indicate distance from the upper left comer. Minus
values indicate distance from the lower right corner.

These two options can be combined, as shown in the example.
Example

This resource specifies that all hpt erm windows will be created 80 characters
wide and 24 characters high, and be placed at the upper right corner of the
display.
hpterm*geometry:

See Also

80x24-1+1

• Chapter 25 for information about how and where to change resources.

26-21

Style Manager Resources

The componentList resource describes which components appear in the
Style Manager window. All the possible choices appear in the default HP VUE
Style Manager Window.
• Color
• Font
• Backdrop
• Keyboard
• Mouse
• Audio
• Screen
• Vuewm
• Startup

The default componentList resource for HP VUE Lite lists the following
elements:
• Color
• Background
• Font
• Window
To set componentList
resource

Example

1. Use the EditResources action to change the componentList resource.

2. Restart vuestyle.
This list displays only the Color, Background, and Font components of Style
Manager:
componentList:

See Also

Color Background Font

• Chapter 25 for information about checking and modifying resources.

26-22

File Manager Resources

The rereadTime resource sets how often File Manager rereads the open
directory and displays the results in the File Manager window.
The default value is 2, meaning the directory is read every 2 seconds.
You may prefer to have the File Manager window updated less often if your
system is running close to capacity, or if you are doing some activity in
another window which causes numerous temporary changes in the active
directory.
If you want it to be read less often, update the resource with the time in

seconds.
If the value is set to zero, File Manager does not reread the directories. You
must manually reread the directory using the Directory menu if you want an

updated version.
To set rereadTime
resource

See Also

1. Use the EditResources action to specify the rereadTime resource value.
2. Choose Restart Workspace Manager from the Workspace menu.
• Chapter 25 for information about checking and modifying resources.

26-23

Font, Color, and Application Resources
File Manager Resources

Non-English HP VUE Sessions

HP VUE offers a number of capabilities in non-English languages. At the
highest level, you can obtain HP-UX for certain languages with HP VUE
localized as the included user interface.
Since HP VUE is designed with internationalization support as a primary
objective, the user interface can be customized in 8-bit and 16-bit languages.
Various elements, such as screens, default languages, and icons can be
changed to non-English languages. In addition, the menus, online help, and
error messages are localizable and available in some languages.

27-2

Fileset Requirements for Asian Lanuages

The following file sets are required to run HP VUE in Asian languages:
Language

Filesets

chinese-s

NLXII-CHS
CHINESES-XII
NLIO-CHS

chinese-t

NLXII-CHT
CHINESET-XII
NLIO-CHT

japanese

NLXII-JPN
JAPANESE-XII
NLIO-JPN

korean

NLXII-KOR
KOREAN-XII
NLIO-KOR

27-3

Non-English HP VUE Login

Non-English login through HP VUE is easy. However, for the effect to be
noticeable, several key elements should be present. Specific hardware
requirements such as keyboards and printers vary by language, character set,
and country. Software and fonts further increase the effective localization of
your system. To login in a specific language:
1. Use the Options menu on the login screen to select a language.
2. Login normally with your name and password.

27-4

Using a Non-English Terminal Emulator

Successful emulation in any language requires that the specified font be
available. Fonts should reside in the /usr/lib/X11/fonts directory.
To determine if a given language is supported, read the file
/usr/lib/nls/config or check for the language in the Options menu at
login.
With 16-bit languages such as Japanese, Chinese, and Korean, Native
Language Input/Output (NL I/O) must also be installed. Refer to the NL I/O
documentation for information and operating instructions.
There are two hpterm terminal emulators available for use in HP VUE:
• The hpterm that is part of XII Window System R4.
• The hpterm that is part of XII Window System R5. This new hpterm
incorporates the Native Language I/O servers.
See Also

• The Using the X Window System manual contains additional information
for localizing terminal emulators and other X Window applications.
• The NL I/O documentation contains additional information about 16-bit
language capabilities.

To Start a Japanese Terminal Emulator
Since the xterm terminal emulator has very limited language capabilities, this
example uses hpterm.
The assumptions are that the default language is not Japanese, that you
are using the Korn Shell, and that the specified font (jpn.8xI8) is in a
subdirectory of /usr/lib/X11/fonts.
1. From a command line in a Kom Shell terminal window type:
LANG=japanese hpterm -fn jpn.8x18

27-5

Non-English HP VUE Sessions
Using a Non-English Terminal Emulator

In other shells, using the appropriate cormnand, set the value of the LANG
environment variable to japanese for the HP15 character set. Other code

sets use different names.
2. After the new terminal window appears, press the System key to display
the softkey labels.
3. Press F8 (Config Keys) and F5 (Terminal Config).
4. Slowly press key F6 until the label for the softkey changes to Japanese.
5. After the cursor changes back to normal, type date to verify that the
language is Japanese.

To Start a German Terminal Emulator
Since the German language uses 8-bit characters, xterm or hpterm may be
used to emulate a terminal.
1. From a cormnand line in a Kom Shell terminal window type:
LANG=german xterm
In other shells set the value of the LANG environment variable to german

using the appropriate cormnand.
2. If you are using hpterm:
a. After the new terminal window appears, press the System key to
display the softkey labels.
b. Press F8 (Config Keys) and F5 (Terminal Config).
c. Press key F6 repeatedly until the label for the softkey changes to
"Deutsch."
d. After the cursor changes back to normal, type date to verify that the
language is German.

27-6

Non-English HP VUE Sessions
Using a Non-English Terminal Emulator

To use the XII R5 hpterm
To use the Xll R5
hpterm

• Runthescript/usr/bin/X11/hptermR4toR5.

To switch back to the

• Runthescript/usr/bin/X11/hptermR5toR4.

Xll R4 hpterm

CAUTION

You should switch to the XII R5 hpterm only if you require the Native
Language IIO servers and the XII R5 input method protocols (Xsi, Xirnp)
for native language input it uses. Using the XII R5 hpterm reduces system
performance.
Always use the scripts to switch between the XII R4 and the XII R5
hpterms. Manually switching the executables can cause errors that prevent
HP VUE from running properly.

27-7

Using Non-English Data

You can create, read, and print non-English files. You can also give files
non-English names. However, you should use file names containing only
ASCII characters for system administration.

To Create or Edit a File with Non-English Characters
If you have logged in to HP VUE in a specific language, the HP VUE Text

Editor will also be set to that language, so the steps below can be skipped.
If your default language for HP VUE is English and you want to create a file

with anon-English character set, you can still use Text Editor, but you must
invoke a new instance in your target language.
1. In a Terminal Emulator window, set the LANG and KBD_LANG
environment variables to the desired language.

2. In the same Terminal Emulator window, execute:
/usr/vue/bin/vuepad -xrm IIVuepad*fontList: font"
Example

-standAlone

The following commands start Text Editor with the Korean language, using a
Terminal Emulator with Korn Shell.
export LANG=korean
export KBD_LANG=korean
/usr/vue/bin/vuepad -xrm "Vuepad*fontList: kor.8x18" -standAlone

You can now enter Korean characters (using NL I/O) if the specified Korean
font (kor.8x18) is properly installed. You can also use the Text Editor session
to edit a previously created Korean file. The -standAlone parameter is
necessary to ensure that the editor does not default to the language set at HP
VUE login.

27-8

Non-English HP VUE Sessions
Using Non-English Data

To Print a File with Non-English Characters
There are many variables affecting the successful printing of non-English
data. The HP-UX operating system supports printing of all 8-bit character
sets. Printing 16-bit characters requires the NL I/O software and a supported
printer. Consult the NL I/O documentation for specifics. NL I/O supports
printing on various Asian-specific devices, and allows Asian printing on HP
LaserJet printers (models II and newer).

27-9

Non-English HP VUE Customization

HP VUE users can modify certain files to achieve a more customized
appearance for their culture or language.

To Localize the Front Panel
If you are running an HP VUE version that has been localized for your

language, the date and several other elements of the Front Panel should
already appear in that language. To rename a workspace with characters of
your language, simply select the Rename Workspace Control and type the
new name (using NL I/O if necessary).
If you select a language at login for which HP VUE is not fully localized or

installed, the necessary fonts may need to be installed in order to rename the
workspaces with the correct characters.

To Localize Icons
If you want to localize an icon, you will need to edit the icon with the icon

editor and then put the result in the correct directory.
HP VUE uses the following search path to locate localized icons, where:
• language is the value of LANG.
• applications is the application class name.

/ HomeDirectory/bi tmaps
/ HomeDirectory
/usr /vue/ icons/ language/ application
/usr /vue/ icons/ application
/usr/vue/icons/Common
27-10

Non-English HP VUE Sessions
Non-English HP VUE Customization

/usr /lib/X11/ language/bi tmaps/ application
/usr /lib/X11/bi tmaps/ application
/usr/lib/X11/language/bitmaps
/usr/lib/X11/bitmaps
/usr/include/X11/bitmaps
See Also

• Chapter 16 explains how to create your own icons.

Localizing actions and filetypes
The search path for action and filetype definition files includes
language-dependent subdirectories of:
• / HomeDirectory/ . vue/types, the personal database.

• /usr/vue/coniig/types, the general database.
• /usr/vue/types, the built-in general database. These files may be

overwritten by subsequent updates.

27-11

System Administration for NLS

This section has information for system administrators. If you are a typical
user, you should seldom need to use it.
These topics are discussed:
• How HP VUE sets the LANG environment variable and other environment
variables.
• Accessing language-dependent message catalogs and resource files.
• Remote execution in systems on which National Language Support (NLS) is
available.

Setting the LANG Environment Variable
The LANG environment variable must be set in order for HP VUE to use
national language support. Setting LANG causes HP VUE to use the operating
system's language-sensitive routines for character handling.
You can set LANG to any value supported by the operating system. The NLS
directory /usr/lib/nls contains an entry for each supported value. The
HP VUE message catalogs are located in subdirectories of the NLS directory.
Supported languages include simplified and traditional Chinese, French,
C-French, German, Japanese, and Korean.
There are three ways to set LANG for HP VUE:
• By a vuelogin resource in the Xconfig file. The login screen is localized,
and LANG is set for all users. This is the only way to change LANG for all
displays in multiple-display systems.
• From the Options menu in the login screen. The login screen is localized
and LANG is set for the user.
• In the. vueprofile file. The login screen is not localized, and LANG is set

for the user.

27-12

Non-English HP VUE Sessions
System Administration for NLS

Using a Vuelogin
Resource

Setting the language by means of a vuelogin resource has these effects:
• The vuelogin client reads the appropriate message catalog for that
language and brings up the localized login screen.
• The LANG environment variable is set to that language for HP VUE
sessions for all users. (LANG can be set for individual users by an entry in
. vueprofile.)
• The resource should set the NLSPATH environment variable appropriately
for the chosen language. If this is not the case, or if you want to set
NLSPATH yourself, see "Message Catalogs-the NLSPATH Environment
Variable" later in this chapter.
The resource is set by placing the following line in
/usr/vue/config/Xconfig:

Vuelogin . hosLdisplay . language : language
For example, the following line sets LANG to Swedish on display hpcvxpae:O.

Vuelogin.hpcvxpae_O.language: swedish
Setting LANG from the
Options Menu

Setting the lanugage from the login screen Options menu causes HP VUE
to use that value of LANG for the next session. LANG returns to its default
value at the conclusion of the session.

Setting LANG in
.vueprofile

User-specific environment variables for HP VUE sessions can be placed in the
file $HOME/ . vueprofile .
• If you use sh or ksh:
LANG=language

export LANG
• If you use csh:

setenv LANG language

27-13

Non-English HP VUE Sessions
System Administration for NLS

To Set Other NLS Environment Variables
This section covers other NLS environment variables. These variables are not
affected by the vuelogin language resource nor by the login screen option
menu.
• Set them in /usr/vue/config/Xsession to set system-wide variables.
• Set them in $HOME/ . vueprofile for user-specific variables.
In the following examples, %L is translated by the system into the value of the

LANG variable; YeN is translated into the value of the application's class name.
Message Catalogs-The The NLSPATH environment variable determines the paths applications search
NLSPATH Environment for NLS message catalogs. HP VUE clients place NLS message catalogs in
Variable
the NLS directories /usr/lib/nls/$LANG (non-Domain/OS systems) or

/usr/nlslib (Domain/OS). Both LANG and NLSPATH rnust be set in order to
use those message catalogs.

The proper value of NLSPATH depends on whether message catalogs exist for
the current value of LANG.
• To use the message catalogs for the language to which LANG is set, set
NLSPATH to:
/usr/lib/nls/%L/%N.cat:/usr/lib/nls/C/%N.cat:$NLSPATH
• If no message catalogs exist for the language to which LANG is set, set

NLSPATH to:
/usr/lib/nls/C/%N.cat:$NLSPATH
Setting
Language-Dependent
App·Defaults

The default location for the app-defaul ts for HP VUE and X clients
is /usr/vue/app-defaults/%L, where %L is the the value of LANG.
For example, if LANG is set to swedish, then applications will look for
their app-defaults in /usr/vue/app-defaults/swedish. If LANG is
not set, %L is ignored, and applications look for their app-defaul ts in
/usr/vue/app-defaults.

The XUSERFILESEARCHPATH environment variables provides the ability to
change the location of app-defaults. For example, if it were desirable to
move app-defaults to /users, then XUSERFILESEARCHPATH could be set
to /users/ app-defaul ts/%L/%N.
27-14

Non-English HP VUE Sessions
System Administration for NLS

If you set XUSERFILESEARCHPATH in $HOME/. vueprofile, the value

applies to all HP VUE and X clients you run. Non-clients will not find their
resource files unless you link or copy them into the directory specified by
XUSERFILESEARCHPATH.

For additional information about localized resources, refer to the discussions
of the resource database in the Xt Intrinsics documentation.
Setting the KBD_LANG
Environment Variable
,

~he ability to support nativelanguagekeyb()~rdsdependson th~'operating syStem.

systems may not support character s~ts fo'rAsian'
languages.
:p
l

!:"

}~' ,"

<~.

Other operating

HP VUE allows you to override the physical keyboard attached to the HP-HIL.
For example, a USASCII keyboard with KBD_LANG set to czech will behave
like a Czech keyboard.

27-15

Non-English HP VUE Sessions
System Administration for NlS

KBD_LANG can be set after the server has started. A convenient place for
setting the variable system-wide is in /usr/vue/ config/Xsession. The
following lines set KBD_LANG appropriately for languages that require the
keyboard to be remapped. Insert theses lines in Xsessions after the line
export EDITOR LOGNAMEMAIL TERM:
if [ ! -z It$LANG" ]

then
case $LANG in
bulgarian I czech I hebrew
hungarian
japanese I korean I polish
rumanian
russian
I serbocroatian)
KBD_LANG=$LANG
export KBD_LANG;;
chinese-t) KBD_LANG=t_chinese;;
export KBD_LANG;;
chinese-s) KBD_LANG=s_chinese
export BKD_LANG;;

\
\

esac
fi

The NLIO processes for Asian users start only when either the physical
keyboard is Asian or KBD_LANG is set to an Asian language.
language-Dependent
Bitmaps-the
XBMlANGPATH
Variable

The XBMLANGP ATR variable specifies the search path for language-dependent
bitmaps. It lists the paths for bitmaps in this order:
1. User-specific bitmaps.
2. System bitmaps listed in the XmpGetlconFileName (3X) man page.

3. Append:
/usr/vue/icons/

This ensures that you will get the non-localized bitmaps, where necessary.

27-16

Non-English HP VUE Sessions
System Administration for NLS

Other Language-Dependent Resource Files
When LANG is set, HP VUE uses the following language-dependent default
resource files:
• /usr/vue/config/Y.L/sys.session
• /usr/vue/config/Y.L/sys.resources
• /usr/vue/config/Y.L/sys.vueYmrc

Editing in HP VUE
All characters that can be entered from an HP keyboard into a terminal
emulator window can also be entered into HP VUE text entry areas.

Remote Execution and NLS
You can invoke localized HP VUE applications on any remote execution
host that has a similarly localized HP VUE installation. The values of
the NLS-related environment variables on the host that is invoking the
application are passed to the remote host when the application is started.
However, the environment variables do not contain any host information.
Thus, the message catalogs and application resource files must be in the same
locations on both systems unless the $HOME/ . softenv file on the remote
host specifies the location of the files on the remote system.

27-17

Reference

This sections covers the supported langauges, and the location of localized
icon and font files.

Supported Languages
Read the file /usr/lib/nls/ config to list system supported languages.

Localized Icon Search Path
HP VUE uses the following search path to locate localized icons, where:

language is the value of LANG.
applications is the application class name.
/ HameDirectory/ . vue/ icons/ application/Color
/ HameDirectory/ . vue/ icons/ application
/HameDirectory/. vue/icons/Color
/ HameDirectory/ . vue/ icons
/usr /vue/ icons/ language/ application/ Color
/usr /vue/ icons/ language/ application
/usr/vue/icons/language/Color
/usr/vue/icons/language

27-18

Non-English HP VUE Sessions
Reference

See Also

• "Where to put icon files" in Chapter 16

Font Locations
Fonts are located in the /usr/lib/Xll/fonts directory_

27-19

Non-English HP VUE Sessions
Reference

For Previous HP VUE 3.0 or X 11 Users

If you've previously used HP VUE 2.01, there are several configuration issues

you may encounter when moving to HP VUE 3.0:
• New locations for configuration files.
• Differences in session management.
• New configuration syntax and features for the Front Panel.
• Toolboxes replace the applications directory.
• New syntax and locations for action and filetype definitions.
• Some backdrops have been replaced.
If you are switching to HP VUE 3.0 from XII Window System, you will need

to know how HP VUE Session Management replaces certain X11 startup files,
and how environment variables are obtained in HP VUE.

28-2

New Locations for HP VUE Configuration Files

System-wide HP VUE files are now located in subdirectories of /usr/vue.

See Also

• Chapter 6 covers using the HP VUE 3.0 toolboxes.

To move the HP VUE 2.01 local_apps to the
General Toolbox
1. Log in as superuser.

2. Move the action and filetype definition (*. ad and *. ft) from
/usr/local/lib/Xll/vue/typesto /usr/vue/config/types.
3. Use vue convert to convert the database files to the HP VUE 3.0 syntax
(see "To convert HP VUE 2.01 database files to HP VUE 3.0 syntax").
4. Move the action icon files from /usr/local/lib/Xll/vue/types/tools
to /usr /vue/ config/types/tools.
If your system contains system-wide actions that were added to

/usr/lib/Xll/vue/types, you can move those to the General Toolbox too.

To move HP VUE 2.01 remote actions to the
Network Toolbox
1. Configure the local and remote systems properly to use remote actions.
See "To configure the database (exporting) host" in Chapter 22 and "To
configure the local (importing) host" in Chapter 22 for information on how
to do this.
2. On the exporting system (the system containing the action definition):
a. Move the action and filetype definition (* . ad and * . ft) files to
/usr/vue/config/export.

28-11

For Previous HP VUE 2.01 or X11 Users
Accessing applications (HP VUE 2.01 to HP VUE 3.0)

b. Use vue convert to convert the database files to the HP VUE 3.0
syntax (see "To convert HP VUE 2.01 database files to HP VUE 3.0
syntax").
c. Move the action icons (the executable files with the same
name as the action, located in tools subdirectories) to
/usr/vue/config/export/tools.

3. On the importing systems:
a. Create a directory in the Network Toolbox that is a link to the exported
action icons:
In -s /nfs/remote_host/usr/vue/config/export/tools \

/usr/vue/config/import/remote_host
b. Remove the host from the Vue.TypesDir search path, which is usually
set in /usr/lib/X11/app-defaults/Vue.

28-12

Filetypes and Actions (HP VUE 2.01 to HP VUE
3.0)

There are several major differences between HP VUE 3.0 and HP VUE 2.01
actions and filetypes:
• Update replaces the actions and filetypes built into HP VUE 2.01.
• HP VUE 3.0 uses a different file name convention and different syntax for
definitions. Although HP VUE 3.0 can continue to use the old syntax,
you should convert the actions and filetypes to the new syntax using the
vueconvert utility. Using the old syntax has a negative effect on system
performance.
• Distributed actions (actions defined on one system that are invoked on
other systems) are configured and accessed differently.

What happens to HP VUE 2.01 actions

>~~

:<.

t;':~

: ~:~t~

-;:'.

-< f

:o~ ~~

.,:

o.~ ~, ";:,~

\':0 '.:'

':, '1

:..

~:.'~l¥'" I, t;

~~>J

:;<~,\:.?1 ~

HPYUE ~.O ,prese~esy?ur' HP V~E2:01~~r~9nal) actio,nslf,ileWpes an~the •~y,ste,r, or $. You can find the command line prompt by pressing (Return) in a
terminal emulation window.
control
A graphical user interface component that enables you to manipulate an
object, select choices, or type information. Menus, text fields, and Front
Panel push buttons and indicators are examples of controls.
current session
A session that was saved when logging out of the previous session.
Returning to the saved session allows you to continue working where you
left off. (Some applications may not participate in "session management,"
so you have have to manually start them after logging in.)
data host
A host computer where the data for an action is located.
database host
A host computer where an action is defined.
Desktop
A place to put files, directories, actions, and applications for quick access.
A Desktop is available in each HP VUE workspace. To put an object on

Glossary-3

the Desktop, drag its icon from a File Manager or Toolbox window and
drop it on the workspace backdrop. An object on the desktop operates
just like its original icon. The HP VUE Desktop is not available in HP VUE
Lite.
dialog
A secondary window displayed by an application window. The Color
dialog, belonging to Style Manager's main window is an example of a
dialog.
display-dependent session
A session that can be restored on only a particular display.
display-independent session
A session that can be restored on any display, regardless of screen
resolution or color capability.
double-click
Pressing and releasing a mouse button twice in rapid succession.
drag
Pressing and holding down a mouse button while moving the mouse,
which moves the pointer on the screen.
drop
Releasing an object, such as a file icon, that has been dragged to a new
position. To drop the icon, release the mouse button.
drop zone
An area of the display that accepts a dropped file. Drop zones include
the Trash, Printer, Mailer, and Personal Toolbox control and icons in
the toolboxes that use file arguments. You can also drop objects on the
Desktop for quick access. There are no drop zones in HP VUE Lite.
execution host
A host computer where an application invoked by the action runs. The
execution host may be the same computer where the action resides, or it
may be another computer on the network.
File Annotator
An HP VUE application for adding text or audio annotations to files.
Annqtations do not alter the contents of the file or directory being

Glossary-4

annotated. (Audio annotations are available only on systems capable of
recording and playing audio.)
File Manager
An HP VUE application for managing the files and directories on your
system. File Manager is not available in HP VUE Lite.
Front Panel
A centrally-located window containing a variety of controls for accessing
applications and utilities on your computer. The Front Panel also contains
the workspace switch. The Front Panel occupies all workspaces.
file server
A host computer used to store data files used by applications.
filetype
An HP VUE mechanism used to associate particular data files with the
appropriate applications and actions. Filetypes can determine the type of
a file based on file naming conventions, such as a particular extension
name, or by the contents of the file.
font
A complete set of characters (letters, digits, and special characters) of one
size and one typeface. "Ten-point, Helvetica, bold" is an example of a
font.
General Toolbox
A container for system-wide actions built into HP VUE or put there
by your system administrator. To display the General Toolbox, choose
General in the Toolboxes subpanel.
home directory
A personal directory where you keep files and additional subdirectories
that belong to you. By default, File Manager and Terminal Emulator
windows are set to your home directory when you first open them.

/ HmneDirectory/
Symbolizes your home directory. For example, if your home directory is
/users/anna/, then / HmneDirectory/bitmaps/smile. bm represents
/users/anna/bitmaps/smile.bm.

Glossary-5

home session
A session you explicitly save without logging out.
hyperlink
A connection from one help topic to another related topic. A hyperlink
can be a word, a phrase, or a graphic image. Any underlined text within
a help window is a hyperlink.

Most hyperlinks cause a "jump" to a related help topic. However,
hyperlinks can also be used to perform other behavior, such as executing
commands or invoking actions.
lTE
An Internal Terminal Emulator. The ITE lets you use your bitmapped
display as a terminal (via No Windows mode from the Login screen).

keyboard binding
Association of a key stroke with a particular behavior.
list

A control, also called selection list, that contains scrollable choices from
which you can select.
local host
A host computer from which an action is invoked. This host must be
running HP VUE.
mapping
A mapped action is an action that invokes another action, rather than
containing its own EXEC-STRING. The file lusr Ivue/types/userprefs. vf contains the built-in mapped actions. For example, the built-in
Mailer action used by the Front Panel is mapped to another action named
Elm. You can change the mailer by remapping.
maximize
To enlarge a window to fill a workspace. The push button that maximizes
a window is located in the upper right comer of a window frame.
menu
A list of commands that is displayed from a window or software
application. The window menu enables you to control the size, shape, and
position of that window. An application menu enables you to operate the
application.

Glossary-6

menu bar
The bar directly beneath a window's title bar that contains the titles of
the pull down menus for the software application.
minimize
To turn a window into an icon. The push button that minimizes a window
is located near the upper right corner of the window frame.
mnemonic
A single, underlined character in a command. The mnemonic initiates
that the command can be executed by typing that letter. Mnemonics are
used most commonly in menu commands, however, other buttons may
also have mnemonics.
modifier key
A key that, when pressed and held, along with another key, changes the
meaning of the second key. @)' @!), and (Shift) are examples.
newline character
An unseen character that marks the end of a line of text in a document.
It tells a printer or screen to break a line and start a new one.
Network Toolbox
A container for actions available locally that are located on other host
computers on your network. To display the Network Toolbox, choose the
Network control in the Toolboxes subpanel.
networked session
A session managed across multiple systems. Using a networked session
allows you to see the same session, regardless of which system you use to
log in. It also provides a single home directory across multiple systems.
object
Any logical piece of data that has associated behavior. For example, in
File Manager, files, directories, actions, and applications are all considered
objects. Each type of object has specific associated actions. Typically,
each object is represented as an icon.
Personal Toolbox
A container for personal applications and utilities. To display the Personal
Toolbox, choose the Tools control in the Front Panel.

Glossary-7

pixmap
An image stored in a raster format. Usually the term pixmap implies that
the image may have more than two colors. An image that is limited to
two colors is usually called a bitmap.
push button
A control that immediately starts an action as soon as it is chosen. OK,
Cancel, and Help are examples of push buttons commonly found in
dialogs.
radio button
_
A control that-combined with other radio buttons-offers you a fixed set
of choices that are mutually exclusive.
resource
A mechanism of the X Window System for specifying an attribute
(appearance or behavior) of a window or application. Resources are
usually named after the elements they control.
scalable typefaces
A mathematical outline for a typeface that can be used to create a
bitmapped font for a particular size, slant, or weight.
scroll bar
A window component for controlling the contents of a scrollable area.
Scroll bars are used when information is too large to display within a
window.
session server
A system that provides networked sessions. The session files reside on the
session server. These files are used whenever the user logs into a system
on the network.
slider
A control that "slides" back and forth across a range of measurements or
values. Style Manager's Color dialog controls that choose the red, green,
and blue color values are examples of sliders.
software application
A computer program that provides you with tools to do your work.
Style Manager, Text Editor, and File Manager are examples of software
applications.

Glossary-B

Style Manager
The HP VUE application with which you easily customize some visual
elements and system device behaviors of your environment, including
colors and fonts, and keyboard, mouse, window, and session startup
behaviors.
subpanel
A component of the HP VUE Front Panel that provides additional controls.
Subpanels usually contain groups of related controls. For instance, the
Printers subpanel provides access to multiple printers.
superuser
A login that allows special permissions for modifying system files that
most users do not have permission to modify. Superuser is also called
"the root user" or simply "root" since the user ill for superuser is root.
On most computer systems, only a few users have permission to become
superuser.
terminal emulator
A window that emulates a particular terminal type for running
non-window programs. The most common use of terminal emulator
windows is interacting with your computer's operating system by typing
commands. The two most common terminal emulators in HP VUE are
hpterm and xterm.
Text Editor
The HP VUE application with which you create and edit documents.
text field
A rectangular area in a window where you type information. Text fields
with keyboard focus have a blinking text insertion cursor.
tile
A rectangular area used to cover a surface with a pattern or visual
texture. Workspace Manager supports tiling, enabling users with limited
color availability to create new color tiles blended from existing colors.
title bar
A rectangular area of a window frame (at the top of the window) that
identifies the contents of the window. Usually, a window's title is the
name of the application-for example, Style Manager.

Glossary-9

toolbox
A container for action icons. There are three toolboxes: Personal Toolbox,
General Toolbox, and Network Toolbox.
window
A rectangular area on your display. Software applications typically have
one "main" window from which "secondary" windows, called dialogs, can
be opened. A window frame has controls with which you can manipulate
the window.
window frame
The visible part of a window that surrounds a software application. A
window frame can contain five controls: title bar, resize borders, minimize
button, maximize button, and the window menu button. (Some windows
may not display all of these controls.)
window icon
A small, graphic representation of a window that takes up little area in a
workspace.
window menu
The menu displayed when you press mouse button 1 on the window
menu button in the upper left corner of the window frame, or press ~
(Space).

workspace
A single screen of windows. The HP VUE Workspace Manager creates
multiple workspaces. Each workspace is like a separate screen, plus you
can have windows "occupy" any combination of workspaces. The Front
Panel contains the workspace switch you use to move from workspace to
workspace.
Workspace Manager
The program that controls the size, placement, and operation of windows
within multiple workspaces. The HP VUE Workspace Manager includes
the Front Panel, the window frames that surround each application, and
window and workspace menus.
Workspace Menu
The menu displayed by pressing mouse button 3 on the workspace
backdrop. This menu is sometimes called the "root" menu.

Glossary -10

Index
A
accessing
help on another host, 4-19
remote data, 22-24
remote systems, 5-26
accessing a remote system, 5-26
access, limiting execution, 22-22
access, NFS, 22-24
access, remote
adding, 5-28
display, 22-23
access to local file system, limiting,
22-21
action, 19-2-27, 21-2-31
accepting dropped data files, 21-8
accepting dropped or prompted
file, 21-9
accepting multiple dropped files,
21-17
accessing remote data, 22-12
adding to toolbox, 19-21
ARG-COUNT field, 21-11
argument, non-file, 21-10
arguments interchangeable, 21-16
arguments non-interchangeable,
21-15
associating icon with, 16-17
associating with filetypes, 20-6
attaching audio playback to action,
21-20
built-in actions, 6-9
command arguments, 21-28

command executed by, 21-28
COMMAND type, 21-30
common database problems, 19-23
concepts, 19-14
Create Action, 19-4, 19-7
created with Create Action, 19-8
creating, 21-2,21-4
creating in HP VUE Lite, 23-16,
23-18
creating manually, 21-3
creating manually, reasons for,
21-2
creating MAP type, 21-6
creating simple, 19-3
database, 19-18
defining command to execute, 21-7
double-click and drop functionality
different, 21-11
double-clicking, 5-12
EditResources, 25-5
enriching, 21-3
executing action of directory, 5-22
executing action of file, 5-22
executing action of object, 5-22
executing xhost command, 22-23
execution string, 21-7
exporting and importing, 22-17,
22-19
fields in COMMAND type, 21-22
fields in MAP type, 21-23
field structure, 21-21
general action, 19-15
Index-1

general action, syntax, 21-21
icon, 20-14, 21-29
icons in toolbox, 6-3
introduction to, 19-2, 19-14
invoking another action, 21-18
invoking shell, 21-28
listing actions and filetypes on
search path, 19-24
making more readily available,
6-5, 6-10
making network action more readily
available, 6-13
MAP type, 21-30
moving general or network action
to Personal Toolbox, 6-6
multiple file arguments, 21-14
non-file data, 21-10
parameter, file, 21-8, 21-9
personal action, 19-15
prompting for file, 21-8
reference information, 19-25, 21-21
remote, 19-15
remote actions, 6-11
running, 19-7
running as different user, 21-19
running remote application, 22-5
scope, 19-16
search path, adding directory,
19-25
starting application, 19-9
starting from Terminal Emulator,
23-18
string variables in definition, 19-26
system-wide, 19-15
system-wide access to remote
application, 22-8
system-wide actions, 6-9
system-wide, in HP VUE Lite,
23-18
testing, 19-22
troubleshooting, 19-22
Index·2

two with same name, 21-12
types, 21-3
using shells, 21-11
window type, 19-5
without data, 21-7
xhosting remote, 22-23
ACTION field, 21-24
action or filetype definition, locating
problem, 19-22
action server
definition, 22-3
ACTIONS field, 20-12
Actions menu, 5-12
active directory, 26-23
adding
access to remote system, 5-28
action to HP VUE Lite subpanel,
23-15
action to toolbox, 19-21
application in HP VUE Lite, 23-12
application to Tools subpanel, 23-13
control to subpanel, 17-14
control to Terminals subpanel, 23-8
directory to actions search path,
19-25
Front Panel control, 17-7
host to Network Tholbox, 22-19
host to remote systems directory,
22-24
printer control, 18-10
printer control to Printers subpanel,
18-11
resources using xrdb, 25-7
subdirectory to Personal Toolbox,
6-5
subpanel, 17-14
system-wide action in HP VUE
Lite, 23-18
workspaces, 17-24
administering
HP VUE sessions, 15-2

networked Front Panel, 17-29
allocating colors for Starbase, 13-17
@!), 3-10
ALTERNATE_IMAGE field, 17-34
animating button, 17-21
animation, drop, 17-36
annotated file, using, 10-15
annotating file, 10-2-16
annotation
creating from file, 10-16
defined, 10-2
deleting, 10-6
editing audio, 10-11
listing, 10-3
printing, 10-8
reviewing all attached to file, 10-5
reviewing single, 10-4
saving as file, 10-15
text, 10-7
annotation, audio, 10-9
recording, 10-9
annotation, text
editing, 10-8
Annotator, File, 10-3
app-defaults file, 25-14
app-def aul t s, language-dependent,
27-14
appearance
changing login screen, 12-3
icon, 24-15
locked display, 2-14
application
accessing HP VUE 2.01 application
in HP VUE 3.0, 28-9
adding in HP VUE Lite, 6-15, 23-12,
23-13, 23-15
adding to Personal Toolbox, 6-7
creating button to activate, 17-16
exiting, 3-4
getting help, 4-3
integrating into HP VUE, 19-16

running Starbase application, 13-17
setting personal resources for, 25-4
starting, 6-5
starting in HP VUE Lite, 6-15
using action to run remote, 22-5
application directory
displaying in HP VUE 3.0, 28-10
applications
remote, restoring, 15-11
application server, definition, 22-2
application window
associating icon with, 16-20
opening and closing, 3-4
using controls in, 3-17
ARG-COUNT field, 21-11, 21-24
ARG-TYPES field, 21-25
argument
non-file, 21-10
syntax in action definition, 21-28
arguments
interchangeable in action, 21-16
multiple file arguments, 21-14
non-interchangeable in action,
21-15
associating actions with filetypes,
20-6
audio
annotation of file, 10-2-16
attaching playback to action, 21-20
customizing behavior, 9-13
devices, configuring, 13-24
editing audio recording, 10-12
server, starting, 13-25
audio annotation, 10-9
editing, 10-11
recording, 10-9
Audio dialog box, 9-13
autoXhosting resource, 22-23

Index·3

B
backdrop, 24-6
customizing, 24-6
deep, 24-7
selecting, 9-10
where to put backdrop image files,
16-16
working with backdrop images,
16-2
Backdrop dialog box, 9-10
backdrops
from HP VUE 2.01, 28-16
BACKGROUND_ TILE field, 17-34
backup resource file, creating, 25-6
bar, title, 24-11
basic file management skills, 5-9
basic window skills, 3-2
behavior
customizing, 9-11
customizing window, 9-15
Login Manager, 12-6
OSF/Motif window, 24-33
bindings
button, 24-23
custom key, 24-31
key, 24-28
keyboard, 24-29
bitmapped fonts, 26-3
bitmaps
how files are found, 16-13
• bm filename extension, 16-13
boot time, starting NCS local location
broker daemon at, 13-24
Broadcast Message Server, 13-21
installation, 13-21
multiple screens, 13-14
running vuewm without, 13-20
security, 22-22
broker daemon, NCS local location,
13-24
browsing
Index-4

files to include in Text Editor, 7-12
help, 4-10
icons using File Manager, 16-21
busy light
position in Front Panel, 17-9
button
animating, 17-21
binding syntax, 24-24
choosing, 3-17
creating, 17-17
creating for application, 17-16
custom binding set, 24-26
customizing bindings, 24-23
minimize, 24-11
printer, 18-7
Terminal, 8-3

c
cached clients, resources for, 25-21
canceling
dragging, 5-12
session, 2-5
capturing region of display, 16-12
categorization criteria for filetype,
20-4
changing
between HP VUE and OSFIMotif
window behavior, 24-33
colors, 9-4
default editor, 18-4
default mailer, 18-5
default Terminal Emulator, 18-4
directory, 5-21
File Manager default preferences,
5-38
File Manager print command, 18-6
File Manager sort order, 5-36
File Manager view, 5-36
File Manager view style, 5-37
Front Panel location, 17-26

functionality of printer push button,
18-7
host name, 22-27
how your next session starts, 9-16
icon appearance, 24-15
login screen appearance, 12-3
number of colors, 9-8
number of workspaces, 17-24
order of overlapping windows, 3-6
printer drop zone, 18-6
properties of directory, 5-18, 5-19
properties of file, 5-18, 5-19
properties of object, 5-18, 5-19
resources using Style Manager,
25-5
window into icon, 3-4
character-display console, configuring,
13-3
characters in file, non-English, 27-8
choosing
another printer for printing help
topic, 4-16
between current and home session,
2-12
button, 3-17
control from subpanel, 3-15
from the Workspace menu, 3-29
Front Panel control, 3-14
list item, 3-20
menu command using keyboard,
3-31
menu command using mouse, 3-30
two actions with same name, 21-12
choosing from the window menu,
3-27
Clean Up (command in View menu),
5-36, 5-37
clearing text in Text Editor, 7-11
client
how gets resources, 25-13
resources, 24-12

starting in different workspace,
23-4
window control, creating, 17-20
clientDecoration resource, 24-11
CLIENT_GEOMETRY field, 17-35
CLIENT _N AME field, 17-35
clipboard, 8-6
closing
application window, 3-4
terminal emulator, 8-3, 8-5
Text Editor, 7-4
window, 3-4
cluster, diskless, 13-6, 13-8
configuring, 22-14
remote data, 22-15
cluster, remote
data access, 22-15
color
changing, 9-4
grabbing from workspace, 9-6
how specified, 26-19
in help windows, 4-9
limiting number of colors, 26-17
limiting usage, 9-8
managing, 26-9
mapping to screen elements, 26-17
number of colors used in palette,
26-16
resources, 26-2
server, 23-6
sets, 26-11
setting foreground, 26-14
Starbase applications, 13-17
usage in icons, 16-22
using dynamiC, 26-15
window frame, 24-14
Color dialog box, 9-4, 9-5, 9-7, 9-8,
24-14
coloruse resource, 26-12
command
executed by action, 21-28
Index·5

helpgen, 4-20
within action definition, 21-7
COMMAND action
creating, 21-4
defined, 21-3
defining, 21-30
execution string, 21-7
fields summary, 21-22
command, application menu
choosing, 3-30
command line
file format, 21-9
specifying resources in, 25-20
command, menu
choosing using keyboard, 3-31
choosing using mouse, 3-30
commands
executing at startup, 15-8
HP-UX, 8-6
comments in action definition, 21-21
components
window, 24-10
window frame, 24-11
concept
actions, 19-14
filetype, 19-14
configuration, default for Login
Manager, 12-11
configuration file
creating subpanel, 17-13,23-14
editing system-wide subpanel,
17-12
Workspace Manager, 17-3, 24-3
configuration files
after update, 28-3
locations, 28-3
Login Manager rereading, 12-10
subpanel, 17-11
configuring
applications in HP VUE Lite, 23-12
audio devices, 13-24
Index·6

character-display console, 13-3
control in printers subpanel, 18-8
diskless cluster, 13-6, 22-14
execution host to access remote
data, 22-12
exporting host, 22-17
Front Panel, 17-24
Help Manager printing, 18-14
local host for remote execution,
22-5
local importing host, 22-18
multiple displays, 13-9
multiple screens, 13-14
networking for diskless cluster,
13-8
network security, 22-21
non-XDMCP terminals, 13-5
online help, 4-19
remote execution host, 22-6
session server, 22-28
subpanels, 17-11
system timeout, 2-15
terminal, mailer, editor, and printer,
18-2
workspace switch, 17-25
console, character-display, 13-3
content-based filetype, creating, 20-8
CONTENT field, 20-12
contents, finding file by, 5-34
context, getting help based on, 4-4
control
adding another printer control,
18-10
adding or removing, 17-14
adding printer control to printers
subpanel, 18-11
adding to Terminals subpanel, 23-8
choosing from subpanel, 3-15
client window, 17-20
configuring control in printers
subpanel, 18-8

creating control that monitors file,
17-18
creating Front Panel, 17-16
creating toggle control, 17-19
customizing Front Panel controls,
17-2-42
defining Front Panel, 17-16
distributing, 17-30
Front Panel, 3-14
height of icon, 17-38
icon for, 17-38
name to associate with executable
control, 17-35
number of processes, 17-41
using in application window, 3-17
conventions, image file naming, 16-13
CONVERTED file, 28-5
ConvertVuewmrc utility, 28-8
copying
directory, 5-17
directory to remote system, 5-27
file, 5-17
file to remote system, 5-27
object, 5-17
object to remote system, 5-27
palette, copying and modifying,
9-7
text in Text Editor, 7-11
Create Action
creating simple action, 19-3
HP VUE Lite, 23-16
limitations, 19-7
using, 19-4
using action created by, 19-7
what it does, 19-4
creating
action, 21-2, 21-3
action and filetype, personal, 19-11
action for multiple dropped files,
21-17

action that accepts dropped file,
21-8
action that accepts dropped or
prompted file, 21-9
action that invokes another action,
21-18
action that prompts for file, 21-8
action that runs as different user,
21-19
action to start application, 19-9
action with Create Action, 19-8
action with multiple file arguments,
21-14
action without data, 21-7
annotation, 10-7
annotation from file, 10-16
backup resource file, 25-6
button and drop zone, 17-17
button for application, 17-16
client window control, 17-20
COMMAND action, 21-4
content-based filetype, 20-8
control that monitors file, 17-18
custom button binding set, 24-26
customized first session, 15-7
custom key binding set, 24-31
custom palette, 9-7
custom window menu, 24-21
directory, 5-15
display-dependent session, 15-9
document, 7-5
drop zone to start terminal, 17-22
execution string, 21-7
file, 5-15
filetype, 20-3
filetype and action, personal, 19-11
file with non-English characters,
27-8
Front Panel control, 17-16
MAP action that modifies Print
action, 21-6
Index-7

new Front Panel, 17-28
object, 5-15
personal fp. printer file, 18-10
personal named-based filetype,
20-7
personal Workspace Manager
configuration file, 17-3
simple action, 19-3
simple filetype, 19-10
subpanel, 17-11
subpanel configuration file, 17-13,
23-14
symbolic link, 5-18
system-wide action for remote
application, 22-8
system-wide filetype, 20-8
Terminals subpanel configuration
file, 23-9
text annotation, 10-7
toggle control, 17-19
current and home session
choosing between, 2-12
current session defined, 2-10
custom
button binding set, 24-26
key binding set, 24-31
workspace menu, 24-20
customizing
audio behavior, 9-13
backdrops, 24-6
button bindings, 24-23
creating window menu, 24-21
File Manager, 26-23
Front Panel, 17-2-42
how window acquires focus, 9-15
HP VUE language, 27-10
HP VUE Lite, 23-2-18
HP VUE Lite Terminal Emulators,
23-7
key bindings, 24-28
keyboard behavior, 9-11
Index-8

language menu, 12-5
Login Manager, 12-2
Login Manager behavior, 12-6
login screen, 12-3
mouse behavior, 9-12
printing, 18-6
screen appearance, 9-4
screen saver, 9-14
sessions, 15-7
system behavior, 9-11
terminal emulator, 8-8
window behavior, 9-15
window components, 24-10
Workspace Manager, 24-2
workspaces, 24-6
cutting
text, 8-6
text from windows, 3-23
text in Text Editor, 7-11
CWD field, 21-26
D

daemon, NCS local location broker,
13-24
daily message at login, 12-6
data
accessing from remote cluster,
22-15
accessing remote, 22-24
action accessing remote, 22-12
action without, 21-7
execution host accessing remote,
22-12
non-file, 21-10
remote, on diskless cluster, 22-15
specifying remote, 22-13
database
actions and filetype, 19-18
common problems, 19-23
defined, 19-18
errors, 19-24

errors, viewing, 19-24
local directories, 19-19
reloading, 19-21
rereading, 19-21
database administration, Login
Manager, 12-9
database host
configuring, 22-17
definition, 22-4
database search path, 19-24
data file
action that accepts dropped, 21-8
remote, 21-8
data files, context-dependent, 22-15
data host, definition, 22-4
data, using non-English, 27-8
decorations
Front Panel, 24-13
subpanel, 24-13
default
editor, 18-3
editor, changing, 18-4
environment variables, 14-4
key bindings, 24-28
Login Manager configuration, 12-11
mailer, 18-3
mailer, changing, 18-5
saving File Manager current
preferences as, 5-38
terminal, 18-3
Terminal Emulator, changing, 18-4
defined
database, 19-18
toolbox, 19-20
definition
action, 21-21
action or filetype, locating problem,
19-22
application server, 22-2
directory, 5-5
file, 5-5

Front Panel, 17-4
path, 5-5
session server, 22-28
deleting
annotations, 10-6
directory, 5-24
file, 5-24
Front Panel control, 17-7
object, 5-24
palette, 9-7
resources, 25-9
text in Text Editor, 7-11
using Trash Can, 5-24
DESCRIPTION field, 21-27
Desktop
putting file or directory on, 5-31
removing file or directory from,
5-32
removing object from, 5-32
using, 5-30
devices
audio, 13-24
dialog box
Audio, 9-13
Backdrop, 9-10
Color, 9-4, 9-5,9-7, 9-8
Delete Palette, 9-7
Font, 9-9
Host, 8-12
Keyboard, 9-11
Modify, 9-5
Mouse, 9-12
Screen, 9-14
Startup, 9-16
Window, 9-15
different double-click and drop
functions, 21-11
different resources for each node,
13-7
different window manager, 15-9
directory
Index-9

active, 26-23
adding host to Remote Systems
directory, 22-24
adding to actions search path,
19-25
changing, 5-21
changing properties, 5-18, 5-19
copying, 5-17
creating, 5-15
deleting, 5-24
dropping, 5-12
getting help on, 5-11
hidden, 5-38
hiding, 5-39
local database directories, 19-19
moving, 5-16
moving or copying to remote system,
5-27
navigating to, 5-21
opening, 5-12
opening on remote system, 5-26
putting on Desktop, 5-31
removing from Desktop, 5-32
renaming, 5-11
re-sorting directories, 5-37
restoring from Trash Can, 5-24
selecting multiple directories, 5-10
selecting single, 5-9
specifying remote, 5-29
viewing remote, 22-24
diskless cluster
configuring, 13-6, 22-14
networking, 13-8
remote data, 22-15
display
capturing region of, 16-12
configuring multiple displays, 13-9
different vuelogin resources,
13-11
environment variables different
for each, 13-13
Index·10

limiting remote access, 22-23
locking and unlocking, 2-13
starting server on each, 13-9
startup script different for each,
13-12
display-dependent session, 28-4
creating, 15-9
DISPLAY environment variable, 12-7,
14-4, 14-9
display-independent session, 28-4
creating, 28-5
displaying
another workspace, 3-7
icon in Front Panel control, 16-19
Login Manager errors, 12-9
man pages, 4-14
message of day at login, 12-6
root window, 24-8
subpanel, 3-15
display lock, 2-13
display name in Xconiig, 13-10
distributed computing, 22-2
distributing control, 17-30
document
creating, 7-5
editing, 7-2-18
formatting, 7-17
opening, 7-5
opening from File Manager, 7-6
saving in Text Editor, 7-7
dot files, 5-38
double-clicking
action performed, 5-12
dragging
canceling, 5-12
directory, 5-9
file, 5-9
object, 5-9
drawing icon image, 16-5
drop action, 17-37
DROP_ACTION field, 17-37

drop animation, 17-36
DROP_ANIMATION field, 17-36
dropped file, action that accepts,
21-8, 21-9
dropped files, action accepting
multiple, 21-17
dropping
directory, 5-9, 5-12
file, 5-9, 5-12
object, 5-9, 5-12
dropping file, defining action invoked
by, 17-40
drop zone
changing printer, 18-6
creating, 17-17
used to start terminal, 17-22
dynamic color, using, 26-15
E
editing
audio annotation, 10-11
audio recording, 10-12
file with non-English characters,
27-8
icon, 16-4
non-English language characters,
27-17
system-wide subpanel configuration
file, 17-12
text annotation, 10-8
text in field, 3-22
text in Text Editor, 7-8-11
text or document, 7-2-18
vuewmre, 24-3
editor
changing default, 18-3, 18-4
configuring, 18-2
Text Editor, 7-2-18
Editor, Icon, 16-4
Edi tResourees action, 25-5
Edi tVuewmre action, 24-3, 24-4

elements
frame, 24-12
window frame, 24-10
emptying Trash Can, 5-25
ending a session, 2-5
entering
text in Text Editor, 7-8
text into empty field, 3-22
environment file, shell, using with
.vueprofile, 14-11
environments, HP VUE partial, 13-19
environment variable
DISPLAY, 12-7, 14-4, 14-9
HOME, 12-7, 14-4
LANG, 14-4
PATH, 12-7, 14-4
SHELL, 12-7, 14-4
USER, 12-7, 14-4
VUEACTIONSEARCHPATH, 19-25
XAUTHORITY, 12-7, 14-4
environment variables, 14-2, 19-27
built into vuelogin, 14-4
different for each display, 13-13
how handled during remote
execution, 22-10
setting personal, 14-10
setting system-wide, 14-6
Starbase applications, 13-18
used by Xstartup, 12-7
.vueprofile, 12-13
erasing
using Trash Can, 5-24
errorlog file, 19-24, 29-4
error messages, 29-4
errors
database, 19-24
displaying Login Manager errors,
12-9
/ete/export, 22-21,22-24
/ete/hosts
changing host name, 22-27
Index-11

example
adding action to HP VUE Lite
Subpanel, 23-15
adding Front Panel control to
bottom row, 17-9
adding printer control to printers
subpanel, 18-11
adding terminal to Terminals
subpanel in HP VUE Lite,
23-9
assigning application to Tools
control, 23-13
configuring networked sessions,
22-29
creating action to start application,
19-9
creating COMMAND action to print
graphics file, 21-4
creating drop zone to start terminal,
17-22
creating MAP action, 21-6
creating personal action and
filetype, 19-11
creating personal named-based
filetype, 20-7
creating system-wide action for
remote application, 22-8
creating system-wide content-based
filetype, 20-8
distributing control, 17-30
exporting and importing action,
22-19
providing file-type dependent
printing, 18-13
EXEC-HOST field, 21-27
EXEC-STRING field, 21-7, 21-28
executing
action of directory, 5-22
action of file, 5-22
action of object, 5-22

Index·12

additional commands at session
startup, 15-8
execution access to system, limiting,
22-22
execution, configuring local host for
remote, 22-5
execution host
configuring remote, 22-6
configuring to access remote data,
22-12
definition, 22-4
execution, remote
how environment variables
handled, 22-10
specifying host, 22-7
execution string for action, 21-7
exiting application, 3-4
exporting
action, 22-17, 22-19
configuring database host, 22-17
[Extend chad, 3-10

F
fail-safe session
customizing, 15-10
logging in and out, 2-8
failsafe session
starting, 2-6
field
ACTION, 21-24
ACTIONS, 20-12
ALTERNATE_IMAGE, 17-34
ARG-COUNT, 21-11, 21-24
ARG-TYPES, 21-25
BACKGROUND_TILE, 17-34
CLIENT_GEOMETRY, 17-35
CLIENT_NAME, 17-35
CONTENT, 20-12
CWD, 21-26
DESCRIPTION, 21-27
DROP _ACTION, 17-37

DROP_ANIMATION, 17-36
editing text in, 3-22
entering text into empty, 3-22
EXEC-HOST, 21-27
EXEC-STRING, 21-7, 21-28
FILE-PATTERN, 20-14
HELP_STRING, 17-37
IMAGE, 17-38
LABEL, 17-38
LAYOUT_POLICY, 17-38
L-ICON for actions, 21-29
L-ICON for filetype, 20-14
MODE, 20-15
MONITOR_FILE, 17-39
PATH-PATTERN, 20-16
PUSH_ACTION, 17-40
PUSH_ANIMATION, 17-40
PUSH_RECALL, 17-41
S-ICON for actions, 21-29
S-ICON for filetype, 20-14
TYPE, 17-42,21-30
WINDOW-TYPE, 21-31
fields
action, 21-21
filetype, 20-11
in COMMAND action, 21-22
in MAP action, 21-23
file
action accepting multiple files,
21-17
action prompting for, 21-8
annotating, 10-2-16
arguments, multiple, 21-14
as source of annotation, 10-16
changing properties, 5-18, 5-19
context-dependent, 13-7, 22-15
context-dependent data, 22-15
copying, 5-17
creating, 5-15
deleting, 5-24
dropping, 5-12

finding by contents, 5-34
finding by name, 5-33
getting help on, 5-11
hidden, 5-38
hiding, 5-39
icon size, 20-15, 21-30
including, 17-26
locating, 5-33
management, basic skills, 5-9
managing files, 5-2
moving, 5-16
moving or copying to remote system,
5-27
name in command line, 21-9
opening, 5-12
putting on Desktop, 5-31
remote data, 21-8
removing from Desktop, 5-32
renaming, 5-11
re-sorting files, 5-37
restoring from Trash Can, 5-24
saving annotation as, 10-15
selecting multiple files, 5-10
selecting single, 5-9
specifying remote, 5-29
system, hierarchical, 5-5
using annotated, 10-15
with non-English characters, 27-8
File Annotator, 10-3
File Manager, 5-2
action icon, 21-29
changing print command, 18-6
changing sort order, 5-36
changing view style, 5-37
controlling views, 5-36
customizing, 26-23
opening document, 7-6
resources, 26-23
saving current preferences as
default, 5-38
using as icon browser, 16-21
Index·13

FILE-PATTERN field, 20-14
file server
definition, 22-2
filetype, 20-2-16
associating icon with, 16-17
associating with actions, 20-6
categorization criteria, 20-4
concepts, 19-14
creating, 20-3
creating simple, 19-10
criteria, 20-2
database, 19-18
defining, 20-3
definition, reference, 20-9
definition syntax, 20-9
example, 20-8
fields, summary, 20-11
general filetype, 19-15
introduction to, 19-2, 19-14
named-based, 20-7
personal filetype, 19-15
reference, 19-25
remote, 19-15
requirements, 20-15
simple, 19-10
system-wide, 19-15
file-type dependent printing, 18-12,
18-13
finding
file, 5-33
file by contents, 5-34
file by name, 5-33
text in Text Editor, 7-13
first session, 15-6, 15-7
setting sys . resources for, 25-10
focus
changing how window acquires,
9-15
pointer, 9-15
focus policy
window, 9-15
Index·14

font
bitmapped, 26-3
listing available fonts, 26-5
location of, 27-19
managing fonts, 26-3
resources, 26-2
resources, setting, 26-3
selecting new size, 9-9
X Logical Font Description, 26-7
Font dialog, 26-3
Font dialog box, 9-9
foreground color, 26-14
foreign server, 13-4
format of file name in command line,
21-9
formatting document, 7-17
formatting document in Text Editor,
, 7-17
fp. printer file, 18-10
fp. tool, 23-13, 23-15
frame
color, 24-14
components, 24-11
resources, 24-12, 24-13
window elements, 24-10
Front Panel
adding control, 17-7
changing editor, 18-3
changing location, 17-26
changing mailer, 18-3
changing printer, 18-3
configuration, 17-24
control, choosing, 3-14
controls, creating, 17-16
controls, defining, 17-16
converting HP VUE 2.01 Front
Panel to HP VUE 3.0, 28-6
converting HP VUE 2.01 to HP
VUE 3.0, 28-8
creating new, 17-28
customizing, 17-2-42

decorations, 24-13
definition, 17-4
deleting control, 17-7
displaying icon in, 16-19
HP VUE 2.01, 28-6
HP VUE Lite, 3-13
localizing, 27-10
logout control, 2-4
modifying, 17-3
modifying control, 17-7, 17-9
moving, 3-16
networked, 17-29
reference, 17-32
turning into icon, 3-16
using, 3-11
what is in, 3-12

G
general action, 19-15
copying to personal toolbox, 6~ 10
making more readily available,
6-10
moving to Personal Toolbox, 6-6
general filetype, 19-15
General Toolbox, 6-9
opening, 6-9
geometry
client window, 17-35
control icon, 17-38
resources, 26-21
German Terminal Emulator, 27-6
getting
current-context help, 4-4
help. on directory, 5-11
help on file, 5-11
help on object, 5-11
grabbing
color from workspace, 9-6
grabbing region of display, 16-12

H
handles, resize, 24-11
help, 4-3-20
accessing on another host, 4-19
browsing, 4-10
client, 4-19
colors, 4-9
context-sensitive, 4-4
duplex printing, 4-17
finding topic by exploring, 4-7
finding topic by keyword, 4-8
getting help on directory, 5-11
getting help on file, 5-11
getting help on object, 5-11
getting within application, 4-3
Help Manager, Version 2.01, 4-10
printing help topic on another
printer, 4-16
printing help topics, 4-16
requesting, 4-4
searching (keyword index), 4-8
server, 4-19
specifying, 17-37
windows, 4-3
helpgen command, 4-20
Help Manager
configuring printing, 18-14
starting, 4-11
Help menu, 4-4
help server, 4-19
HELP_STRING field, 17-37
Help System, HP, 4-3
hidden files, 5-38
hiding directory, 5-39
hiding file, 5-39
hiding object, 5-39
hierarchical file system, 5-5
home and current session, choosing
between, 2-12
HOME environment variable, 12-7,
14-4
Index·15

home session
automatically starting at login,
2-11
defined, 2-10
saving, 2-1
host
accessing help on another, 4-19
adding to Network Toolbox, 22-19
adding to remote systems directory,
22-24
configuring exporting, 22-17
configuring local importing host,
22-18
definition of host data, 22-4
definition of host database, 22-4
file name in command line, 21-9
Host dialog box, 8-12
host, execution
accessing remote data, 22-12
definition, 22-4
host, local
configuring for remote execution,
22-5
definition, 22-4
host name, changing, 22-27
host, remote
configuring remote execution, 22-6
specifying remote execution, 22-7
hotspot in an icon, 16-12
HP Help System, 4-3
hpterm, 8-2, 8-12, 25-7
HP-UX commands, 8-6
HPVUE
first session, 15-6
installing over Softbench, 13-21
moving to HP VUE from Softbench,
13-21
running session from X startup
script, 13-19
sessions, administering, 15-2
sessions, types of, 15-3

Index·16

starting session, 2-2-15
HP VUE 2.01
accessing Help Manager, 4-1
accessing HP VUE 2. 1 applications
in HP VUE 3.0, 28-9
actions in HP VUE 3.0, 28-13
backdrops replaced in HP VUE 3.0,
28-16
converting database files to HP
VUE 3.0, 28-14
converting Front Panel definition
syntax to HP VUE 3.0, 28-8
differences in session management,
28-4
different configuration file locations,
28-3
displaying HP VUE 2.01 tools in
HP VUE 3.0 toolboxes, 28-10
displaying HP VUE 3.0 tools, 28-10
filetypes in HP VUE 3.0, 28-13
Help Manager, 4-10
moving local_apps to General
Toolbox, 28-11
moving remote actions to Network
Toolbox, 28-11
switching to HP VUE 3.0 Front
Panel, 28-7
the first HP VUE 3. session, 28-4
what happens to HP VUE 3.0 Front
Panel, 28-6
HP VUE Lite
adding application, 6-15, 23-15
adding applications, 23-12, 23-13
configuring terminals, 23-7
customizing, 23-2-18
deleting directory, 5-24
deleting file, 5-24
deleting object, 5-24
differences from HP VUE Regular,
23-2
Front Panel, what is in, 3-13

° °

logging out, 23-6
making only session, 23-3
resources for first session, 23-5
sessions, 23-3
starting, 23-6
starting applications, 6-15
starting Edi tVueTNIIlrc, 24-3
starting session, 2-6
terminal emulators, 8-12
tools, 6-15
using tools, 0-14
HP VUE or OSF/Motif window
behavior, 24-33
HP VUE session
starting after using HP VUE Lite,
2-3
I
icon
action, 20-14, 21-29
appearance, 24-15
associating with action or filetype,
16-17
associating with application
window, 16-20
color usage, 16-22
displaying icon box, 9-15
displaying in Front Panel control,
16-19
drawing image, 16-5
editing, 16-4
for control, 17-38
for pushed button, 17-40
hotspot, 16-12
how files are found, 16-13
localized, 27-10
making associations, 16-17
naming conventions, 16-13
non-English, 27-10
opening for editing, 16-4
resources, 24-10

search path for localized, 27-18
selecting multiple icons, 5-10
selecting single, 5-9
size, 21-30
size recommendations, 16-23
turning Front Panel into, 3-16
turning window into, 3-4
using File Manager as icon browser,
16-21
working with, 16-2
Icon Editor
capturing region of display, 16-12
opening icon for editing, 16-4
resizing icon, 16-8
saving icon, 16-7
saving icon with new name, 16-7
starting, 16-4
using, 16-4
icon file
specifying, 16-17
where to put, 16-15
iconify
window, 3-4
IMAGE field, 17-38
image file
naming conventions, 16-13
where to put backdrop, 16-16
image files
how they're found, 16-13
images, types of, 16-2
importing
action, 22-17, 22-19
host, configuring local, 22-18
INCLUDE, 17-26, 17-29
incl ude syntax, 24-4
including
file in Text Editor, 7-12
files, 17-26
other files in vueTNIIlrc, 24-4
remote file, 17-29

Index-17

inetd. sec file, changing host name,

22-27
information on display, organizing,
3-3
inserting file in Text Editor, 7-12
installing HP VUE over Softbench,
13-21
integrating application into HP VUE,
19-16
interchangeable arguments, 21-16
interchangeable, arguments not,
21-15
invalid directory error, 5-27
item, choosing list, 3-20
item help, 5-11
J

Japanese Terminal Emulator, starting,
27-5
justification, Text Editor, 7-17
K

KBD_LANG environment variable,
27-15
key bindings, customizing, 24-28
key binding set, custom, 24-31
keyboard
bindings, 24-28
bindings syntax, 24-29
choosing menu command using,
3-30, 3-31
customizing behavior, 9-11
Keyboard dialog box, 9-11
keys used to move around in
workspace, 3-10
keyword, finding help topic by, 4-8
ksh, used in actions, 21-11
L

LABEL field, 17-38

Index-18

LANG environment variable, 14-4,
27-12
LAN G (language) setting, 14-9
language
customizing, 27-10
different, 2-5
reference, 27-18
setting system-wide, 14-9
setting with a vuelogin resource,
27-13
system administration, 27-12
language menu, customizing, 12-5
languages
supported non-English, 27-18
language, setting using vuelogin
resource, 27-13
LANG variable in . vueprofile,
27-13
LAYOUT_POLICY field, 17-38
L-ICON field
for actions, 21-29
for filetype, 20-14
limitations of Create Action, 19-7
limiting
access by X-terminals to host, 13-4
access to local file system, 22-21
color usage, 9-8
execution access to system, 22-22
number of colors, 26-17
remote access to display, 22-23
link, creating symbolic, 5-18
listing
annotations, 10-3
available fonts, 26-5
database errors, 19-24
list item, choosing, 3-20
ListVueTypes action, 19-24
local database directories, 19-19
local file system, limiting access,
22-21
local host

configuring for remote execution,
22-5
definition, 22-4
local importing host, configuring,
22-18
localizing
Front Panel, 27-10
icons, 27-10
location of
fonts, 27-19
Front Panel, 17-26
session data, 15-3
lock
at timeout, 2-15
configuring, 22-21
lock cover, 2-14
locked display, appearance of, 2-14
locking the display, 2-13
logging into and out of fail-safe
session, 2-8
logging into HP VUE Lite, 2-6
logging into HP VUE session, 2-2-15
logging out of HP VUE session, 2-4
login
non-English, 27-4
system-wide script, 12-7
Login Manager
built-in variables, 14-4
configuration files, 12-12
configuration files on update, 28-3
customizing, 12-2
customizing behavior, 12-6
database administration, 12-9
default configuration, 12-11
displaying errors, 12-9
files, 12-12
how it starts session, 12-13
location of configuration files, 28-3
reference, 12-11
rereading configuration files, 12-10
vuegreet, 12-12

vuehello, 12-12
vuelogin, 12-12
login message of day, 12-6
login screen
changing appearance, 12-3
customizing, 12-3
logout
from HP VUE Lite, 2-7
script, system-wide, 12-7
logout control
position in Front Panel, 17-9
M

mailer
changing default, 18-3, 18-5
configuring, 18-2
managing
colors, 26-9
files, 5-2, 5-9
fonts, 26-3
multiple screens, 13-15
man pages, displaying, 4-14
manually, creating actions, 21-3
MAP action
creating, 21-6
defining, 21-30
definition, 21-3
summary of fields, 21-23
mapping
color to screen elements, 26-17
Terminal Emulator, 23-7
margins
Text Editor, 7-17
matching wildcards, 5-33
maximize button, 24-11
menu
Actions, 5-12
command, choosing, 3-30
command, choosing using keyboard,
3-31
creating for window, 24-21
Index·19

language, 12-5
Terminal, 8-12
using, 3-25
Workspace, 3-29
Workspace Manager menus, 24-17
message catalogs, NLSPATH
environment variable, 27-14
message of day at login, 12-6
messages
error, 29-4
misspelled words, correcting, 7-14
MODE field, filetype definition, 20-15
Modify dialog box, 9-5
modifying
colors, 9-5
Front Panel, 17-3
Front Panel control, 17-7, 17-9
palette, 9-5
subpanels, 17-11
MONITOR_FILE field, 17-39
monitoring file, 17-18, 17-39
mounting, NFS, 22-12, 22-24
security, 22-21
mouse
customizing behavior, 9-12
Mouse dialog box, 9-12
moving
around in workspace using keys,
3-10
between directories, 5-9
cursor within document, 7-9
directory, 5-16
directory to remote system, 5-27
file, 5-16
file to remote system, 5-27
Front Panel, 3-16
general or network action to
personal toolbox, 6-6
object, 5-16
object to remote system, 5-27
text in Text Editor, 7-11
Index·20

window or window icon, 3-5
multiple directories, selecting, 5-10
multiple-displays, configuring, 13-9
multiple file arguments for actions,
21-14
multiple files
selecting, 5-10
multiple icons
selecting, 5-10
multiple interchangeable file
arguments, 21-16
multiple objects
selecting, 5-10
multiple screens, 13-15
Broadcast Message Server, 13-14
configuring, 13-14
how HP VUE supports, 13-14
session manager, 13-14
mWlIl, using instead of vuewm, 15-9
N

name
filetype based on file name, 20-7
finding file by, 5-33
same for two actions, 21-12
navigating
moving between directories, 5-9
to directories and subdirectories,
5-21
NCS' local location broker daemon,
13-24
network action
making more readily available,
6-13
moving to Personal Toolbox, 6-6
networked
Front Panel, 17-29
session, 22-28
session, configuring system for,
22-29
session, example, 22-29

networking, 22-2
for diskless cluster, 13-8
network security, configuring, 22-21
Network toolbox
incorporating HP VUE 2.01 actions,
28-11
Network Toolbox, 6-11
adding host, 22-19
opening, 6-12
NFS mounting, 22-12, 22-24
security, 22-21
NLS environment variables, 27-14
NLS remote execution, 27-17
NoBackdrop, 24-8
node, different resources for each,
13-7
non-English
characters in file, 27-8
characters, printing file with, 27-9
data, using, 27-8
HP VUE seSSions, 27-2
login, 27-4
Terminal Emulator, 27-5
non-interchangeable arguments in
action, 21-15
NO-STDIO action window type, 21-31
No Windows mode, 2-9
starting session, 2-6
number of colors
limiting, 26-17
palette uses, 26-16

o
object
changing properties, 5-18, 5-19
copying, 5-17
creating, 5-15
deleting, 5-24
dropping, 5-12
executing its action, 5-22
executing its directory, 5-22

executing its file, 5-22
getting help on, 5-11
hiding, 5-39
moving, 5-16
moving or copying to remote system,
5-27
opening, 5-12
putting on Desktop, 5-31
removing from Desktop, 5-32
renaming, 5-11
re-sorting objects, 5-37
restoring from Trash Can, 5-24
selecting multiple objects, 5-10
selecting single, 5-9
specifying remote, 5-29
one-instance control, creating, 17-19
online help, 4-3-20
opening
application window, 3-4
directory, 5-12
directory on remote system, 5-26
document, 7-5
document from File Manager, 7-6
existing document, 7-5
file, 5-12
General Toolbox, 6-9
Help Manager, 4-11
icon for editing, 16-4
Network Toolbox, 6-12
new document, 7-5
object, 5-12
Personal Toolbox, 6-4
terminal window in current
directory, 5-21
Trash Can, 5-23
window, 3-4
opening Style Manager, 9-2
options, command-line, 25-13
order, changing File Manager sort,
5-36
order of overlapping windows, 3-6
Index·21

organizing information on display,
3-3
OSF/Motif window
behavior, 24-33
manager, 24-2
overlapping windows, changing order
of, 3-6
p

pages, displaying man, 4-14
palette, 24-14
adding, 9-7
copying and modifying, 9-7
creating, 9-7
deleting, 9-7
modifying, 9-5
number of colors used by, 26-16
restoring deleted, 9-7
selecting, 9-4
setting, 26-10
panel decorations, 24-13
.. (parent directory), 5-6, 5-38
partial HP VUE environments, 13-19
password
changing, 2-5
pasting
text, 8-6
text in Text Editor, 7-11
text into windows, 3-23
path
action and filetype search path,
19-24
actions search path, 19-25
database search path, 19-24
defined, 5-5
search path for localized icons,
27-18
PATH environment variable, 12-7,
14-4
PATH-PATTERN field, 20-16
PATH variable, 21-7
Index·22

PERM-TERMINAL action window
type, 21-31
personal
action, 19-15
filetype, 19-15
personal action, making more readily
available, 6-5
personal environment variables,
setting, 14-10
personal filetype and action, creating,
19-11
personal fp. printer file, 18-10
personal resource files, 25-18
personal resources for application,
25-4
Personal Toolbox, 6-4
adding application to, 6-7
adding subdirectory, 6-5
opening, 6-4
pixmaps
how files are found, 16-13
pixmap shadows, 26-13
placement of window, 9-15
. pm filename extension, 16-13
popup menu
command, choosing using keyboard,
3-31
command, choosing using mouse,
3-30
popup menus, how to use, 5-9
print command, changing File
Manager, 18-6
printer
configuring, 18-2
control, adding to printers subpanel,
18-11
drop zone, changing, 18-6
push button, changing functionality,
18-7
printer subpanel

adding another printer control,
18-10
configuring, 17-11
configuring control in, 18-8
printing
configuring Help Manager printing,
18-14
customizing, 18-6
document in Text Editor, 7-18
duplex (online help), 4-17
file-type dependent, 18-12, 18-13
file with non-English characters,
27-9
help topic on another printer, 4-16
help topics, 4-16
text annotation, 10-8
problem, locating cause of in action
or file type definition, 19-22
problems, common database, 19-23
processes, number for control, 17-41
prompting for file, action, 21-8, 21-9
prompting for non-file data, 21-10
properties, changing
directory, 5-18, 5-19
file, 5-18, 5-19
object, 5-18, 5-19
PUSH_ACTION field, 17-40
PUSH_ANIMATION field, 17-40
pushed button icon, 17-40
PUSH_RECALL field, 17-41
putting
file or directory on Desktop, 5-31
object on Desktop, 5-31
window in multiple workspaces,
3-9
R
R4 server, 13-4
radio button, selecting, 3-17
raising window with focus, 9-15
recording

audio, 10-11
audio annotation, 10-9
editing audio, 10-12
reference
language, 27-18
reference information
action definitions, 21-21
actions and filetypes, 19-25
filetype definitions, 20-9
Front Panel, 17-32
Login Manager, 12-11
resources, 25-12
Workspace Manager, 24-34
ReloadAct ions, 19-21
reloading database, 19-21
remapping actions, 18-3
remote
action, 19-15
execution and NLS, 27-17
filetype, 19-15
remote access
through terminal emulator, 8-9
to display, limiting, 22-23
remote action, automatic xhosting,
22-23
remote application
system-wide action for, 22-8
using action to run, 22-5
remote applications
restoring, 15-11
remote authorization, user-based,
22-23
remote cluster, data access, 22-15
remote data
accessing, 22-24
action accessing, 22-12
execution host accessing, 22-12
file, 21-8
on diskless cluster, 22-15
specifying, 22-13

Index·23

remote directory or file, specifying,
5-29
remote directory, viewing, 22-24
remote execution
configuring local host for, 22-5
host, configuring, 22-6
host, specifying, 22-7
how environment variables
handled, 22-10
remote file, including, 17-29
remote host, 8-12
RemoteHpterm, customizing, 23-8
remote system
accessing, 5-26
adding access to, 5-28
moving or copying directory to,
5-27
moving or copying file to, 5-27
opening directory, 5-26
Remote Systems directory, 22-24
adding host, 22-24
remote terminal buttons, customizing,
23-8
RemoteXterm, customizing, 23-8
removing
control from subpanel, 17-14
file or directory from Desktop,
5-32
Front Panel control, 17-7
object from Desktop, 5-32
remsh command, 15-11
renaming
directory, 5-11
file, 5-11
object, 5-11
workspace, 3-8
replacing
current resources using xrdb, 25-8
text in Text Editor, 7-11,7-13
requesting help, 4-4
rereading
Index·24

database, 19-21
Login Manager configuration files,
12-10
rereadTime resource, 26-23
resize function, 8-7
resize handles, 24-11
resizing window, 3-6, 8-7
re-sorting
files and directories, 5-37
objects, 5-37
resource
autoXhosting, 22-23
coloruse, 26-12
files, language-dependent, 27-17
rereadTime, 26-23
syntax of specifications, 25-12
Window Manager, 24-34
resource file
creating backup, 25-6
personal, 25-18
system, 25-16
RESOURCE_MANAGER property,
25-13, 25-20
resources
adding using xrdb, 25-7
cached clients, 25-21
changing using Style Manager, 25-5
client, 24-12
color, 26-2
deleting, 25-9
different for each node, 13-7
first HP VUE Lite session, 23-5
font, 26-2
frame, 24-12, 24-13
geometry, 26-21
how clients get, 25-13
icon, 24-10
moving from XII, 28-17
personal, 25-4
reference information, 25-12
replacing using xrdb, 25-8

scope of, 25-15
setting using Edi tResources action,
25-5
specifying in command line, 25-20
Style Manager, 26-22
system-wide, 25-10
using, 25-2
vuelogin, different for each
display, 13-11
workspace, 24-12
resources, language-dependent, 27-14
restoring
deleted palette, 9-7
items in Trash Can, 5-24
text in Text Editor, 7-11
reviewing
all annotations attached to file,
10-5
annotations, 10-3
single annotation, 10-4
.rhosts file, 15-11
root menu, 24-17
root window, displaying, 24-8
running
different X server, 12-8
HP VUE Lite session, 2-6
HP VUE session from X startup
script, 13-19
remote application using action,
22-5
Starbase applications, 13-17
system-wide scripts at login and
logout, 12-7
terminal emulator on another
system, 8-9
vueTNIIl without HP VUE, 13-20
window manager without HP VUE,
13-20

S
saving
annotation as file, 10-15
document in Text Editor, 7-5, 7-7
File Manager current preferences
as default, 5-38
home session, 2-10
scalable typefaces, 26-3
scope
action, 19-16
resources, 25-15
screen
appearance, customizing, 9-4
elements, mapping color to, 26-17
locking, 2-13
login, 12-3
saver, customizing, 9-14
Screen dialog box, 9-14
screens
configuring multiple, 13-14
how HP VUE supports multiple,
13-14
multiple, 13-15
script
login and logout, system-wide,
12-7
scrollBar resource, 25-7
scrolling
contents of window, 3-19
text in Text Editor, 7-9
searching for text in Text Editor,
7-13
searching online help (keyword
index), 4-8
search path, actions, 19-24, 19-25
security
Broadcast Message Server, 22-22
display access, 22-23
locking the display, 2-13
network: configuring, 22-21
NFS, 22-21, 22-24
Index-25

selecting
backdrop, 9-10
directory, 5-9
file, 5-9
font size, 9-9
icon, 5-9
multiple directories, 5-10
multiple files, 5-10
multiple icons, 5-10
multiple objects, 5-10
object, 5-9
palette, 9-4
text in Text Editor, 7-10
toggle or radio button, 3-17
server
action server definition, 22-3
application server definition, 22-2
audio server, starting, 13-25
file server definition, 22-2
foreign, 13-4
R4, 13-4
session server, configuring, 22-28
session server example, 22-29
starting on each display, 13-9
starting on each node, 13-6
X server, running different, 12-8
session
canceling, 2-5
changing startup, 9-16
creating display-independent, 28-5
customizing, 15-7
display-dependent, 15-9
ending, 2-4
executing additional commands at
startup, 15-8
fail-safe, 15-10
first, 15-7
first HP VUE, 15-6
first HP VUE 3.0 after using HP
VUE 2.01, 28-4
first HP VUE Lite, 23-5
Index·26

how Login Manager starts, 12-13
HP VUE Lite, 23-3, 23-6
in different languages, 2-5
networked, 22-28
non-English, 27-2
session data location, 15-3
setting sys. resources for first,
25-10
setting variables for current, 14-6,
14-7
starting HP VUE, 2-2-15
starting HP VUE Lite, 23-4
termination, 12-14
types other than Regular, 2-6
using only HP VUE Lite, 23-3
sessionetc file, 15-8
session management, moving from
HP VUE 2.01 to HP VUE 3.0,
28-4
Session Manager, 15-2
how it chooses session type, 15-5
how it works, 15-3
HP VUE Lite, 23-3
location of configuration files, 28-3
multiple screens, 13-14
restoring remote applications,
15-11
starting Workspace Manager, 15-9
session server
configuring, 22-28
definition, 22-28
example, 22-29
using, 22-29
session startup
executing additional commands,
15-8
script, 15-8
session type, how Session Manager
chooses, 15-5
setting
appearance of locked display, 2-14

different system-wide environment
variables for each display, 13-13
environment variables for Starbase
applications, 13-18
foreground color, 26-14
Front Panel decorations, 24-13
palettes, 26-10
personal environment variables,
14-10
subpanel decorations, 24-13
system-wide environment variables,
14-6
system-wide language, 14-9
window frame color manually,
24-14
X server variables, 14-6
shadows, pixmap, 26-13
shell
invoking in action, 21-28
used in action, 21-11
shell environment file, using with
.vueprofile, 14-11
SHELL environment variable, 12-7,
14-4
sh, used in actions, 21-11
S-ICON field
for actions, 21-29
for filetype, 20-14
size
file icon, 20-15
icon, 21-30
icons, 16-23
skills, basic
file management, 5-9
window management, 3-2
sliders, using, 3-24
Softbench
installing HP VUE over, 13-21
moving to HP VUE from, 13-21
on same system as HP VUE, 13-21
quitting, 13-23

removing, 13-22
running HP VUE if have customized
Softbench, 13-22
softenv file, 13-21
softini t file, 13-21
softtypes file, 13-21
sort order, changing File Manager,
5-36
special characters, using in Text
Editor, 7-16
specifying
display name in Xconfig, 13-10
icon file, 16-17
remote directory or file, 5-29
remote execution host, 22-7
window frame components, 24-11
spelling, correcting in Text Editor,
7-14
Starbase
colors, 13-17
running Starbase applications,
13-17
setting environment variables,
13-18
starting
action from Terminal Emulator,
23-18
application or utility, 6-5, 6-15
audio server, 13-25
creating drop zone to start terminal,
17-22
failsafe session, 2-6
German Terminal Emulator, 27-6
home session at login, 2-11
HP VUE Lite session, 2-6
HP VUE session, 2-2-15
HP VUE session from X startup
script, 13-19
Icon Editor, 16-4
Japanese Terminal Emulator, 27-5

Index-27

NCS local location broker daemon
at boot time, 13-24
No Windows mode session, 2-6
server on each display, 13-9
server on each node, 13-6
session, how Login Manager starts,
12-13
terminal emulator, 8-3
terminal emulator in HP VUE Lite,
8-12
Text Editor, 7-3
starting Style Manager, 9-2
startup
changing session, 9-16
customizing, 12-7
script for each display different,
13-12
script, HP VUE Lite, 23-4
Startup dialog box, 9-16
string variables in action definition,
19-26
Style Manager, 24-2
changing resources using, 25-5
opening, 9-2
resources, 26-22
starting, 9-2
subdirectory
adding to Personal Toolbox, 6-5
navigating to, 5-21
subpanel
adding, 17-14
adding or removing control, 17-14
choosing control from, 3-15
configuring, 17-11
displaying, 3-15
subpanel configuration file, 17-11
creating, 17-13,23-14
editing system-wide, 17-12
subpanel decorations, 24-13
subpanelDecorat ions resources,
24-13
Index·28

subpanel, printers
adding another printer control,
18-10
configuring control in, 18-8
subpanel, Terminal
creating configuration file, 23-9
Sub-Process Control Daemon, 13-21
summary
fields in COMMAND action, 21-22
fields in MAP action, 21-23
switch, configuring workspace, 17-25
Switch control
location in Front Panel, 17-14
symbolic link, creating, 5-18
syntax
actions, 21-21
button binding, 24-24
filetype definition, 20-9
keyboard bindings, 24-29
resource specifications, 25-12
Window Manager resource, 24-34
Workspace Manager menu, 24-18
sys.res.lite, 23-5
setting for VUE Lite, 25-11
sys . resources, setting for first
session, 25-10
sysrm command, 13-22
sys.ses.lite, 23-4
system
accessing remote, 5-26
adding access to remote, 5-28
moving or copying directory to
remote, 5-27
moving or copying file to remote,
5-27
opening directory in remote, 5-26
running terminal emulator on
another, 8-9
system administration, language,
27-12
system resource files, 25-16

system subpanel configuration files,
17-11
system timeout, configuring, 2-15
system-wide
action, 19-15
action, adding in HP VUE Lite,
23-18
action for remote application, 22-8
environment variables, different
for each display, 13-13
filetype, 19-15
filetype, creating, 20-8
resources, 25-10
scripts at login and logout, 12-7
subpanel configuration file, editing,
17-12
sys.vuewmrc, 24-3
T

terminal
changing default, 18-3
create drop zone that starts, 17-22
supporting XDMCP, 13-4
Terminal
adding in HP VUE Lite, 23-8, 23-9
button, 8-3
slide up menu, 8-12
TERMINAL action window type,
21-31
terminal configuration, 18-2
terminal emulator, 8-2-13
in fail-safe session, 2-8
in HP VUE Lite, 8-12
Terminal Emulator
changing default, 18-4
configuring in HP VUE Lite, 23-7
customizing, 8-8
German, 27-6
non-English, 27-5
starting action from, 23-18
starting and stopping, 8-3

starting in Japanese, 27-5
using, 8-6
Terminal subpanel
adding control, 23-8, 23-9
creating configuration file, 23-9
customizing, 23-8
terminal window
opening in current directory, 5-21
terminating
session, 12-14
Softbench, 13-23
testing action, 19-22
text
cutting and pasting, 8-6
cutting and pasting in windows,
3-23
editing, 7-2-18
editing in field, 3-22
entering into empty field, 3-22
text annotation, 10-7
editing, 10-8
Text Editor
browsing file to include, 7-12
checking and correcting spelling,
7-14
clearing text, 7-11
closing, 7-4
copying text, 7-11
cutting and pasting text, 7-11
deleting text, 7-11
editing text, 7-8-11
entering text, 7-8
finding or searching for text, 7-13
formatting document, 7-17
including or inserting file, 7-12
justification, 7-17
margins, 7-17
moving cursor in document, 7-9
moving text, 7-11
opening document, 7-5
printing document, 7-18
Index·29

replacing text, 7-11, 7-13
saving document, 7-5
saving document to new file, 7-7
saving document to original file,
7-7
scrolling, 7-9
selecting text, 7-10
special characters, 7-16
starting, 7-3
undoing edit, 7-11
unselecting text, 7-10
using, 7-2-18
word wrapping, 7-8
Text Review dialog, 10-4
timeout, 2-13
configuring system, 2-15
locking, 2-15
timezone, setting, 14-8
title bar, 24-11
toggle button, selecting, 3-17
toggle control, creating, 17-19
toolbox
adding action, 19-21
defined, 19-20
directory locations, 19-20
using, 6-2
Toolbox
General, 6-9
toolboxes
HP VUE 2.01, 28-9
Toolbox, General
opening, 6-9
Toolbox, Network, 6-11
adding host, 22-19
opening, 6-12
Toolbox, Personal, 6-4
adding application to, 6-7
adding subdirectory, 6-5
opening, 6-4
tools

Index-3D

displaying HP VUE 3.0 tools from
HP VUE 2.01 Front Panel,
28-10
in HP VUE Lite, 6-15
Tools control (HP VUE Lite), 23-12
Tools control (HP VUE Lite), assigning
an application, 23-12
Tools control(HP VUE Lite), assigning
an application, 23-13
tools in HP VUE Lite, 6-14
Tools subpanel
adding control, 23-12, 23-13, 23-15
using Create Action, 23-16
tool subpanel, configuring, 17-11
trans ientDecorat ion resource,
24-11
Trash Can
emptying, 5-25
opening, 5-23
putting directory in, 5-24
putting file in, 5-24
putting object in, 5-24
restoring object from, 5-24
using, 5-23
troubleshooting actions, 19-22
ttyModes resource, 25-7
typeface
scalable, 26-3
TYPE field, 17-42,21-30
types of boxes, 17-42
types of images, 16-2
TZ (timezone) setting, 14-8
U
undoing edit in Text Editor, 7-11
unlock display,configuring, 22-21
unlocking display, 2-13
unselecting text in Text Editor, 7-10
update
Login Manager files, 28-3
update .log file, 29-4

useMessaging resource, 13-20

starting in HP VUE Lite, 6-15

user, action running as different,
21-19
user-based remote authorization,
22-23
USER environment variable, 12-7,
14-4

vueaction, 21-18, 23-18

user-prefs

customizing, 18-3
user-prefs. vf, 23-7, 23-8

contents, 18-3
user-prefs. vf
remapping actions, 18-3
using
action created by Create Action,
19-7
action to run remote application,
22-5
controls in application windows,
3-17
Create Action, 19-4
custom workspace menu, 24-20
Desktop, 5-30
dynamic color, 26-15
Front Panel, 3-11
home session, 2-10
Icon Editor, 16-4
menus, 3-25
non-English data, 27-8
No Windows mode, 2-9
resources, 25-2
shell environment file with
.vueprofile, 14-11
sliders, 3-24
terminal emulator, 8-6
toolboxes, 6-2
Trash Can, 5-23
utility
adding in HP VUE Lite, 23-12
Create Action, 19-4
starting, 6-5, 6-15

V
variable, PATH, 21-7
variables
built into Login Manager, 14-4
set by Xsession, 14-5
setting for current session, 14-7
setting X server, 14-6
variables, environment, 14-2, 19-27
different for each display, 13-13
how handled during remote
execution, 22-10
setting personal, 14-10
setting system-wide, 14-6
Starbase applications, 13-18
Xstartup, 12-7
variables in definition, string, 19-26
viewing
database errors, 19-24
remote directory, 22-24
views, controlling File Manager, 5-36
view style, changing File Manager,
5-37
vueaction, 19-22
VUEACTIONSEARCHPATH
environment variable, 19-25
vueaction utility, 21-18, 23-18
vueconvert, 28-14
vueconvert utility, 28-13
vuegreet, 12-12, 12-13
vuehello, 12-12, 12-13, 23-6
VUE Lite
setting sys .res .lite, 25-11
vueli te resource, 23-3
vueli tesession script, 23-6
vuelogin, 12-12
default DISPLAY value, 14-9
environment variables built in,
14-4
Index·31

how it works, 12-13
resource, setting language with,
27-13
resources for each display, different,
13-11
user-specific files, 12-13
vueli te resource, 23-3
.vueprofile

setting LANG, 27-13
. vueprof ile file, 12-13

when read, 12-13
vuesession, run by vuelogin, 12-13
vuewm, 24-2

running without HP VUE, 13-20
vuewmrc, 17-3, 24-3, 24-4

W
white background (in help windows),
4-9
wildcards, matching, 5-33
window
basic skills, 3-2
changing order of overlapping
windows, 3-6
closing, 3-4
customizing behavior, 9-15
cutting and pasting text in, 3-23
displaying, 3-4
focus policy, 9-15
iconify, 3-4
moving, 3-5
opening, 3-4
putting in multiple workspaces,
3-9
raising, 3-6
resizing, 3-6
root, 24-8
scrolling contents of, 3-19
turning into icon, 3-4
type used by action, 19-5
using controls in application, 3-17
Index·32

window behavior, HP VUE or
OSFIMotif, 24-33

window components, customizing,
24-10
window control, client, 17-20
Window dialog box, 9-15
window focus policy, 9-15
window frame
color, 24-14
components, 24-11
elements, 24-10
window icon, moving, 3-5
window manager
changing, 15-9
running from startup script, 13-19
running without HP VUE, 13-20
Window Manager resource syntax,
24-34
window menu, 3-27,24-17
button, 8-5
creating, 24-21
WINDOW-TYPE field, 21-31
wmStartupCommand resource, 13-19,
15-9
word wrap, turning on and off, 7-8
workspace
adding, 17-24
colors, changing, 9-4
customizing, 24-6
displaying another, 3-7
menu, 24-17
menu, custom, 24-20
putting window in multiple
workspaces, 3-9
renaming, 3-8
resources, 24-12
starting clients in, 23-4
switch, configuring, 17-25
using keys to move around in, 3-10
workspaceList resource, 23-4, 25-7
Workspace Manager

configuration file, 24-3
configuration file, creating, 17-3
customizing, 24-2
menus, 24-17
menu syntax, 24-18
reference, 24-34
Workspace menu, 3-29
Workspace Menu
logout command, 2-4
Workspace switch
location in Front Panel, 17-14

x
XO .hosts file, 22-23
XII
environment variables, 28-17
integrating resources, 28-17
moving to HP VUE 3.0,28-17
startup script, replacing for HP
VUE, 28-18
startup script, replacing for HP
VUE Lite, 28-19
XAUTHORITY environment variable,
12-7, 14-4
. Xauthori ty file, 12-13
Xconfig, display name, 13-10
Xconfig file, 12-12, 12-13
XDMCP
protocol, 13-4
terminals supporting, 13-4
'Xerrors" file, 29-4
xhost command executed by action,
22-23
xhosting remote action, 22-23
X*hosts file, 15-11
xinitcolormap, 13-17
XLFD, 26-3, 26-7
X Logical Font Description, 26-3,
26-7
xrdb
adding resources using, 25-7

replacing resources using, 25-8
Xreset file, 12-12, 12-14
Xreset script, 12-7
Xresources file, 12-12, 12-13
xrm command-line option, 23-4
X server
running different, 12-8
setting system-wide variables, 14-6
stopping, 2-5
stopping temporarily, 2-9
Xservers file, 12-12, 12-13
editing for X-terminals, 13-5
Xsession
file, 12-12, 12-13
file, editing for Starbase, 13-17
online help search path, 4-19
variables set by, 14-5
Xsession
after update, 28-3
xsetroot, executing at session
startup, 15-8
Xstartup environment variables,
12-7
Xstartup file, 12-12, 12-13
for customizing startup, 12-7
X startup script, running HP VUE
session from, 13-19
xterm, 8-2, 8-12
X-terminal access to host, limiting,
13-4
X-terminals
configuring, 13-4
editing Xservers for, 13-5
protocols, 13-4
X-terminal, using workstation as,
13-5
XUSERFILESEARCHPATH variable,
27-14
Z
zone, creating drop, 17-17
Index·33

r/i~ HEWLETT

a!1!.tI

PACKARD

Reorder No.
Bl171-90061

Manufacturing
Part No.
Bl171-90061

1111111111111111111111111111111111111111111111111111111111111111111111

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37
Create Date                     : 2012:09:26 09:20:46-08:00
Modify Date                     : 2012:09:26 11:09:02-07:00
Metadata Date                   : 2012:09:26 11:09:02-07:00
Producer                        : Adobe Acrobat 9.52 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:7256cad5-6248-4b94-b4c3-05408e987351
Instance ID                     : uuid:3267c990-6184-4ee9-96b6-654ca451e329
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 686

EXIF Metadata provided by EXIF.tools

B1171 90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 90061 HP Visual User Environment 3.0 Users Guide Jul92

B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 user guide pdf -FilePursuit

B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92 B1171-90061_HP_Visual_User_Environment_3.0_Users_Guide_Jul92

Navigation menu

Versions of this User Manual:

Views

Navigation