Juicy Presentation Pattern, yet another presentation pattern, not. JUIPP works on top of ASP.NET WebForms, so I like to think of it as a catalyst, a set of libraries and tools that promote a clean and juicy pattern. Views synchronize themselves to a View Model (VM) and the Views (V) are not supervised by a Controller (V) even though binding is initiated by the Controller. Optionally, Views can catch Behavior and Transition Events, and conditionality synchronize themselves with values of the View Model. Users interact with the Views, and the Views would translate the user inputs to a pair of a Behavior Reference and ViewModel and sends it to the Controller in the form of a Behavior Event object wrapping a behavior reference and a ViewModel. The Container in JUIPP is most times in charge of behavior binding and the Controller sends Behavior Events to the appropriate Behavior (B) in behalf of the Views for data persistence and mapping and the Controller would also accordingly transition one view to the other if the behavior being executed is bound to another view (which makes it a transition behavior).
The concept of Model is behind the scene in JUIPP, as typically only Behaviors are dealing with the actual data (Model). The Model can be a data contract from a web service, or an Entity Model from an ORM (Object Relational Mapping) context. Nevertheless the Model is isolated from the Controller and the Views, by means of the Data Behaviors that can interact with the Model and also translate and map data to ViewModels that the rest of the application can understand and consume as Data Transfer Objects (DTO).