Just want to warn you that java and c# was chosen due to the fact that I consider them the strongest from the point of view of the PLO.
Imagine that there is a text box, let it be abstract, as this will not interfere with the drawing of the picture that has the name TextField. In this field you can write and it will send an event change. And here I wanted to do a regular feature called Inputthat will be his "womb" to create an instance of TextField, sign it under an event change and it will retain the entered data in.. where? Let it be a property. And after saving the component will send an event inputChange.
Now the question is whether the property in which is written data from the TextField to the model of mvc, that is, whether this property or let it not be property, and will be the most common object that a property will have text, whether it is business logic of the model of mvc?
The text property is simply a property of the text. It's not business logic, it's just a property (or object).
To MVC it is irrelevant.
neoma answered on July 12th 19 at 17:27
In my opinion, Yes - it can be called a model. Perhaps, even necessary
What is the business logic? No processing rules, nothing - just pass data from the view to the model - there is no BL
delta_Bart answered on July 12th 19 at 17:29
Can. The model is the data repository associated with the View.
But where's the Controller? And what for it in the desktop app? In Belovskom clearly, each Action is a URL, each URL corresponds to a page or other response from the server (View+Model), everything is logical. And in the desktop that will Actionами? Windows? So they are available from the entry point further from each other, not externally as a URL.