Model-View-Controller pattern in WTL-based apps

Question

1.00/5 (1 vote)

See more:

I've read about Model-View-Controller pattern, and I plan to use it for my WTL-based project. For example, I would like to write a calculator application.

First of all, I write CCalculator class that performs actual calculations. This is the model in terms of MVC.

Then I create a dialog and write CCalculatorDlg class (derived from WTL's CDialogImpl<> template class) to handle dialog events. What is this in terms of MVC? View or view-controller? If this is just a view, than should I write another class, say CCalculatorController, as an intermediary between CCalculatorDlg and CCalculator? How to apply MVC pattern to WTL correctly?

Posted 14-Jul-11 2:08am

OlegKrivtsov

Updated 15-Jul-11 17:47pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-07-14T07:49:00

The answer to the questions "The question is how to apply MVC pattern correctly? What is the view and what is controller?" is a part of MVC. Keep reading. It need some experience in analysis and architecture.

The Model is the calculation model represented in data: operands and result of calculation. I think it should not contain any strings representing numeric data, should be numeric-only. In a more or less advanced calculator if should be something like expression tree.

The View should be the window with controls.

The events of the window should be implemented in Controller. The idea is: the events should not be translated in the UI-related processing. All events should be consumed by Controller to update the state of the model. Then the whole updated model is used by Controller to map it on the states of the View.

Now, what is the functionality of the calculator? I would say in this is a calculator with buttons (1, 2, 3, +, -, etc.) it would be a waste of time. Who needs it? Just to mimic standard historical calculator. The real thing should work with text input.

I would understand that you need it just for exercise. Otherwise, making a Windows application for a calculator would be a waste of time. Why? Because a practical calculator is something like mine:

http://www.sakryukov.org/freeware/calculator/[^].

—SA