Lars, the knowledge you share is a treasure we do not deserve!)
I am confused by one thing though...
This type of architecture you presented in the article is very similar to MVVM at some point. Specifically, when you describe how View receives updates and communicates user interactions to the Presenter via "bindings". Those bindings remind me of MVVM characteristic related peculiarity when VM and V communicate through binders without knowing each other. Am I getting this wrong?
I am also wondering, if we'd use Inline templates for presentational component, would it violate the statement that our Presenter has no reference to the View?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Lars, the knowledge you share is a treasure we do not deserve!)
I am confused by one thing though...
This type of architecture you presented in the article is very similar to MVVM at some point. Specifically, when you describe how View receives updates and communicates user interactions to the Presenter via "bindings". Those bindings remind me of MVVM characteristic related peculiarity when VM and V communicate through binders without knowing each other. Am I getting this wrong?
I am also wondering, if we'd use Inline templates for presentational component, would it violate the statement that our Presenter has no reference to the View?