From: claird@... (Cameron Laird)
Date: 2001-03-17T23:40:02+09:00
Subject: [ruby-talk:12771] Re: Understanding Design Patterns Was: GUI Toolkit for Ruby

In article <35139.198.200.139.3.984159859.squirrel@webmail.primary.net>,
Guerry A. Semones <gsemones@primary.net> wrote:
			.
			.
			.
>Most simply put, the GUI should not do much more than delegate calls
>to non-GUI classes that do the real work.  The GUI code should deal
>with GUI issues, the business logic should deal with business logic.  
>
>We are currently doing a project where we've done just this.  All
>business logic and validation are done separate from the GUI, and the
>GUI just delegates back.  Most of the core business also delegates
>back to a mid-tier.  The core point, however, is that we will be
>taking the business and validation logic and put it, unchanged, into
>an MVC designed web architecture: same code, same tests, different
>interfaces.
			.
			.
			.
For an expression of the same sentiment from the
standpoint of quality assurance of application
development, see
<URL: http://www.sunworld.com/unixinsideronline/swol-03-2001/swol-0316-testing.html >
-- 

Cameron Laird <claird@NeoSoft.com>
Business:  http://www.Phaseit.net
Personal:  http://starbase.neosoft.com/~claird/home.html