The WVM (Windows-View-Model) pattern is an MVC achitectural pattern built using a basis of a window approach. It follows a series of predefined structures that makes up the WVM itself. This system can be entirely classified into six categories which are Routes, Frames, Models, APIs, Sessions and Rex files, where the Rex files are template files controlled mostly with template directives and compiled using compiler functions. All window associative files are stored and processed from their relative directory within the root windows directory that is mainly reserved for storing window associative files. The WVM system depends on a structure where a Model is created before a View is rendered. In order to work with WVM framework, a Window file must be created. Window files are the main classes that are extended to the root Window controller class which determines how the entire application is processed. Hence, Window files inherit the properties of their root parent Window which has extensive route management and template loading features. The window system resolves routes mostly by the use of predefined routing logic. These routing logics are responsible for determining how routes are validated and resolved.
Why use WVM approach?

The WVM approach can be best employed for managing web routes or an entire web application for the following reasons:

  • WVM approach makes it easier to constantly manage and maintain web applications.
  • The design architecure makes it easy to secure project applications.
  • It provides a system of handling more robust application with lesser files.
  • The development structure is designed to help in file organization making it easier to locate files.
  • The window system has a great relationship with template rendering.
  • Cross device compability provides a great assistance in file migration.
  • Cross environment compatibility is balanced between offline and online environments.
  • Interaction between existing and non-existing urls is made easier.
  • This system also makes it easier to create and manage web APIs.
  • Integration of extensible architecture is made possible.
  • Internally integrated tools assists in smooth migration of files.
  • This system helps to develop a production ready application.
Demerits of WVM approach?

The WVM approach can be best employed for managing web routes or an entire web application for the following reasons:

  • This system requires a great understanding of the relationships between url addresses and route management structures in order to avoid technical issues.
  • Managing routes may prove a bit technical and advanced depending on developers understanding of the concept.
Window properties

A window file is any file that extends to the root Window class. The following are the properties of a Window file.
  • A window file must exist within the windows/ directory or window/ subdirectory.
  • A window file (class) name should be initialized with an upper case.
  • A window file (class) must be extended to the root Window class
  • A window file (class) must have a public __construct() method which serves as entry point.
  • A window file (class) specifically routes, must have a closing structure.

Window subclasses

Windows subclasses that extends to the root Window class are the Routes and Frames. Routes which is used for handling routes and also, we have Frames which serve as binding or parent structure for Routes. The Route files are usually placed within the Routes subdirectory of the windows directory while similarly, Frame files are expected to be within the Frames subdirectory of the windows directory.

Managing windows

The management of windows depends on the understanding of window logics which are the basic root technicalities behind how route are managed or resolved. More information on route logics are provided here.