MVP on the scheme and in the real project. How to structure?

Question

C++ / C#

Here on paper, I roughly decomposed the application into classes according to the mvc model, everything is as it should be, here are the model classes, here the controller, the provision .... How can I present them in AS? Scatter across different packages (package for model, package for controller, view)? How to deal with access modifiers? Or store all classes in one root?

Answer 1

the letter f was missed in the word ifstream

Answer 2

Despite the established practice in Android to sort classes by type (Presenters in .presenters, Listeners in .listeners, and so on to the point of insanity), in a real project with many classes, this scheme does not work. It is easier for a person to perceive the structure built around the semantics of the application. That is, if the application has a main menu and it has a transition to the Customers, Invoices sections, then you just need to make packages .menu, .customers, .invoices