Everhart, Glenn From: carl@gerg.tamu.edu Sent: Wednesday, January 06, 1999 9:16 PM To: Info-VAX@Mvb.Saic.Com Subject: Re: DW-MOTIF licence costs. JF Mezei writes... }Dennis.P.Costello@usa.dupont.com wrote: }> VWS does have its uses, though. As old and unsupported as it is, it still runs }> on most modern versions of VMS (on VAXstations, not Alpha). It uses a lot less }> memory than DECwindows, so it's good on resource-tight machines. It provides }> terminal emulators, an application programming interface, and a few OOTB }> applications. } }This is what I am using now. I have VWS license that came with the cheap }vaxstation. Installed both DECwindows and VWS but can't use DECwindows. But so }far, I have only seen the terminal emulators. What other applications are }there ? When VWS was installed it probably created a directory called VWSDEMO on your system disk (in the disk's root directory, not in the system directory tree; at least that's where mine is). It has a variety of interesting demos including: A calendar, calculator, and clock in a program called "[vwsdemo.epas]desk.exe". The excellent "banner.exe" which shows various things (optionally selectable) like a clock, weekday, date, and time, a CPU usage graph, a set of N/U/S/E/K/I time in modes bar graphs, and some other statistics like pages on the free page list and suchlike, plus user definable ones, all in one window - there is also a file called "[VWSDEMO.COM]BANNER.COM" (and possibly one called BAN.COM, although that might be one that I made - the pared down version with only the options I wanted specified; it has been so long that I don't remember if I made that file or if it came with it) that you can run in your SYSPECIFIC.COM to get it running at system startup as a detached process. Several interesting graphics demos - I particularly like [VWSDEMO.FOR]PSYCHO.EXE and ROSE.EXE The ubiquitous sliding numbers puzzle, [VWSDEMO.EPAS]CPUZZLE.EXE. All kinds of other things, some interesting and some not (although they often give good examples of how to do specific things, or comparisons of different options, for writing your own VWS applications). Most of them also have source. There are demos written in Basic, C, "EPAS" (Extended Pascal, or something - it appears to be applications made from some modules written in Pascal (*.PAS) and others in Macro (*.MAR) and others with the extender ".EPAS" which look like Pascal to me), Fortran, Pascal, and PLI. There is also a "master demo menu" to select various demos to run called [VWSDEMO.COM]DEMOMENU.COM (which runs a menu program as a detached process via the DEMOMENU2.COM file, which you could run instead to make it run in your own process), and there's a DEMOLOOP.COM that automatically shows a bunch of them in a loop. There is also Sight - $ HELP SIGHT SIGHT SIGHT (Simple Interactive Graphics Handling Tool) is a gra- phic editor and presentation software tool for use on VMS workstaions. Format SIGHT [input-file-spec] Additional information available: Parameters Logical_names SIGHT Subtopic? which you should be able to set up at system startup with the sys$startup:sight$startup.com file. And there is also a VWS$EXAMPLES logical pointing to some other (less interesting) examples in the SYS$COMMON:[SYSHLP.EXAMPLES.VWS] directory. }By the way, in VWS, is it supposed to be possible to copy from one window and }paste in another window ? Yes. Center button select & copy, right button paste - but possibly only if you have the right logical names defined properly before you open the windows in question. The settings for this are in the sys$startup:uis$setup_vt240.com file, which you should run at system startup - I think the default settings are to allow this, but I may have changed them long ago and not remember. The relevant bits for this are in the sections starting: $! Copy and Paste: $! $! This option enables the transparent Copy (not cut) operation. The COPY $! operation SELECTS a section of text that is coped into a PASTE buffer. There are many options allowing for either stream or rectangular copy, passing or filtering control characters, yada, yada, yada. In my syspecific.com file I have these lines: $ @sys$startup:uis$setup_vt240 $ @sys$startup:sight$startup $ @sys$manager:liveicon $ submit/noprint/after="+0:10:00"/queue=system_batch_gergo sys$startup:ban $ define/system/exec uis$print_destination lta1: The liveicon.com file consists of these two lines: $ define/sys uis$vt_enable_live_icon true $ define/sys uis$vt_use_fake_icon true (you can also set these by editing sys$startup:uis$setup_vt240.com) which enable a fun feature of VWS - when a terminal window is iconified (after this is set up) it is actually shrunk down and keeps displaying everything, but it uses a 1x1 font. This gives you some idea of what is going on in the terminals since you can notice scrolling, line lengths, and whatnot. It's is very spiffy. Someone should make a thing for DECwindows that does the same thing. My sys$startup:ban.com file is just the specific settings for the banner demo that I use.sys$startup:ban. The definition of uis$print_destination makes the "Print (portion of) screen" menu option print to the specified location. }I must say, being able to have a VT220 display 54 lines is pretty good. Also, }now I have an ethernet connection to my all mighty server and screen refresh }is very fast. Not sure how long I will be able to resist clustering the two. I am using a VAXstation 3100m48 with VWS for the terminal window I'm doing this in right now - but it is SET HOST over to a system with a faster processor (a now measly 175MHz 21064 based DEC 3000m600). Not only can you get 55 lines in the terminal window, but you can also get it to be 168 characters wide (assuming your have a screen with the same resolution as mine, which seems likely). I have symbols defined I can use to set the width to 80 or 132 (called "w80" and "w132", not coincidentally), and the length to the normal 24, a middle size of 32 (which turns out to be a good size for some systems with smaller screens), a nice 40 lines (which is my default), or a longer 50 lines (called "short", "med", "long", and "longer"). Considering how slow the VAXstation 3100m48 is, the responsiveness of VWS on it is quite nice. It was even fairly responsive on a VAXstation 2000. --- Carl