Conference bulova::decw_jan-89_to_nov-90

    I would also be interested in any help
    
    						Regards,
    							Sylvie

    Ultrix has implemented it, but VMS has not.  Under Ultrix, the
    Xprompter has a switch will allow you to run an application which
    displays a logo instead of the Digital logo.  Ultrix also allows
    the  user to disable the logo completely through the resource
    	displayLogo:		no
    found in /usr/lib/X11/app-defaults/XsessionManager resource file.
    
    Now what about VMS.  I have tried specifying the above resource
    in DECW$LOGIN.DAT with no avail.  I am almost positive the VMS will
    not allow LOGINOUT/DECW$LOGINOUT to execute another process just to
    display a logo.
    
    Here is a possible workaround.  You could write a program which will
    display your own logo after the Digital Logo appears (checking to see
    if a window at the appropriate location and size exists by querying the
    server).  Your logo would have to occlude the Digital logo.  Once the
    window id for the Digital logo is obtained by your program, set a 
    DestroyNotify event on that window so that when it goes away, your 
    application exits.  You might have to play around with override redirect 
    so the window manager would not attempt to put any dressings on the 
    window if it happened to start up before you application exits.  The
    application should probably be place in DECW$STARTAPPS.COM after the
    start of DECW$STARTLOGIN.EXE.  You should avoid editing the DECW$*.COM
    files; however, so that your logo is displayed correctly with all uses of 
    DECW$STARTUP.COM (restarts and server only starts) it is appropriate
    here.
    
    Just an idea.
    
    David
    

    Gee, we planned to have a logical which would allow you to run an
    arbitrary image as an alternative to the DEC logo.  I'm not sure what
    the status of this is, though.  Maybe the decw$loginout will answer.
    
    Burns

    You can turn off the Digital Logo by defining the logical 
    DECW$LOGIN_BACKGROUND.
    
    	$ define/system/exec DECW$LOGIN_BACKGROUND "TRUE"
    
    This will prohibit the Digital logo from appearing at all.  However,
    I was unable to get the alternate image to work. It involves a command
    procedure and defining decw$display/SYSTEM (which is not recommended)
    and other gyrations.  Maybe someone else will have better luck.
    
    David
    

    
    This should work for VMS in V2.  You need to 
    	
      define/sys/exec decw$login_background filename
    
    DECwindows loginout will translate the logical name and if it is
    defined, will do a CREPRC with sys$input = filename and
    sys$output = WSA device.   When your program does an XOpenDisplay,
    it will see that sys$output is a WSA device and connect to the
    correct display.
    

    re: .2
    
    Okay, in the Ultrix world, how would I go about:
      1) Setting the switch to the Xprompter - I cannot find this in
    the documentation and
      2) How would I go about actually changing the logo? If we can
    demo this to the customer, it would be great.
    
    Thanks for your help.
    
    /jim
    

1.  Putting a -nologo on the Xprompter command line will get rid of the logo.

2.  There is no provision that I can see for an alternate logo.

				Jeff

    Is it possible that there is a file with the bitmap for the
    Digital logo in it?  If there is such a file it should be possible
    to either modify it or change the filename that Xprompter is
    looking for.
    
    I also have a customer that has been digging through their UWS
    system trying to get their logo to be displayed.  They are now
    playing with alternate login programs from the X11 distribution.
    Any help with this would be greatly appreciated!
    

On UWS, you can get rid of the logo, but you can't replace it with
one of your own choosing.
				Jeff

    Now that V5.3 of VMS is out and has V2 of DECwindows, can we replace
    the DEC logo with one of our own?
    
    Mike
    

    Yes, but you need to be willing to put some effort into it.  See note
    248 in the ELKTRA::DW_EXAMPLES conference.

                 Dave

    For those unwilling to work, but willing to take someone else's logo, I
    offer the following:
    
    DDIF::SYS$SYSTEM:CDA_LOGO.COM and .EXE -- CDA Program's logo
    DDIF::SYS$SYSTEM:FLAMINGO.COM and .EXE -- VAXTPU's logo
    
    Just copy them to your SYS$SYSTEM: and...
    
    $ DEFINE /SYSTEM /EXEC DECW$LOGIN_BACKGROUND SYS$SYSTEM:CDA_LOGO
    	-or-
    $ DEFINE /SYSTEM /EXEC DECW$LOGIN_BACKGROUND SYS$SYSTEM:FLAMINGO

    re -1
    
    Name a conference room after that man!
    
    :-)

$ MCR Xphoon
$ Stop/Id=0
$
    

  "DECW$LOGIN_BACKGROUND" = "SYS$MANAGER:DECW$LOGIN_BACKGROUND"

$  set noon
$ xg :== $xgif
$ set display/create wsa0:
$ set def sys$manager
$ xg EDWARD_BARTON-SANCTUARY_PAINTING.GIF  -e 2
$logout:
$logout

Re .12

Thanks for the files Mark, but when I run them I get an error because I have no
VAXCRTL.EXE file.  I'm running Desktop VMS on a Pvax - what's the problem?

brian

    XSetRoot works very nicely for displaying a picture in the login screen
    background...

re: .16

DESKtop VMS V1.0 uses DECwindows V1, which doesn't have the background
login feature.

Jeff

The way that you nuke the DEC logo and replace it with something else
is different between VMS and ULTRIX DECwindows (no, really??).  Attached
is how to do it on ULTRIX.  I've removed the engineers names to protect
them.

This is just a re-gurgitation of what they said.  The only thing I did
was ask.

g.

Subject: using DPS logos with the 2.2/4.0 Xprompter


The UWS 2.2 (and therefore, UWS 4.0) version of Xprompter supports
user-specified Display Postscript logos which override the Digital
bitmap.  It is not currently possible to specify X bitmaps which
override the Digital bitmap.

First, I'll list the X resources which affect the prompter logo, then
give some examples of their use, and finally add some general comments
and warnings.


RESOURCES
- ---------

The X resources which control prompter logo behavior are:

	XSessionManager*initializeDPS
	XSessionManager*logoFile
	XSessionManager*logoColor
	XSessionManager*logoBw
	XSessionManager*logoFullScreen
	XSessionManager*logoSaver
	XSessionManager*saverInterval

*initializeDPS

	This indicates whether the prompter initializes the Display Postscript
	(DPS) extension in the server.  This takes noticable time on slower
	machines, and uses colormap cells.  This is necessary in order to use
	a DPS prompter logo.  Defaults to True.

*logoFile

	This specifies the Ultrix filename which contains the postscript for a
	DPS logo.  Defaults to "", which makes the prompter use the standard
	Digital bitmap as a logo.  This resource must be set in order for
	any of the following resources to have any effect.

*logoColor

	The prompter sets the initial color of the DPS context to the X color
	specified by this name before running the DPS logo program, on color
	displays.  Defaults to "MediumBlue."  The DPS logo program may or may
	not use	this information.

*logoBw

	The prompter sets the initial color of the DPS context to the X color
	specified by this name before running the DPS logo program, on black
	& white displays.  Defaults to "White."  The DPS logo program may or
	may not use this information.

*logoFullScreen

	This indicates that the DPS context should be given the entire screen
	area to draw in.  Otherwise, it has only the area above the prompter's
	dialog box.  Defaults to False.

*logoSaver

	This indicates that the DPS program should be used as a screen saver
	(i.e. it actively changes the display).  Instead of using the normal X
	screen saver, the prompter hides its dialog box after a specified idle
	interval (see *saverInterval below).  Defaults to False.

*saverInterval

	Used in conjuction with *logoSaver set to True, this is the number of
	seconds of idleness before the prompter hides its dialog box and
	leaves just the DPS logo dislayed.  Defaults to 300 (five minutes).


EXAMPLES
- --------

The usual place to set these resources is not your .Xdefaults file,
since Xprompter runs as root, which is usually not you.  If you have
your own file system, setting these resources in /.Xdefaults or adding
them to /usr/lib/X11/app-defaults/XSessionManager will work equally
well.  If you share /usr then changing the app-defaults file will
affect all machines sharing /usr, while changing /.Xdefaults will
affect only yourself.

Suppose I had a postscript logo in the file
/udir/mikey/logos/my_logo.ps, and this logo said "Mikey" instead of
"Digital" just above the prompter's dialog box Then, I could add the
following line to /.Xdefaults:

	XSessionManager*logoFile: /udir/mikey/save/logos/my_logo.ps

If I had a logo which drew a box around the entire screen, I would
instead add:

	XSessionManager*logoFile: /udir/mikey/save/logos/box_logo.ps
	XSessionManager*logoFullScreen: true

Finally, if I had an active, full-screen DPS logo which changed the
screen contents continuously and which could act as a screen saver
(with the dialog box staying up for 1 minute), I would instead add:

	XSessionManager*logoFile: /udir/mikey/save/logos/active_logo.ps
	XSessionManager*logoFullScreen: true
	XSessionManager*logoSaver: true
	XSessionManager*saverInterval: 60


COMMENTS/WARNINGS
- -----------------

Your DPS logo program should begin with a blank line or comment, due
to a bug in the prompter code that wasn't discovered until too late.

If your DPS logo program produces any text output, it will be saved in
the file /tmp/Xprompter.PSerr.  This is most useful for determining
why your DPS logo dies when trying to displaying itself.  Note that
this file is cleared the next time Xprompter runs and tries to use a
DPS logo.

The DPS context that your DPS logo program starts up in will have
clippath defined to be the rectangular area just above the prompter
dialog box (if *logoFullScreen is False), or the entire screen area
(if *logoFullScreen is True).  Your program can use this to "center"
itself, if necessary.

If you want to allow the user to change a single color in your logo
display, or if you want to use different colors for color and
monochrome displays, you should probably save the initial state of the
context as the prompter uses setrgbcolor to set the initial color
based on *logoColor or *logoBW and the screen depth.

Since your DPS logo program executes within the DPS context of the
server, you should be careful about what it does.  For instance,
active programs which run continuously should not have memory leaks in
them.  Otherwise, they will cause the server to grow without bound and
ultimately, crash the server.

My customer has been using the suggestions in here to great effect.  They
especially think it's "cute" to put the IBM logo on the VAXstations screen.

But they want to put their own company logo on the login screen, and need
more room than is available.  Or, as was said in DW_EXAMPLES:

>          <<< ELKTRA::NOTESPUBLIC:[NOTES$LIBRARY]DW_EXAMPLES.NOTE;1 >>>
>                           -< "DECwindows examples" >-
>===============================================================================
>Note 248.20               Login Image Customisation?                   20 of 27
>GSRC::MARKEY "Stand and Deliver!"                   11 lines   1-FEB-1990 16:38
>                     -< what about moving the login box? >-
>-------------------------------------------------------------------------------
>    Many thanks to TASTY::JEFFERY for the deflogin.c that automagically
>    calculates the image window location form the file.  Got it up and
>    working just fine with that help!
>    
>    One more question, though.  Is it possible to redefine the location of
>    the login box itself?  Something like dropping it down so that a larger
>    image can be displayed?  Any ideas?
>    
>    Thanks,
>    
>    Ron

There were no responses to that question in DW_EXAMPLES.  Any ideas from the 
readership of this file?  Thanks in advance.

-- Ken Moreau

    Hacky, but it works:
    UFP::SYS$PUBLIC:LOGO.C and LOGO.BIT. (Make your own picture, of course)
    locates the login window and moves it to the bottom edge of the screen
    before displaying the logo.
    	-Rick

The info in .19 comes closer.  My normal old .ps files vanish once they are 
drawn.  How can I make them stay?  

More importantly, to me, are my executable display programs. DPS is black magic.
I have toys which draw animated displays in normal X11 mode, I can even make
"pyro" work from /usr/examples/dps.  But these are executable images, not 
PostScript files.  How do I make the leap into an executable?

\bob