View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007

Sum02 Final Exam Review: MVC vs. Morphic

Edit Sum02 Final Exam Review: MVC vs. Morphic here.

a. Name an application where MVC is preferable to Morphic.

MVC is good when what is desired is a one-to-many model/view software. for example, one set of data is to be presented in various forms, like a chart, bar graph, or pie graph. MVC is also a natural divison of the pieces that go into a gui. alan fay
Here we are talking about an MVC project versus a Morphic project. There are other advantages to MVC. Can anyone else name one? Barbara Ericson
MVC interfaces are usually very simple to operate. (Remember the clock we made?) Pluggable buttons can be used to implement simple "push for this action" type interfaces. Morphic is fancier and more flexible, but it's a little less obvious to the user than the simple layout of an MVC application. Plus, MVC is faster than morphic. - Jim McPherson
or . . . embedded devices where all the "features" of Morphic are not only superflous, but take up valuable resources. Batman


b. Name an application where Morphic is preferable to MVC.

morphic is a good approach when rapid prototyping of a gui is desired, with its premade widgets and the support for building a gui from drag-and-drop components. alan fay

c. Identify three major design differences between Morphic and MVC.

in morphic, the view and the controller are merged into one object. one programs the event-handling and the view layout in one class. moprhic involves less message passing than MVC. additionally, the MVC architecture requires more work in programming the actual view; in morphic, many components are pre-made and can just be altered to suit needs. alan fay
There are some more. Anybody else? Barbara Ericson
Morphic is slower. MVC follows classic "observer" pattern to a T, where as Morphic merges the model and view, and embeds the controller in the world. MVC allows for multiple views on same model, whereas Morphic has a "what you see is what you get" policy. I think all that's right....can anyone verify that? - Jim McPherson


d. Can you use the MVC Paradigm in Morphic? Why or why not?

i did. :) i delegated the event-handling to a separate object, so that there wasn't a whole lot of copying code around. essentially, each morph just acted as a view. you can do pretty much anything in smalltalk, provided you write enough classes. alan fay

e. Name at least one commercial UI package today that is based on the MVC paradigm.

java's swing. alan fay

Link to this Page