[Info-vax] VMS Desktop system

Shark8 OneWingedShark at gmail.com
Sat Sep 13 21:28:21 EDT 2014


In another thread, there was some discussion of how a "modern browser" 
for VMS is needed which, in turn, prompted discussion of VMS as a 
desktop system.

There are apparently a few windowing-managers for VMS (I've seen X and 
DECWindows mentioned); but as an absolute newcomer to VMS I have no 
experience with either and, from the context, it seems that neither of 
these are adequate.

So then, it follows that the following must be asked:
"WHAT DOES VMS NEED FOR A SUCCESSFUL DESKTOP"
(and, presumably, windowing-system)

   Given the context of the previous thread, it seems this
   can be summarized as "a common, accessible GUI interface"
   and supplemented with "lightweight and accessible from
   other machines [possibly non-VMS] over a network" given
   the propensity of VMS towards more "server-esque" tasks.

Also, there arises the question of how to achieve these; should the 
implementation of such build, in successive layers, say first binding 
OpenGL (in a sensible manner, say using Ada and proper [strong] typed 
enumerations instead of throwing GLEnum around everywhere)? Then a set 
of GUI-primitives [for internal usage]? Then producing a GUI-component 
library? (Perhaps something conceptually similar to Delphi's VCL.)

{In addition to that, would we want to do the window-system proper in a 
language explicitly designed for visual media, like PostScript? If so, 
would that be a good way to tout/flaunt VMS's common-language environment?}

On the "network-accessible" end; how would we handle the [implicit] RPC?
Would it make sense to have the GUI components have [essentially] three 
callbacks for every event: pre-remote, remote, and post-remote? 
(Corresponding to client, remote, and client handling of the [GUI] 
event.) -- While a bit more complex than Delphi [or C#] it would have 
the advantage that *any* application could be remote/distributed w/o 
much [any?] extra work given a little thought/foresight on that 
layout... moreover, it would be ideal for a "minimalistic computation 
device" [e.g. cell-phone] to have as a [native] client and let the VMS 
machine(s) to the "heavy lifting".



More information about the Info-vax mailing list