Forums Register Login

MVC implementation

+Pie Number of slices to send: Send
Hi Friends,
I just wanted to know if what I knew about it MVC implementation is right.
From what I have understood, we design classes that manange the GUI(the view) , define listener classes for all the gui components (the controller, which, effectively intercept the events help us do the task required of that gui component) and finally we have classes that encapsulate the domain data and behaviour.
All I can understand from this is the clean logical separation of responsibilities.
Is this all there is to implementing the MVC? or is there more to it than meets (my) eyes?

Appreciate your responses.
Vrinda
+Pie Number of slices to send: Send
Hello Vrinda,
You idea is pretty much right.
In code that I maintain and develop.. a lot of times the view and controller are combined into one class and then the model (an encapsulation of all your data) is in another class.
Hopes this helps!
Mark
+Pie Number of slices to send: Send
The way of splitting them up I tend to use is to say "What if I want to distribute this application in 2 formats?".
How much of my code is common, and contains the core functionality? That's the model.
How much of it changes if I change distribution from a website to WAP? That's the view.
The controller sits in the middle.
Eliminate 95% of the weeds in your lawn by mowing 3 inches or higher. Then plant tiny ads:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 511 times.
Similar Threads
Bilateral Interaction Between JComponents
Relationship between Model (in MVC) and DAO
server gui ? and safe shutdown
GUI Frustration - help NEEDED!
Client Gui!
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 09:28:12.