Comments on: MVC (Model-View-Controller) introduction simplified

By: CHARLES

CHARLES — Tue, 07 Sep 2010 04:19:37 +0000

CheapTabletsOnline.Com. Canadian Health&Care.Special Internet Prices.No prescription online pharmacy.Best quality drugs. High quality pills. Order pills online…

Buy:Zithromax.Viagra Soft Tabs.Cialis.Soma.Maxaman.Levitra.Cialis Professional.Viagra Professional.Viagra.VPXL.Cialis Soft Tabs.Super Active ED Pack.Viagra Super Force.Propecia.Viagra Super Active+.Cialis Super Active+.Tramadol….

By: NEIL

NEIL — Mon, 06 Sep 2010 09:31:50 +0000

CheapTabletsOnline.Com. Canadian Health&Care.Special Internet Prices.Best quality drugs.No prescription online pharmacy. No prescription pills. Order drugs online…

Buy:Tramadol.Viagra Soft Tabs.Cialis.Propecia.Soma.Viagra.Levitra.Viagra Super Active+.VPXL.Viagra Super Force.Viagra Professional.Zithromax.Cialis Super Active+.Maxaman.Cialis Professional.Cialis Soft Tabs.Super Active ED Pack….

By: Giulian Drimba

Giulian Drimba — Sat, 06 Mar 2010 00:07:03 +0000

Very nice tutorial, thank’s for this!!!

By: Thaylin

Thaylin — Tue, 02 Feb 2010 14:36:36 +0000

Good question Byron.
The View in this example sits around and only contains the graphical elements. We don’t want to couple the View with the Model too tightly which is why it uses the Controller to do all the functionality and changes. The View will just accept input from the user and dispatch an event which is then handled by the Controller to update the Model or View if necessary. The only thing I do here with regards to the Model pairing with the View is passing the Model into it’s constructor so we can let the Controller know that there’s a Model associated with it.
Sometimes there may be reasons for using an observer to take over certain responsibilities of the Controller but based on my schooling and a lot of research I did to create the most concise and logical tutorial I could, this is what seems to be the best methodology. Though, there is never really a wrong way to do things and certain projects would require certain levels of changes to occur.
Remember this is a pattern, which is based on many people running across this type of interaction between objects throughout the years. As such, it does not need to be strictly followed but merely understood that this could come up and this is a good way to handle that interaction. But never complicate things too much if you don’t need to. By adding an observer where you may not need it, you’ve just added another class in which you would have to look when errors occur, complicating your project to the nth degree depending on how much of that you do.
My mantra in programming is “The less typing the better”.

By: byron

byron — Tue, 02 Feb 2010 05:34:22 +0000

According to the figure at the top of the MVC Wiki page, the View is an observer of the Model. Also, according to the figure, the View and the Model have a direct association such that the View can send messages to the Model.

When I look at your code, I don’t see examples of these associations. In addition, it looks like you have the Controller being an observer of the Model, which is an association which doesn’t appear on the figure at the top of the MVC Wiki page.

I am misinterpreting the MVC figure and/or your code?

Thanks.

By: Thaylin

Thaylin — Mon, 01 Feb 2010 16:54:47 +0000

Why thank you Joenbaldwin. Your comment is concise and to the point. I also removed your spam url and title. Just wanted to post this spam comment since it was hilariously generic.

By: Joenbaldwin

Joenbaldwin — Wed, 27 Jan 2010 01:44:32 +0000

The author of thaylin.info has written an excellent article. You have made your point and there is not much to argue about. It is like the following universal truth that you can not argue with: Idle minds are a chance to think for yourself Thanks for the info.

By: Cor van Dooren

Cor van Dooren — Wed, 20 Jan 2010 20:30:50 +0000

Thaylin,

Thanks for the clear explaination!
I would love to see some more complex MVC structure.

Regards

By: Thaylin

Thaylin — Tue, 19 Jan 2010 18:41:21 +0000

The Thaylin approach? I love it!
Any other questions feel free to ask.

By: Barney

Barney — Tue, 19 Jan 2010 18:36:27 +0000

Hi.

Thanks alot for putting this up. I’m new to MVC and was struggling to find a way to get input from textfields (user presses button to validate input) into the controller. I was contemplating putting a reference to the view into the controller somehow, as this seemed the only solution, but no-one else seems to mention that this is ever necessary. Perhaps it’s because it’s often illustrated with things like keyboard events. Anyway, you sound like you know what you’re talking about so I’ve gone with the Thaylin approach!