Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.238 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Fri, 22 Mar 2013 17:29:54 -0700
Subject: Re: git commit: FLEX-33130 Added label setter/getter to interface
Thread-Topic: git commit: FLEX-33130 Added label setter/getter to interface
Thread-Index: Ac4nW7Pr9BpWbJwESr+1nDjoUUajwAAAdYGC
Message-ID: <CD724592.4FDD7%aharui@adobe.com>
In-Reply-To: <E198D35D-42D9-49F3-8705-A966338EEED6@classsoftware.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.16.0.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 3/22/13 5:16 PM, "Justin Mclean" <justin@classsoftware.com> wrote:

> Hi,
>=20
>> I'm not vetoing, but I don't like it.  A button that is just graphical
>> (play/pause/rewind in a video control) now must have a label?
>=20
> Fair point. I was just looking for low hanging fruit to pick.  However
> Button.as (both of them) and the button skins do assume all buttons have
> labels even if they are not displayed.
True, but in theory some Flash-based button could implement just enough to
play in this game.
>=20
> Perhaps the button class needs to be broken up?
In the new FlexJS framework, it is.  But I wouldn't rush to do it for
current Flex.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui