macdevnet / mvvmc-demo Goto Github PK

In this project，I did not saw any code like 'push' 、'present' and 'dismiss'.
and in real-world, I must push some controller use navigationController.

with my own mind, I think should put this push or dismiss code in 'pageCoordinate',
some thing like this:

In ListCoordinator.swift ：

extension ListCoordinator: ListViewModelCoordinatorDelegate
{
    func listViewModelDidSelectData(_ viewModel: ListViewModel, data: DataItem)
    {
        detailCoordinator = DetailCoordinator(window: window, dataItem: data, nav:self.navigationController)
        detailCoordinator?.delegate = self
        detailCoordinator?.start() // within ,push detail controller
    }
}


extension ListCoordinator: DetailCoordinatorDelegate
{
    func detailCoordinatorDidFinish(detailCoordinator: DetailCoordinator)
    {
        self.detailCoordinator = nil
        self.dismiss ...
    }
}

is it a right way?

Hi,

do you have some starting point for a MacOS app based around the NSWindowController. Not entirely sure whether to pass that one around or how to best refactor this?

Thanks,
Daniel

As far as I understand MVVM, the operations (CRUD) should happen inside the model but the operations triggered from a view into the view -model, should happen inside the view-model only.

In this case, when I hit the login button, the login function which checks the Username and Password should be there in the MVVMCAuthenticateViewModel and not inside MVVMCAuthenticateModel. Could you please take out some time and see what I am referring to? Overall wonderful lecture in the video, it cleared a lot of my doubts.

Question: Who should be responsible for detecting model-changes?

In the sample app you display a list of people and their rank. I guess that list does not change to often, but lets say it did. Who would then be responsible for doing these updates/refetches?

Possibility 1: It's the models responsibility and it should contain a timer function to periodically do the refetch. But then I guess the model would need a way to notify the viewModel about the update?

Possibility 2: It's the viewModels responsibility. If would have a timer function and periodically call the model.items function to update/refetch.

(Of course you could do it easy and put a "refresh" button in the view that the user has to click to get the latest data, but I would like it to be more "event driven")