On Fri, 18 May 2012 10:03:04 -0600, Jim Janney
<jjanney@shell.xmission.com> wrote:
ram@zedat.fu-berlin.de (Stefan Ram) writes:
In the MVC pattern, I think, M, V, and C should be at least
one non-innner class each?
I often have seen (possibly, especially in beginner code) a
coding pattern, where there is only one single non-inner class:
the model.
Beginner code does tend to be for a small system.
The listeners and the view then are embedded into this
model, possibly, as inner classes. It's not really MVC
as the observer pattern is not used for decoupling.
So, to code a simple Java-GUI application, one just writes
a single class with the model and the controllers as inner
classes and no observer pattern for model-view decoupling.
Is there a name for this simple design?
How about "KISS"?
What about ?the bulk-class pattern?? Or ?the naive GUI pattern??
Big Ball of Mud seems to fit:
http://laputan.org/mud/
If the ball is not big, then it is a case of KISS or maybe YAGNI.
There is little sense in using large system methodology on a
small system. (Do watch though that you do not keep adding to a small
system and switch over to having a large system wihtout realising it.)