Model-View-ViewModel (MVVM from now on) was created by Microsoft and is defined as follows:
The Model-View-ViewModel (MVVM) pattern is an application pattern that isolates the user interface from the underlying business logic. MVVM belongs to a class of patterns called Separated Presentation. These patterns provide a clean separation between the UI and the rest of the application. This improves the testability of the application and allows the application and its UI to evolve more easily and independently.
The Model-View-ViewModel (MVVM) pattern helps you to cleanly separate the business and presentation logic of your application from its user interface (UI). Maintaining a clean separation between application logic and UI helps to address numerous development and design issues and can make your application much easier to test, maintain, and evolve. It can also greatly improve code re-use opportunities and allows developers and UI designers to more easily collaborate when developing their respective parts of the application.
It basically adds a new «separation layer» to break down the MVC pattern into more manageable pieces.
MVC on Cocoa hast always been a pain because it always translates to «Massive View Controller» due to the need to many delegates that are usually implemented by one controller (e.g. when binding a tableview where you need a delegate for the tableview and also a delegate for the data source, etc).
MVVM separates the View from the Model via an «intermediate» class named ViewModel.
This intermediate class allows the binding of the View and the Model in a more clean and easy manner and also separates some logic as to how/when to load the data removing that responsability from the View and leaving pretty much only the UI specific code in it.
RxViewModel is the marriage between MVVM and Rx extensions
Long story short: a blatant «imitation» of ReactiveViewModel using RxCocoa.
Since ReactiveViewModel project felt on stagnation and there's not Swift or Swift 2.0 implementation we found the need to implement something like this on Swift.
Given the fact that there's no Swift branch and the lack of interest in the project we felt it was better to give RxSwift/RxCocoa a chance and instead use it as the base for this reactive view model approach.
To run the example project, clone the repo, and run pod install from the Example directory first.
Simply add the following line to your Podfile:
pod "RxViewModel"And then run:
pod installJust add the following to your Cartfile
github "RxSwiftCommunity/RxViewModel"And run:
carthage updateCurrently RxViewModel supports the following features from ReactiveViewModel (*ALL of them 😉):
-
didBecomeActive -
didBecomeInactive -
forwardSignalWhileActive -
throttleSignalWhileInactive
Esteban Torres
RxViewModel is available under the MIT license. See the LICENSE file for more info.