[Info-vax] User Interface Design, Implementation

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Wed Jun 5 23:23:19 EDT 2019


On 2019-06-04 22:59:04 +0000, Arne Vajhj said:

> On 6/4/2019 11:11 AM, Stephen Hoffman wrote:
>> In more recent times, this UI design and implementation discussion can 
>> be a subtopic of a larger app architectural discussion, such as 
>> model-view-controller app designs, or analogous schemes.
>> 
>> https://en.wikipedia.org/wiki/Model–view–controller
>> 
>> OpenVMS doesn't have a concept of MVC, though that's an approach that 
>> can certainly be used within OpenVMS apps.  And MVC has its issues.
> 
> Does VMS have less MVC than any other OS?

Feel free to review what's been included in the previously-cited 
documentation materials around this topic.  You won't find much.

It's fairly rare to see existing OpenVMS apps written in BASIC, C, C++, 
or Fortran using MVC and/or using some other analogous design, though 
some can and do.

> There are probably way less GUI frameworks available on VMS than the 
> more popular platforms.

I'm using some of the approaches from MVC for server app work, not just 
GUI-related work.

The "view" here is the network connection with the clients, as an 
alternative to an OpenVMS-traditional character-cell interface and ANSI 
control sequences or ilk.

There certainly might be some php, Java, Tomcat, Lua, or Python 
frameworks used on OpenVMS—or maybe eventually server-side Swift or 
Rust or other locally-appropriate languages—but those are probably all 
best initially connected to the server and the view using networking 
absent some specific performance requirements, as that allows the 
clients to also be remote via SSL.  If there is a requirement for a 
faster local connection, that's fodder for view-related work in the app 
code of the server.



-- 
Pure Personal Opinion | HoffmanLabs LLC 




More information about the Info-vax mailing list