An MVC concern
-
I noticed in one of my professor's MVC Java programming projects he put a Controller class inside a model package. Is it true that in MVC often people use just MV and don't bother with the C because they don't think it's worth creating another layer just for a couple of extra classes? It seemed illogical to me to put a controller inside a model package.
-
I noticed in one of my professor's MVC Java programming projects he put a Controller class inside a model package. Is it true that in MVC often people use just MV and don't bother with the C because they don't think it's worth creating another layer just for a couple of extra classes? It seemed illogical to me to put a controller inside a model package.
-
I noticed in one of my professor's MVC Java programming projects he put a Controller class inside a model package. Is it true that in MVC often people use just MV and don't bother with the C because they don't think it's worth creating another layer just for a couple of extra classes? It seemed illogical to me to put a controller inside a model package.
You can split Control and View by doing that. It has several advantages: one of the biggest to me is, that I can change the view without touching the behavior of the UI. I can also use one Controller for several Views, which gives me more control about what's happening. But I also use just MV, addressing anonymous event listeners in the view's code. Mostly on dialogs or when "quick&dirty" is required.
regards Torsten I never finish anyth...