HP3000-L Archives

March 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Patrick Thrapp <[log in to unmask]>
Reply To:
Patrick Thrapp <[log in to unmask]>
Date:
Tue, 23 Mar 1999 14:16:16 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Tracy Johnson wrote in message ...
>On Tue, 23 Mar 1999, Nick Demos wrote:
>
>> > >>> Bonnie Roman <[log in to unmask]> 03/23/99
>> > 06:18am >>>
>> > Hi Guys,
>>
>> But these terminals do not supprt HP's block mode, required for
>> VPlus applications.
>>
>> Nick D.
>
>It all depends if VPlus applications are what you WANT.  For example,
>Powerhouse Quick screens had excellent screen drivers for VT terminals on
>the HP3000.  All you had to do was tell Powerhouse you were using a VT100
>at run time.  They had drivers for several dozen other brands as well.
>
>Tracy Johnson
>"Trust No One" - Semper Gumby
>

Wingspan, from a group on Vashion Island in Washington state, could do VIEW
emulation to VT terms.  Required building XLs from your VIEW files.  VIEW to
C to XL.  Then running the app using the VIEW file with an XL= parm with the
Wingspan XLs in proper order.  They trap the VIEW calls.  Didn't require any
changes to HP code, UNLESS you have a menuing system to create/activate your
app programs.  Then, depending on whether you had to change VIEW files,
changes might be required.  It worked pretty well.  Downside was that
changes to VIEW files required the extra effort/(memory) to also build &
replace the module in the XL.  If I remember correctly you could add drop
downs.  It was basically like an ASCII windowing system.

ATOM RSS1 RSS2