Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Must we use MVC ?

 
Zhou Can
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have finished my assignment for near a month . Recentlly , I read many tips about MVC , but I have not considered it in my design . I hold all view , controller , model of client in one class . Now ,I found it a very big project to use the MVC design pattern to seperating the one client class . So , I want to know if it is OK to avoid the MVC in client class . Of course , this pattern is used in the JTable .
If we must use MVC , which way in the following is better ?
1: One Controller to control all view .
2: Each View with a controller .
 
Mike Skinner
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi
I uploaded my assignment two weeks ago and I didn't use MVC in the design. For the JTable yes but no other place!
Had a GUI class taking care of the UI and a client class holding both the controller and model.
I would be very suppriset if I would fail the assignment because I didn't use MVC. If it was a must I think it should say so in the requirements!!
Feels a bit weird to change my desing that is working just to fit it in to the MVC pattern!
In a way I already used MVC for the JTable...
Hopefully I will get my result this week or the next so then we'll see how important it really is....
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic