so the next one more you control and others this is big
why are you just it give you bet
that so complicated yeah i thought let's drive for
really into the hot stuff right away so we don't have much
time so no actually you will need it and you will need it for
the problem you will have to solve the task
of this course you wanted to solve yes yes or no user interfaces
through them and so the problem is we need to
separate somehow the concerns data and logic on one hand
use into action people click on buttons all the time
like and then the presentation in two main
to see something yeah there's no to react
to and we need to separate all these things that
all program keeps maintainable and that is flexible at some
points and also confirm rules so that we can kind of
to the same things the very way in and change that
yeah so it's already codes model you controller
and we get three different things we want to decompose have
had already than that these three parts model of human controller
might take certain yeah functionality and and
or or one of those so the the first stores the data and provides
the logic also sometimes called business logic tolls the actual
things which are happening the viewers who yeah
it's a view so it's the same your see if and it is therefore
to prevent or or whatever the yeah they they formation the
data from the model to the user and then there's a controller
which handles all the interaction and of course of you was
receives interactions of if you click on a button the buttons
part of if you of course and we already see that in the
other hand and the most important thing here is that we need
to decouple all these things so they shouldn't be kind of completely
into my one class so so the user into x with a
view we already said that the due process given to the controller
the controller updates the model and before all that happens
if you which is that as an observer and here we got like the
first south and then we will discuss in the second
and i don't automatically like works right
yeah and now we're going to understand how the magic internally
first so almost almost directly because of one thing that not
just at least want to mention is and we see your
it comes in like a lot of variance and if you start fooling
and we see more you control if you start fooling for diagrams
for coal i mean it's mass yeah you will have like
thousand pages and two thousand descriptions all that
everybody tells us like the complete contrary
to the to the to the wonderful but they all agreed
that it's about separating the concerns is autistic or like
the common cold and it's not everything is different so it's
most likely that ninety percent is the same and then the actual
realisation might differ from library to library
because it might be used in different contexts
and so you basically often you also do not implement the model
you can call itself but you use some sort of framework
yeah actually does that for you and as it is a pattern you
already understand than they didn't model the
controller and all they did this here and
so if you notice the someone is using a model you controller
you already know that all the data is residing and insights
model that the view is going to yeah going to do the presentation
to the user and says something in between whatever it is called
of might you if you have you want so whatever
that method my different but the general idea
is always the same soul let's dive into the details
of so we have three patterns which all part of
this model we can but which model you can
control as composed of we have to observe a pattern
which kind of registered to view as an observable for a model
and then the model notifies single
service we will cover that in the second
we have to strategy pattern which can have helps us
what the strategy for the control how it will solve problems
and then when the composite pattern which have system good
if you from sort of ok component