Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 david@davidarno.org does not designate 209.85.212.175 as permitted sender)
From: "David Arno" <david@davidarno.org>
To: <flex-dev@incubator.apache.org>,
	<jeffry@dot-com-it.com>
References: <060d01ccd3bd$1414aa00$3c3dfe00$@davidarno.org>
 <4F132EEF.8090109@dot-com-it.com>
In-Reply-To: <4F132EEF.8090109@dot-com-it.com>
Subject: RE: Overly large classes (was Flex incubation on Apache as
 Opensource)
Date: Sun, 15 Jan 2012 21:01:18 -0000
Message-ID: <063d01ccd3c8$d4b31d90$7e1958b0$@davidarno.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQDBRm3Dd44VbUGGEZiI/QsPSBkUKQJQsPzxmBJ5pWA=
Content-Language: en-gb

> From: Jeffry Houser [mailto:jeffry@dot-com-it.com] 
> Sent: 15 January 2012 19:54
>  I'm curious as to what your suggestions would be simplifying something
like this? 
>  [Or ignoring my commercial component, the Flex List class]
I'd prefer not to comment on your commercial creations Jeffry, but I'll
comment on List.

The class does many things: it's a container; it displays the contents of a
data provider; it supports scrolling; it supports item renderers; it
supports dragging & dropping; it supports single selections; it supports
multiple selections; it supports item editing etc. Classes should be single
purpose. Therefore the List class should be a compositional class that is
composed of IDataProviderSupport, IScrollSupport, IDragAndDropSupport etc
and the functionality that is currently in List should be in classes that
implement those interfaces. That way, the currently overly-large,
over-complex, unfocused class could be broken up into a large number of
properly focused, smaller classes.

David.