Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.albasani.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Gene Wirchenko <genew@ocis.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: How is this "pattern" called?
Date: Fri, 18 May 2012 10:50:42 -0700
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <lp2dr7da6p0jslnua32ldd4uki1036ibfs@4ax.com>
References: <pattern-20120518104439@ram.dialup.fu-berlin.de> <ydnlikpbhon.fsf@shell.xmission.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info: mx04.eternal-september.org; posting-host="wKah3EH8kutwAOV6+9FiEQ"; logging-data="10045"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18WlDSOT/JCknuUN12zZYpU5R3I3iTofdU="
X-Newsreader: Forte Agent 4.2/32.1118
Cancel-Lock: sha1:dvU+Aru8iM8Ypi3F3GZ1vRJhssQ=
Xref: csiph.com comp.lang.java.programmer:14626

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.)

Sincerely,

Gene Wirchenko