Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Mixed Case class names and SW, SWC etc
From: Tink <flex@tink.ws>
In-Reply-To: 
 <149F8129B58B2D418508E63117D9C5419B3A61983C@nambx05.corp.adobe.com>
Date: Sun, 19 Aug 2012 11:45:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7AF644A4-A08C-4126-B7FA-A3624A4C7981@tink.ws>
References: 
 <149F8129B58B2D418508E63117D9C5419B3A61983C@nambx05.corp.adobe.com>
To: flex-dev@incubator.apache.org

I wasn't really suggesting changing them, as they would break a whole =
load of peoples code, just  pointing out that this is a mistake that =
leaves well named classes unreadable.

It also doesn't help with interfaces and Adobe convention of using a =
capital I's. If acronyms weren't all uppercase, an interface would be =
clear to see as it would be a capital I, followed by another capital =
letter. If the second letter wasn't capitalised, you'd know it was an =
interface.

For instance

ID3Info, interface or class? Id3Info would have made it clear that it =
was a class.


Tink


On 18 Aug 2012, at 01:53, Gordon Smith wrote:

> On second thought, changing them would be a bad idea because this =
convention comes from the flash.* API. In other words, it wasn't an =
arbitrary choice for Flex. As long as Flex is Flash-based, acronyms =
should not be mixed case, so that the API looks consistent at all levels =
of the platform stack.
>=20
> - Gordon