<aside> đź’ˇ What is UX? The standard definition of "UX" is user experience. But for simplicity, I'll refer to the TRIRIGA UX framework as "UX".
</aside>
<aside> đź’ˇ To download a PDF copy of this TRIRIGAFEEDIA Introducing UX, click the attachment below.
</aside>
TRIRIGAFEEDIA_3.x.x_UX_Framework_01_Introducing_UX_20210425.pdf
CONGRATULATIONS! So you've heard about the new UX application framework. You've thought about it and you're ready to dive in. But what exactly is TRIRIGA UX? How do you get started? First, let's introduce a few key concepts. After all, this isn't the same old TRIRIGA anymore.
First of all, in the words of Mike Herbert, our (former) principal architect on the TRIRIGA applications team, the UX framework "implements an MVC architecture for TRIRIGA applications." This is key. To break this down, UX implements MVC. In turn, MVC is applied to our applications.
But what is MVC? According to Wikipedia:
Model–view–controller (MVC) is a software architectural pattern for implementing user interfaces. It divides a given software application into three interconnected parts, so as to separate internal representations of information from the ways that information is presented to or accepted from the user.
In other words, MVC separates the application into 3 components or layers -- the model, view, and controller. Returning to Wikipedia:
[T]he model captures the behavior of the application in terms of its problem domain, independent of the user interface. The model directly manages the data, logic and rules of the application.
[The] view can be any output representation of information, such as a chart or a diagram; multiple views of the same information are possible, such as a bar chart for management and a tabular view for accountants.
[T]he controller accepts input and converts it to commands for the model or view.
Here's a basic diagram of the typical MVC components and process flows.