| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 27.1 | | CSSE32::MERMELL | Window Pain | Thu Jan 26 1989 22:30 | 7 |
| VMSKIT""::SYS$KITS:[VMS051.DOC_LINE]
VMSKIT""::SYS$KITS:[VMS051.DOC_LN03]
VMSKIT""::SYS$KITS:[VMS051.DOC_ONLINE]
VMSKIT""::SYS$KITS:[VMS051.DOC_POST]
Note that only the Postscript and Online files are complete.
|
| 27.2 | this is be kind to VMSKIT week | PSW::WINALSKI | Paul S. Winalski | Thu Jan 26 1989 22:39 | 4 |
| Also in PAGODA::DISK$PLATYPUS:[VMS051.DOC_ONLINE] for the online docs.
--PSW
|
| 27.3 | And behind door number 3 we have ... | GOFER::HARLEY | He'd steal flies from a blind spider... | Fri Jan 27 1989 01:08 | 4 |
| ... MPGS::Sys$Kits:<VMS051.DOC_mumble>
/Harley
|
| 27.4 | Guide to Application Programming
| JGL::JLENIHAN | Byte Twiddler | Fri Jan 27 1989 07:28 | 13 |
| Anyone know where I can finda Postscript copy of
VMS DECwindows Guide to Application Programming....
which seems to in the BOOKreader but not in any of the other Documentattion Kits.
Thanks
>> j.
|
| 27.5 | Order number? | REGENT::MERSEREAU | | Mon Jan 30 1989 20:03 | 8 |
| 27.6 | VMSKIT::SYS$KITS:[VMS051.DOC_POST] | DECWIN::FERGUSON | Jim Ferguson - VMS Development | Tue Jan 31 1989 13:31 | 11 |
| Re: .4
"VMS DECwindows Guide to Appliation Programming:"
Directory VMSKIT""::SYS$KITS:[VMS051.DOC_POST]
DECW_TOOLKIT_GUIDE.PS;1 5708 3-JAN-1989 09:05:05.00
Total of 1 file, 5708 blocks.
|
| 27.7 | 'Official' documentation order numbers | EEMELI::HAKALA | Tuomo Hakala, ES Finland | Thu Feb 02 1989 16:19 | 44 |
| RE: .5
> Does anyone know the part number for the "official" documentation
> (with the binders, etc.).
I got the following list of documentation part numbers when asking
the course material order numbers. Hope this helps.
- Tuomo
REFERENCE LIST (Order from Printing
and Circulation Services)
Overview of VMS DECwindows AA-MG17A-TE
VMS DECwindows User's Guide AA-MG18A-TE
VMS DECwindows Desktop Applications Guide AA-MG19A-TE
XUI Style Guide AA-MG20A-TE
UWS Reference Pages AA-MA85A-TE
UWS Introduction to the UWS User Environment AA-MA86A-TE
UWS DECwindows User's Guide AA-MA87A-TE
UWS DECwindows Desktop Applications Guide AA-MA88A-TE
VMS DECwindows Guide to Application Programming AA-MG21A-TE
VMS DECwindows Guide to Xlib Programming:
MIT C Binding AA-MG24A-TE
VMS DECwindows Guide to Xlib Programming:
VAX Binding AA-MG25A-TE
VMS DECwindows Xlib Routines Reference Manual
Part 1 AA-MG26A-TE
VMS DECwindows Xlib Routines Reference Manual
Part 2 AA-MG27A-TE
UWS Guide to the Xlib Library: C Language
Binding AA-MA97A-TE
VMS DECwindows User Interface Language
Reference Manual AA-MG22A-TE
VMS DECwindows Toolkit Routines Reference
Manual AA-MG23A-TE
UWS Guide to the Xtoolkit Widgets: C Language
Binding AA-MF09A-TE
UWS Guide to the XUI Toolkit Intrinsics:
C Language Binding AA-MA96A-TE
January 26, 1989
|
| 27.8 | Q's are better that AA's ... | CIM::KAIRYS | Michael Kairys | Thu Feb 02 1989 17:33 | 97 |
| I extracted (and condensed) the following from the VMS 5.1 Release
Notes, copied from VMSKIT::SYS$KITS:[VMS051]VMS_RELEASE_NOTES.TXT.
Note that ordering the Documentation Kits by Q number is often the only
way to get binders and spine inserts to go with the books.
Documentation Information
5.2 New Documentation for VMS Version 5.1
Table 5-1 lists the order numbers for general VMS
Version 5.1 documentation. See the Overview of VMS
Documentation for information on ordering other VMS
manuals and kits.
Table 5-1 General VMS Version 5.1 Documentation
_______________________________________________________
Manual____________________________________Order_Number_
VMS Version 5.1 Installation Guide AA-MG15A-TE
VMS Version 5.1 Release Notes AA-MG16A-TE
VMS Version 5.1 New Features Manual AA-MG29A-TE
_______________________________________________________
The order number for the DECwindows User Documentation
Kit is QA-09SAB-GZ. This kit contains the manuals
listed in Table 5-2.
Table 5-2 DECwindows User Documentation Kit Contents
_______________________________________________________
Manual____________________________________Order_Number_
Overview of VMS DECwindows AA-MG17A-TE
VMS DECwindows User's Guide AA-MG18A-TE
VMS DECwindows Desktop Applications AA-MG19A-TE
Guide
_______________________________________________________
The DECwindows Programming Documentation Kit is a
multi-volume set divided into separately orderable
Volumes 1, 2 and 3. The order number for the entire
DECwindows Programming Documentation Kit is QA-001AM-
GZ. This kit contains the following three volumes:
o Volume 1 - Application Programming, order number
QA-001A5-GZ. This volume contains the following
manuals:
____________________________________________________
Manual_______________________________Order_Number___
XUI Style Guide AA-MG20A-TE
VMS DECwindows Guide to Application AA-MG21A-TE
Programming
VMS DECwindows User Interface AA-MG22A-TE
Language Reference Manual
VMS DECwindows Toolkit Routines AA-MG23A-TE
Reference Volume Part 1
VMS DECwindows Toolkit Routines AA-MK88A-TE
Reference_Volume_Part_2_____________________________
o Volume 2 - Xlib Programming, order number QA-001A6-
GZ. This volume contains the following manuals:
____________________________________________________
Manual_______________________________Order_Number___
VMS DECwindows Guide to Xlib AA-MG24A-TE
Programming: MIT C Binding
VMS DECwindows Guide to Xlib AA-MG25A-TE
Programming: VAX Binding
VMS DECwindows Xlib Routines AA-MG26A-TE
Reference Manual Part 1
VMS DECwindows Xlib Routines AA-MG27A-TE
Reference_Manual_Part_2_____________________________
o Volume 3 - Device Driver/CDA, order number QA-
001A7-GZ. This volume contains the following
manuals:
Manual_______________________________Order_Number___
VMS DECwindows Device Driver Manual AA-MG28A-TE
VMS Compound Document Architecture AA-MG30A-TE
Manual______________________________________________
|
| 27.9 | ultrix docs? | ODIUM::DOUG | to bless and not to curse | Tue Feb 14 1989 14:27 | 7 |
| is there an ultrix decwindows conference? or should ultrix queries be
placed here? because i'd like to ask the same questions regarding the
ultrix docs as have been answered for the vms docs. ie, where are they
on the net, and what are the order numbers?
thanks
-- dd
|
| 27.10 | Check GURU:: | MTA::GRAHAM | the beat is tough and jazzy | Wed Feb 15 1989 00:46 | 30 |
|
A decnet directory listing of node 'guru' yielded the following:
# dls -l guru::~guest/
Directory GURU::/usr/users/guest/
JIG4A_VAXINE.COM;32767
-rw-r--r-- 02-FEB-89 18:59:53 8318
UWS drwxr-xr-x 02-FEB-89 09:35:35 512
WRITE_REFERENCE.PS;1
-rw-r--r-- 08-FEB-89 08:21:28 1519652
WRITE_USERS_GUIDE.PS;1
-rw-r--r-- 08-FEB-89 08:30:50 1904485
ZKSECTST.TMP -rw-r--r-- 18-JAN-89 19:54:51 0
ds3100_perform drwxr-xr-x 25-JAN-89 13:30:43 512
f77.lib -rw-r--r-- 04-FEB-89 21:58:02 645120
f77.tar -rw-r--r-- 04-FEB-89 21:25:55 962560
grepper drwxr-xr-x 16-DEC-88 15:11:29 512
libF77.a1.31 -rwxr-xr-x 04-FEB-89 21:50:52 178224
ultrix drwxrwxrwx 02-FEB-89 09:36:31 512
ultrix.v24.ft.documents.nroffed
drwxr-xr-x 16-DEC-88 15:11:29 1536
uws drwxr-xr-x 02-FEB-89 09:37:41 512
v2.2 drwxr-xr-x 16-DEC-88 15:11:30
v2.3 drwxr-xr-x 12-JAN-89 11:20:11 512
v2.4-ft-manuals drwxr-xr-x 16-DEC-88 15:11:30 1536
v3.0 drwxr-xr-x 13-FEB-89 11:10:01 512
kris..
|
| 27.11 | Order Number for ULTRIX docs | RAVINE::jeanne | Jeanne --DTN 381-1604 | Wed Feb 15 1989 19:21 | 7 |
| This order number will get you the entire (manuals, binders, spine insrts)
ULTRIX Worksystem Software 2.0 documentation kit:
QA-0JQAA-GZ
-J
|
| 27.12 | Sorry , can't find it. | MUDIS3::FISCAL | Artur Fiscal - Mudis3 | Tue Feb 21 1989 05:31 | 11 |
| Hello world
Trying desperately to get at the location of the documentation on
VMSKIT::SYS$KITS:[VMS051.DOC*]. It's simply not there. I'd greatly
appreciate if it could be made accessible again.
Thanks world.
artur
|
| 27.13 | Try MPGS::Sys$Kits:<VMS051.DOC*> | GOFER::HARLEY | At home, you can scratch where it itches | Tue Feb 21 1989 12:25 | 1 |
|
|
| 27.14 | VMS New Features documentation | MUDIS3::FISCAL | Artur Fiscal - Mudis3 | Wed Feb 22 1989 11:10 | 8 |
|
Thanks for the hint. Could it be possible to put a copy of the
VMS-NEW-FEATURES documentation into the same location. I have only a
fragmentary edition of it.
Thanks in advance
artur
|
| 27.15 | ULTRIX docs | FLUME::griffin | | Fri Feb 24 1989 12:49 | 5 |
| .10 has it partially right for documentation information on GURU -
in ~guest/UWS is two subdirectories: sk (Starter Kit information) and
docs. In the sk should be a pointer to online documentation. In docs is
the overview of each of the UWS documents.
|
| 27.16 | Coming via ADS?? | HPSCAD::FORTMILLER | Ed Fortmiller, MRO1-3, 297-4160 | Fri Mar 17 1989 13:01 | 2 |
| Will the DECwindows documentation be distributed via ADS?
|
| 27.17 | Yes | UKCSSE::LESLIE | Executive Lemming | Fri Mar 17 1989 15:40 | 3 |
| WIth VMS V5.1 Doc, methinks. At least, thats what I was told when I
enquired last week.
|
| 27.18 | | ASIA::MCLEMAN | Jeff McLeman | Fri Mar 17 1989 16:05 | 2 |
| You get the user docs with V5.1, not the programming docs.
|
| 27.19 | VTX ADS | CRLVMS::HALBERT | CRL, Trellis | Fri Mar 17 1989 16:24 | 4 |
| If you type $ VTX ADS , and then look at the FYI menu, you can find a
note explaining this and giving the order number for the programmer
documentation. --Dan
|
| 27.20 | Cannot access postscript docs | BMT::DESANTIS | | Thu Apr 06 1989 13:30 | 15 |
| ref: 27.12 & .13
I'm trying to get access to the postscript docs and keep getting;
error opening MPGS::SYS$KITS:<VMS051.DOC_POST>*.*;* as input
-RMS-E-PRV, insufficient privilege or file protection violation
I can see the on-line docs from:MPGS::SYS$KITS:<VMS051.DOC_ONLINE>
Can someone turn on the access to the postscript docs ?
Thanks
rusty
|
| 27.21 | And now a word from the MPGS system mangler... | GOFER::HARLEY | At home, you can scratch where it itches | Thu Apr 06 1989 15:16 | 9 |
| I have the PS docs protected because various (l)users at my site began mass
printing them, and I figured that I'd rather not see my LPS40 pay the entire
site's FS budget...
If anyone needs access to these files, just send me mail and I'll be glad to
provide copies.
/Harley
|
| 27.22 | Any pointer to SDC version of documentation ? | PRCSWS::NICHOLASHO | Nicholas Ho, PRC SWS, @HGO (Hong Kong) | Thu May 11 1989 04:37 | 26 |
| Hi,
Where can I get SDC version of online documentation of DECwindows
Toolkit and Xlib manuals ? The files in the following location are still
in field test version.
Directory MPGS::SYS$KITS:[VMS051.DOC_POST]
DECW_TOOLKIT_GUIDE.PS;1
4214/4215 24-OCT-1988 21:50:04.00
DECW_TOOLKIT_REF_MANUAL.PS;1
6036/6036 16-NOV-1988 12:59:53.00
DECW_XLIB_REF_PART1.PS;1
3571/3573 28-DEC-1988 10:46:55.00
DECW_XLIB_REF_PART2.PS;1
3076/3078 16-DEC-1988 21:07:29.00
Thanks for any help.
Regards
Nick
|
| 27.23 | for online documents see DECWINDOWS_DOCUMENTATION.NOTE | CSSE32::MERMELL | Window Pain | Tue May 16 1989 16:02 | 6 |
| > Where can I get SDC version of online documentation of DECwindows
> Toolkit and Xlib manuals ?
They're no longer accessible on VMSKIT::. See DECWINDOWS_DOCUMENTATION
note 165.8 for Alternate Sites for Network Kits.
|
| 27.24 | order QA-001AM-GZ | WELWEL::GRAHAM | Hopelessly Hopeful ! | Wed May 31 1989 13:34 | 14 |
| Page 5.2 of the VMS 5.1 release notes says :
The order number for the entire DECwindows Programming Doc kit is
QA-001AM-GZ which is made up of these 3 volumes :
QA-001A5-GZ Application Prog
QA-001A6-GZ Xlib Prog
QA-001A7-GZ Device Driver/CDA
Regards,
Dave
|
| 27.25 | Postscript Previewer Documentation | LDP::GREEN | | Fri Jun 23 1989 15:59 | 5 |
| RE:
Is there any documentation available for the Postscript Previewer that
runs under DECwindows?
|
| 27.26 | | PSW::WINALSKI | Careful with that VAX, Eugene | Fri Jun 23 1989 16:57 | 6 |
| There isn't a PostScript Previewer under DECwindows, at least not in the
official product. It was pulled from the product at the last minute because DEC
and Adobe couldn't come to terms on licensing arrangements.
--PSW
|
| 27.27 | dxpsview ships with UWS | 4981::thomas | The Code Warrior | Fri Jun 23 1989 17:54 | 2 |
| VMS doesn't have a postscript previewer but Ultrix does.
|
| 27.28 | man page for dxpsview | COOKIE::KITTELL | Richard - Architected Info Mgmt | Tue Jun 27 1989 02:29 | 463 |
|
dxpsview(1X)
NAME
dxpsview - DECwindows PostScript previewer
SYNTAX
dxpsview [ options ] [ file ]
ARGUMENTS
file Specifies the file that is to be opened at
startup. If a file is not specified,
dxpsview lets you open a file after it has
started up.
DESCRIPTION
The dxpsview PostScript viewer lets you view files that are
in a PostScript format. At start-up, dxpsview provides a
window that consists of the following four areas:
Title Bar Displays the name of the window, the
name of the file currently being viewed,
and window manager icons that allow you
to iconify, move, and resize the
dxpsview window. For more information,
see dxwm(1X).
Menu bar Lists the available dxpsview menus.
Work area Contains the image of a page generated
by the PostScript document. This window
does not accept input focus and does not
support text selection.
Status area Specifies the current page status and
provides push buttons for viewing the
next or previous page.
OPTIONS
-bd color Specifies the color of the window's
border (color displays only). The
default is black.
-bg color Specifies the color of the window's
background (color displays only). The
default is white.
-d dispname Specifies the display screen on which
dxpsview displays its window. If the
display option is not specified,
dxpsview uses the display screen speci-
fied by your DISPLAY environment vari-
able. The display option has the format
hostname:number. Using two colons (::)
instead of one (:) indicates that DECnet
1
dxpsview(1X)
is to be used for transport. The
default is :0. For more information,
see X(1X).
-display dispname This option is the same as the -d
option.
-geometry Specifies the width, length, and loca-
tion of the dxpsview window. If the
geometry option is not specified, xfd
uses default values. The geometry
option has the format
=[width][xlength][x][y]. For more
information about the screen coordinate
system, see X(1X).
-rv Reverses the default color values (for
example, black becomes white and white
becomes black). The default is to
reverse the color values.
MENUS
The dxpsview application contains the following menus:
File
Page
Options
File Menu
The File menu contains the following menu items:
Open Selected Opens the contents of the file specified
by the currently selected file name. If
the selected file doesn't exist, a file
selection dialog box is displayed
prompting for the name of the file to be
opened. After a file is opened, the
title bar is updated with the newly
loaded file name.
Open... Displays a file selection dialog box
that lets you specify the file to be
opened. If you want to view a file in
another directory or with an extension
other than .ps, just change the File
filter pattern at the top of the dialog
box, and then press the Filter pushbut-
ton to the right. After a file is
opened, the title bar is updated with
the newly loaded file name.
Revisit Current Reopens the current file. This is use-
ful if the file has been modified.
2
dxpsview(1X)
Exit Closes the dxpsview window and exits
from the application.
Page Menu
The Page menu contains the following menu items:
Display number Displays the page before the currently
displayed page. If the currently
displayed page is the first page, this
menu item is disabled.
Display ... Displays a dialog box that prompts for
the number of the page to be displayed.
Display number Displays the page after the
currently displayed page. If
the currently displayed page
is the last page, this menu
item is disabled.
Options Menu
The Options menu contains the following menu items:
Sheet Selection Displays a dialog box that lets you
specify the sheet size on which the
Postscript file is to be displayed.
Changing the sheet size does not change
the size of the dxpsview window.
Instead, the display is formatted (in
length and width) for the sheet size you
specify. The choices are Letter, Legal,
Ledger, Executive, A3, A4, A5, B4, and
B5. The default is Letter. In addi-
tion, the rotation page options let you
specify the angle of rotation at which
the sheet is to be displayed. The
choices are 0, 90, 180, and 270 degrees.
The default is upright (0 degrees).
Use Comments Choosing this option turns comment mode
on or off. In comment mode, dxpsview
attempts to interpret the commens in the
file as hints that allow moving from
page to page more quickly. By default,
comment mode is on. If you try to view
a file but receive an error message, you
may be able to correct the problem by
turning comment mode off and reopening
the file with the Revisit Current menu
item.
Use Bitmap Widths Specifies whether to use the bitmap
3
dxpsview(1X)
widths or scalable widths of the prede-
fined fonts. With scalable widths, the
resulting characters are spaced more
evenly and more legibly, but the right
edge of paragraphs is jagged. With bit-
map widths, the right edge line up but
the character spacing is uneven. Use
bitmap widths for the font placement if
you are viewing the document for form
rather than content. When turned on,
the option does not take effect until a
new file is opened or reopened with the
Revisit Current menu item. By default,
this option is turned off.
Use Fake Trays Specifies that files that contain tray
size directives can be displayed. Some
PostScript files for the LPS40 have tray
size directives included in the docu-
ment. Tray size directives are
PostScript programming language instruc-
tions that tell the printer which tray
size to use. For example, a file might
contain tray size directives that
instruct the printer to switch from the
letter tray (8 1/2 x 11) to the ledger
tray (11 x 17) while that file is being
printed. The viewer does not, however,
permit the addition of these tray size
directives to PostScript files in this
way. If you try to display a file that
contains PostScript tray size direc-
tives, the viewer displays an error mes-
sage. To display this file, acknowledge
the error, choose the Use Fake Trays
menu item, and redisplay the file by
choosing the Revisit Current menu item
from the File menu. By default, this
option is turned off.
COMMANDS
The command region of the dxpsview window contains one label
and two push buttons as follows:
Page Specifies the number of the page
currently being displayed. In most
cases, the label will specify the total
number of pages that can be displayed in
the currently opened file.
Next Page Displays the next page. If the
currently displayed page is the last
4
dxpsview(1X)
page, this command is disabled.
Previous Page Displays the previous page. If the
currently displayed page is the first
page, this command is disabled.
X DEFAULTS
The dxpsview application reads the .Xdefaults file during
startup and uses the appropriate resource specification to
customize the appearance or characteristics of its displayed
dxpsview window. The format for a resource specification in
the .Xdefaults file is:
[name*]resource: value
name Specifies the application name or the name string
that restricts the resource assignment to that
application or to a component of an application.
If this argument is not specified, the resource
assignment is globally available to all X applica-
tions.
resource Specifies the resource.
value Specifies the value that is to be assigned to the
resource.
For more information, see X(1X).
Because each toolkit-based application can consist of a com-
bination of widgets (for example, push buttons and a scroll
bar), you can form the name string by adding widget class
and name identifiers to the string. For further information
about adding class and name identifiers, see X(1X).
For dxpsview, the available class identifiers are:
Label
MainWindow
Menu
PSViewer
Pulldown
PushButton
Scroll
Scrollw
Separator
Window
The class PSViewer must be specified in the .Xdefaults file
when you specify that the resource apply to dxpsview only.
The class PSViewer must be the first element in the specifi-
cation.
5
dxpsview(1X)
For dxpsview, the available name identifiers are:
mainWin Specifies that the resource is to
apply to the dxpsview main window
and not subsequent windows.
commandBar Specifies that the resource is to
apply to the command bar located at
the bottom of the dxpsview window.
The three named items on the com-
mand bar are odometer, next, and
prev.
scrollw Specifies that the resource is to
apply to all dxpsview scroll bars.
vbar Specifies that the resource is to
apply to the vertical scroll bar.
To specify a resource for either
the up or down stepping arrows, you
can add the name ScrollButton1 or
ScrollButton2.
hbar Specifies that the resource is to
apply to the horizontal scroll bar.
To specify a resource for either
the left or right stepping arrows,
you can add the name ScrollButton1
or ScrollButton2.
menuBar Specifies that the resource is to
apply to the menu bar.
Help Specifies that the resource is to
apply to the Help push button.
file Specifies that the resource is to
apply to the File menu. To specify
that a resource is to apply to one
of the menu items displayed in the
file menu, you can specify openSel,
openDialog, revisit, or quit.
page Specifies that the resource is to
apply to the Page menu. To specify
that a resource is to apply to one
of the menu items displayed in the
file menu, you can specify
displayPrev, displayChoose, or
displayNext.
options Specifies that the resource is to
6
dxpsview(1X)
apply to the Options menu. To
specify that a resource is to apply
to one of the menu items displayed
in the file menu, you can specify
trays, comments, bwidths, or fak-
etrays. You can also specify the
separator widget with the name
sep1.
In addition to the general resources listed in X(1X), the
resources available for dxpsview are:
pixmapCacheSize Specifies the number of pages that
dxpsview caches. If the value is
greater than 1, dxpsview can
display previously seen pages more
quickly. However, the greater the
number, the more memory used in the
server. The default is 1.
fileNameSuffix Specifies the file name extension
used by the Open... menu item in
the File menu. The default is ps.
fileNamePrefix Specifies the directory used by the
Open... menu item in the File menu
when searching for a file. The
default is the directory from which
the previewer was invoked.
FILES
~/.Xdefaults
/usr/lib/X11/app-defaults/PSViewer
SEE ALSO
X(1X), dxwm(1X)
7
|
| 27.29 | Careful with those ads | WNDMLL::SCHNEIDER | New lamps for old | Wed Jun 28 1989 03:44 | 13 |
| >There isn't a PostScript Previewer under DECwindows, at least not in the
>official product. It was pulled from the product at the last minute because DEC
>and Adobe couldn't come to terms on licensing arrangements.
In a recent issue of the trade magazine Computer Systems News, there
was a two-page advertisement of ours showing how we have helped Pioneer
solve some problems. Prominently displayed was a workstation screen,
and lo and behold within the Icon Box, I noticed the Postscript
Previewer icon! And FileView had a VMS filespec in its icon! I
suppose one or the other could have been running remotely, but...
Dan
|
| 27.30 | | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Thu Jun 29 1989 19:43 | 4 |
| We were also showing it in the DECtop University. Sigh.
Burns
|
| 27.31 | Who was showing it? | SSPENG::MCCARTNEY | | Fri Jun 30 1989 14:11 | 6 |
| Who showed it at DECtop? I know in the Integration area (where the
DECwindows folks and workstation folks were) we made a point NOT to
show it on VMS Workstations.
Irene
|
| 27.32 | read the fine print in contracts and ads | SMURF::HOFFMAN | anywhere in the universe | Fri Jun 30 1989 14:46 | 24 |
| re .29 and .31
I saw the Computer Systems News ad also and immediately brought
it to the attention of Jim Kelly [?], head of Base Product Marketing.
Yes, there are ways in which the system could have been an
ULTRIX system running the PostScript Previewer locally and
all those SYS$ applications remotely. But that is NOT how
most people would interpret it. Note that running the PostScript
Previewer remotely to other systems probably violates the
contract with Adobe as well, even though we don't have any way
to prevent that. At any rate, ads like that could quickly
convince Adobe's well paid lawyers (and maybe ours, too!)
that Digital is not living up to the terms of the contract
and that Digital doesn't even care enough to try.
PLEASE, keep those lawyers off our computer systems!!!
re .31
We showed PostScript Previewer at DECtop on our ULTRIX systems.
Maybe that's where you saw it. We even ran it across the wire
to neighboring VMS displays, just like we ran BookReader from
VMS on an ULTRIX display. Maybe that's what you saw there.
John
|
| 27.33 | | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Fri Jun 30 1989 14:57 | 8 |
| Sorry, but it was on a VMS system in the VUE menu. I removed it as soon
as I saw it, but it was there for a time.
It was in the area where I, a DECwindows developer, was assigned. Is that
the Integration Area?
Burns
|
| 27.34 | Unusual licensing restrictions should be documented | SX4GTO::ROSE | | Fri Jun 30 1989 16:57 | 6 |
| Re .-2: "Running the PostScript Previewer remotely to other systems
probably violates the contract with Adobe."
Where is this documented, so customers (and even employees) won't do it
if it's wrong?
|
| 27.35 | | LESLIE::LESLIE | Gentlemen! Let's broaden our minds! | Sat Jul 01 1989 06:55 | 7 |
| 27.36 | Talk about legal issues should be left to specialists! | KONING::KONING | NI1D @FN42eq | Wed Jul 05 1989 15:35 | 13 |
| Re .34, .35: I am not convinced that this is so, in particular not in the
case in question.
In any event, non-lawyers would do well to avoid random speculations on
such topics. There are DEC policies that require this -- for the obvious
reason that speculation on legal matters by amateurs is a source of potentially
false information.
If you want answers about this sort of questions, talk to product management
and ask them to state the real rules.
paul
|
| 27.37 | Let's stop this nonsense | SDSVAX::SWEENEY | Honey, I iconified the kids | Wed Jul 05 1989 16:00 | 20 |
| re: 27.36
I'm not convinced that the bashing that .34/.35 took in .36 is
appropriate.
The characterization of its contents as "random speculations" is
unwarranted - "potentially false" indeed. Tell me what _isn't_
potentially false.
It is not speculation but a for-certain-true-fact that licensing
aspects of the distributed computing model of which DECwindows is part
of are incompletely and ambiguously documented.
"Bite your tongue... THIS IS A LEGAL PROBLEM" is a head-in-the-sand
approach and it's getting a little tiresome to read on daily basis.
Of course, product managers ought to be contacted; I'm only beginning
to wonder why they are waiting for us to call them rather than being
"up front" with the information.
|
| 27.38 | | KONING::KONING | NI1D @FN42eq | Wed Jul 05 1989 19:15 | 15 |
| My mistake, I should have hammered on .32, not .34 (which merely quoted
a statement from .32).
I wasn't advocating that anyone stick their head in the sand while waiting
for a lawyer to come along and dig it back out. But I'm concerned about
information posted that relates to terms&conditions, if it looks like it
hasn't been checked out by the people responsible for same. Comments
that you may not be allowed to run product P in situation S may be harmful
if they aren't accurate, since they make people think P isn't a solution to
a problem when it in fact is.
Additional reasons for posting .36 I will pass along off-line.
paul
|
| 27.39 | more on VMS PostScript Previewerv ad | SMURF::HOFFMAN | anywhere in the universe | Thu Jul 06 1989 18:53 | 23 |
| re .32
The name of the person in charge of Base Product Marketing
is Jim Casey, not Jim Kelly as I stated. Sorry about that.
In response to other comments, I will be quite careful in
future statements here and elsewhere regarding what is or
might be proper or legal software. I based my statements
on information provided to me and others regarding the
packaging of the ULTRIX DECwindows software products.
It is very likely that the arrangements with Adobe will
be clarified before too long, so anyone concerned with this
issue should be sure to keep up with the facts.
The point of my comments in .32 was that the people who create
our publicity text and pictures should be very careful about
what gets presented. Those people probably don't read this
notesfile, but perhaps some of their friends do. Some of those
friends might even be engineers who set up the displays for
the photographer. Let's all be careful!
John
|
| 27.40 | | VAXWRK::BSMITH | I never leave home without it! | Thu Jul 13 1989 18:04 | 7 |
| .8 lists the part numbers for the V1 programmers guides. Can anyone
comment on the availability of the V2 guides?? Can someone supply
the part numbers for them??
Thanks,
Brad.
|
| 27.41 | Can't get manuals for products still in field test | CLYPPR::COFFLER | Have you hugged your dog today? | Sun Jul 16 1989 21:06 | 11 |
| re: .-1
Well, since DECwindows V2 isn't even in the SDC, I'd venture to say
that the manuals simply aren't available (in fact, I'd venture to say
that they're changing from day to day).
You should probably check again when DECwindows V2 is out of field test
and available through the SDC ...
-- Jeff
|
| 27.42 | looking for V2.0 documentation | ZORBA::BURACK | Not Fade Away | Thu Feb 08 1990 15:54 | 7 |
| Hi,
I am looking for pointers to the DECwindows Version 2.0 documentation.
Thanks,
Ruth-Ellen
|
| 27.43 | | VMSINT::MFOLEY | Rebel Without a Clue | Thu Feb 08 1990 17:48 | 5 |
|
Order the VMS 5.3 update docs (BY-09SAA-3Z5.3)
mike
|
| 27.44 | want to copy the books, not order them... | CASEY::BURACK | Not Fade Away | Thu Feb 08 1990 20:24 | 8 |
| Hi,
Isn't the documentation available online so I can copy the books that I
need?
Thanks,
Ruth-Ellen
|