[Info-vax] User Interface Design, Implementation

[Craig A. Berry]

On 6/6/19 7:54 PM, Arne Vajhøj wrote:
> On 6/6/2019 6:45 PM, Richard Maher wrote:
>> On 5/06/2019 6:59 am, Arne Vajhøj wrote:
>>> 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?
>>>
>>> There are probably way less GUI frameworks available on VMS than
>>> the more popular platforms.
>>>
>>> But if the GUI framework is available on VMS, then it should
>>> support MVC just as well as on any other OS.
>>>
>>> Various Java frameworks (Swing, Struts 1, Struts 2, JSF, Spring MVC).
>>>
>>> Various PHP frameworks (Laravel, CodeIgniter, Symfony, ZF, CakePHP).
>>>
>>> Maybe RoR and Grails would run as well.
>  >
>> I and most others now use mvC or just "C"ontrollers for RESTful APIs. 
>> Any language could support this.
> 
> Without M then I would consider it to be a very trivial application.
> 
> :-)
> 
> But yes - no V - or you can say that V is moved to client tier.

I think the point is that something consuming a REST or GraphQL service
*might* be a GUI client, or it might just be another service or
application.  The "V" can be in any "tier" using 20th-century
terminology, or it can be in any service, micro-service, server-less
lambda function, or whatever, including, but not limited to, GUI clients
based on anything from green screen to Java WebStart to WPF to
Angular/React/Vue.  Somewhat muddying the waters is the fact that
"service" is now used by a number of these client-side frameworks to
refer to a client-side data abstraction layer that runs on the client,
not the server.