CQRS and DDD = one Domain model and at least one Query model. Now, it's for your own good to not think of DDD as of something with many rules which broken will make you the DDD public enemy no1.
Let's think a bit: Once a Domain object is updated and a domain event is published, you'll have an event handler which will update the query model. Which query model is exactly the one you need for the UI (the view models).
The client UI should request updates (passing the current model datetime stamp) at an interval. Which updates are also part of the query model. In order to detect what changed, the update should have a datetime stamp which will get compared with the one currently shown. If it's a web app, then I strongly suggest to use a js framework like angularjs.org
Now, The MVC Model in this scenario is the query repository. When insert/edit a row, the Model will be a service (or a command handler) which will update the Domain. Everything related to Domain changes and query model generation is outside the UI, as a part of a Services/Application (call it whatever you wish) layer.