WAXLER@XRT.UPENN.EDU (05/12/88)
I would like to use the Macintosh interface as a friendly front end for a set of programs on a Vax (VMS). I need to understand the product(s) and programming effort needed to enable me to do this. Of course there are lots of terminal emulators, which would enable me to type in a command line, and see graphic and tty output. But how can I get the Vax to know about pull down menu selections and dialogue box choices, not to mention "SAVE AS" and "OPEN" directories? Any help would be appreciated. Jerry waxler@xrt.upenn.edu
STAFF.SAS@CHIP.UCHICAGO.EDU (Stuart Schmukler) (05/13/88)
I saw a product that Alisa Systems distributes called MakeEasy that provides a finder like interface to VMS. When Bob Denney demotrated it the program worked smoothly, allowing you to invoke VMS programs, edit VMS files with, etc. It is produced by a company in Italy called LIST - they also have a product called MACnix that makes UNIX look like the finder. SaS PS: I have no stock in Alisa Systems or LIST. And I have not personally used the product (only see it). -------
han@apple.UUCP (05/13/88)
In article <8805121433.AA09310@linc.cis.upenn.edu> WAXLER@XRT.UPENN.EDU writes: >I would like to use the Macintosh interface as a friendly front end >for a set of programs on a Vax (VMS). > > >Of course there are lots of terminal emulators, which would enable me to >type in a command line, and see graphic and tty output. But how can >I get the Vax to know about pull down menu selections and dialogue box >choices, not to mention "SAVE AS" and "OPEN" directories? > MacWorkstation! Ta Da!!! (sorry - my partisanness is showing) MacWorkstation will allow a host to send text sequences which are interpreted by the Macintosh running MacWorkstation and generate Macintosh user interface elements such as menus, dialogs, windows, etc. etc. etc. When the user selects a menu item or clicks in a button, the host is notified using text strings as well. Also can include executable code modules to enhance MacWorkstation, etc etc etc. For more information, contact Apple software licensing. It is available in site license format only I believe. I apologize if this posting is construed as too commercial. This represents only my view and not those of Apple Computer, Inc. -- Byron Han, Communications Tool "OS/2 - Half of an operating system." Apple Computer, Inc. MS 27Y ------------------------------------- ATTnet:408-973-6450 applelink:HAN1 domain:han@apple.COM MacNET:HAN GENIE:BYRONHAN COMPUSERVE:72167,1664 UUCP:{sun,voder,nsc,decwrl}!apple!han
sys_ms@bmc1.uu.se (05/19/88)
In article <9745@apple.Apple.Com>, han@Apple.COM (Byron Han, fire fighter) writes: > In article <8805121433.AA09310@linc.cis.upenn.edu> WAXLER@XRT.UPENN.EDU writes: >>I would like to use the Macintosh interface as a friendly front end >>for a set of programs on a Vax (VMS). >> >>Of course there are lots of terminal emulators, which would enable me to >>type in a command line, and see graphic and tty output. But how can >>I get the Vax to know about pull down menu selections and dialogue box >>choices, not to mention "SAVE AS" and "OPEN" directories? >> > MacWorkstation! Ta Da!!! (sorry - my partisanness is showing) > > MacWorkstation will allow a host to send text sequences which are interpreted > by the Macintosh running MacWorkstation and generate Macintosh user interface > elements such as menus, dialogs, windows, etc. etc. etc. > When the user selects a menu item or clicks in a button, the host is notified > using text strings as well. Also can include executable code modules > to enhance MacWorkstation, etc etc etc. And soon we will have Mac VMS. A vms that send these "text sequences" to the workstation in the other end. Or you could have a $ SET TERM/DEVICE=MACWORKSTATION :- -Mats
Gavin_Eadie@UM.CC.UMICH.EDU (05/23/88)
MacWorkstation is pretty good. I've been working with it for a long time, from when it was 'unsupported software' available from Apple in 1985! Now that it's available as a product I expect it'll be a lot more interesting to many people. It required some commitment to write code for the 'big machine' and I've done this for an IBM 3090-400 mainframe to support e-mail, conferencing and database access for a large campus community. Gavin Eadie, The University of Michigan Computing Center