Model-View-Presenter - help

Question

Hi,
I recently read about Model-View-Presenter on Martin Fowler's website, and elsewhere. I think I understand the idea...
The view just displays the GUI components..events fired from the View are delegated to a Presenter. The presenter then deals with the model and updates the View accordingly. Sound about right?
Ok, so I learn best by example..and I haven't found any code samples yet, so I thought I'd give it a shot. Below is my code...
Model
* the model to be displayed in a View
public class Album {
     private boolean isClassical;
     private String composer;
     public String getComposer() {
          return composer;
     public void setComposer(String composer) {
          this.composer = composer;
     public boolean isClassical() {
          return isClassical;
     public void setClassical(boolean isClassical) {
          this.isClassical = isClassical;
View - interface
import java.awt.event.ActionListener;
* An interface which defines the methods needed by a presenter
public interface View {
     public boolean isClassical();
     public void setClassical(boolean b);
     public boolean isComposerEnabled();
     public void setComposerEnabled(boolean b);
     public void addClassicalChangeListener(ActionListener al);
     public void showView();
View - implementation
import java.awt.Dimension;
import java.awt.event.ActionListener;
import javax.swing.JCheckBox;
import javax.swing.JFrame;
import javax.swing.JPanel;
import javax.swing.JTextField;
* A an implementation of the View interface.  It shows a checkbox
* and a textfield.
public class MyView extends JFrame implements View {
     private JCheckBox checkboxClassical;
     private JTextField textfieldComposer;
     private MyPresenter mp;
     public MyView() {
          checkboxClassical = new JCheckBox("Classical");
          textfieldComposer = new JTextField();
          textfieldComposer.setPreferredSize(new Dimension(100, 20));
          textfieldComposer.setEnabled(false);
          JPanel p = new JPanel();
          p.add(checkboxClassical);
          p.add(textfieldComposer);
          add(p);
          setSize(600, 400);
     public void addClassicalChangeListener(ActionListener al) {
          checkboxClassical.addActionListener(al);
     public void setPresenter(MyPresenter mp) {
          this.mp = mp;
     public void setClassical(boolean b) {
          checkboxClassical.setSelected(b);
     public boolean isClassical() {
          return checkboxClassical.isSelected();
     public void setComposerEnabled(boolean b) {
          textfieldComposer.setEnabled(b);
     public boolean isComposerEnabled() {
          return textfieldComposer.isEnabled();
     public void showView() {
          setVisible(true);
Presenter
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
* A presenter for a View.  When the "classical" fires
* an ActionEvent, the "composer" component is enabled or disabled.
public class MyPresenter {
     private Album album;
     private View view;
     public MyPresenter(Album album, View viewVal) {
          this.album = album;
          this.view = viewVal;
          view.addClassicalChangeListener(new ActionListener() {
               public void actionPerformed(ActionEvent e) {
                    view.setClassical(view.isClassical());
                    view.setComposerEnabled(view.isClassical());
          view.showView();
}and here is a simple Main to tie it togehter.
* Ties together the M-V-P
public class Main {
     public static void main(String[] args) {
          Album al = new Album();
          al.setClassical(false);
          MyView myView = new MyView();
          MyPresenter mp = new MyPresenter(al, myView);
          myView.setPresenter(mp);
}Ok, the idea is this. The GUI shows a checkbox and a textfield. basically, if the checkbox is selected the textfield is enabled and can be typed into. If the checkbox is not selected, the textfield is disabled. From the model point of view, if isClassical is false, then no composer can be defined.
So, is my code following the pattern? Does anyone have any simple code to contribute as an example? For some reason is just seems weird to me that I would have an interface define a bunch of methods that the Presenter can call. And I have to create the Model and View which get passed to the presenter, and then I have to set the presenter on the view....it just seems weird to me.
Any comments, suggestions, examples??
Thanks for your time and contributions.

Answer 1

The other information didnt answer my questions. The response was mixing the idea of MVC instead of MVP, and then the response discussed what they thought was wrong with MVP and why they use a different model. I am looking for help on understanding the pattern more, also for someoen (who knows about MVP) to look at my sample code and help me understand what I did right/wrong.
Thanks.