🚀 go-pugleaf

ICS wrote:

> Anyone feel that they have a real philosophical understanding of the
> model-view-controller architecture and have grounded this into
> practicality... if you have an example that you wouldn't mind sharing with
> me -- I'd love to see it.

A good starting point would be the JBuilder Developer's
Guide.  Chapter 33 is pretty lucid (at least I think so).

Also, some background reading, provided to you by Javasoft.
(Swing is MVC-based.)

  http://java.sun.com/products/jfc/tsc/swingdoc-static/swing-arch.html

Once you read this, go on to read about the Swing JTree:

  http://www.javasoft.com/products/jfc/tsc/swingdoc-current/trees-tables.html

  http://www.javasoft.com/products/jfc/tsc/swingdoc-current/tree_model.html


Finally, study the source code for an MVC-based component like the 
ListControl. Chapter 34 dissects the ListControl. 

And once you have that down, start thinking about how you would
organize your application around MVC.  That is, completely segregating
views (frames, dialog boxes) from models (data structures and get/set
methods associated with them), with a controller to mediate behavior
demanded by events which come from menu items and from user interaction
with view components (buttons, comboboxes, lists, trees, tables, etc.).
Set three rules for your design: 1) no view shall know the name of a piece
of data; 2) no data structure shall know the name of a view; and 3) no
major view (frame/dialog) shall know the name of another major view.
[Hint: the controller knows everybody.]


Paul Furbacher