Am I right in thinking it’s almost like a wrapper for all the objects necessary for a View?
For example, say you had an online store that sold music and dvds. On your browse page you’d want to display a list of all your dvds and music. Would you therefore construct a ViewModel object that has two properties containing an albums list and a dvds list?
From my understanding it seems that you have all your model classes ie. an Album/Dvd class, but simply passing these alone wouldn’t be enough for your View. Does a ViewModel basically act as a carrier for all the data your View requires?
Your understanding is mostly correct, but it’s not complete.
The ViewModel may also perform conversions from the type of data that your Model carries to the type of data your View can conveniently work with; this might even mean that the ViewModel does not carry Models directly but other vessels that carry (possibly a subset of) the same information in a more suitable format.
Consider that you could have a Library model that aggregates Albums and DVDs — the difference between such a model and the corresponding ViewModel is precisely that the Model doesn’t care (or even know about) the View while the ViewModel has the express purpose of facilitating it.