Model - View - View Adapter - Controller (MVVAC)

MVVAC differs from classic MVC only in that views are abstracted away from consumers by way of the view adapter. This view adapter is simply the adapter pattern applied between the view and it's consumers. By using this pattern, JavaScript developers need not target HTML directly in their code. This allows for a separation of roles between user experience design and development. While this separation is supported, it is not required that the roles be fulfilled by different individuals. This also allows for the views to be injected and potentially replaced with mocks or other implementations as needed. View adapters are built from view adapter definitions written in JavaScript by application developers. These definitions are processed and assembled into view adapter instances by the AtomicJS view adapter engine. A set of adapter attachments are injected into the AtomicJS engine that target and connect the view adapters to the technology that the views are built in. By default, AtomicJS provides adapter attachments for supporting HTML 5 based views. Adapter attachments for supporting unit testing are expected to be added at a later date. By isolating the integration of the view adapters with the underlying views to be a function of the AtomicJS library, application developers can focus more on their application logic and less on JS/HTML binding logic.