Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gosmith@adobe.com designates
 64.18.1.181 as permitted sender)
From: Gordon Smith <gosmith@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Tue, 31 Jul 2012 09:00:00 -0700
Subject: RE: What namespace should new components go in?
Thread-Topic: What namespace should new components go in?
Thread-Index: Ac1uwTcABveO17VpRNuV8A4iyTnkeAAc5P9Q
Message-ID: 
 <149F8129B58B2D418508E63117D9C5419B3A441664@nambx05.corp.adobe.com>
References: <B924CD80-E14F-4975-A71C-979906CB3017@classsoftware.com>
In-Reply-To: <B924CD80-E14F-4975-A71C-979906CB3017@classsoftware.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Regarding the existing namespaces -- and I'm referring to the namespace URI=
s, not the namespace prefixes -- isn't it time to get "adobe" out of  them =
and "apache" into them, now that the parity release is complete?

For example,=20

http://ns.adobe.com/mxml/2009 -> http://ns.apache.com/mxml/2012
library://ns.adobe.com/flex/spark -> library://ns.apache.com/flex/spark
library://ns.adobe.com/flex/mx -> library://ns.apache.com/flex/mx

- Gordon

-----Original Message-----
From: Justin Mclean [mailto:justinmclean@gmail.com] On Behalf Of Justin Mcl=
ean
Sent: Monday, July 30, 2012 7:07 PM
To: flex-dev@incubator.apache.org
Subject: What namespace should new components go in?

Hi,

Reposting (and expanding) as suggested under a new topic to make it clear t=
his discussion is about namespaces. This has been discussed on the list bef=
ore but no clear consensus was reached.

In the patches branch I've created a new apache target in the build script =
to compile an an apache.swc to place new components in. It uses a new names=
pace - http://flex.apache.org/ns. This has been in the patches branch for s=
everal months. The PostCode validator and format classes currently use this=
 namespace and I would like to move them into trunk, followed closely by Mi=
ke's collection classes.

What are people preferred option with new components and namespaces?

1. Use existing mx and spark namespaces
Advantages: No new namespaces required.
Disadvantages: New components mixed in with old and compiled into existing =
swcs making them larger etc, hard know what's new over 4.6 SDK. Not always =
obvious which namespace mx or spark a new component should go into.

2. Place components under a single new namespace called http://flex.apache.=
org/ns.
Advantages: All new components have a new ant target, new swc and namespace=
 so easy to see what is new in the SDK and if a project is using Apache Fle=
x. Work already done in patches branch. Namespace is valid URL and was sugg=
ested by a mentor.
Disadvantages: It's a new namespace.

Example of how a user of the SDK would see it/use it:
http://svn.apache.org/viewvc/incubator/flex/whiteboard/jmclean/validators/s=
rc/PostCodeValidationExample.mxml?view=3Dmarkup

(also see patches branch)

3. Place components under a single new namespace other than one suggested i=
n 2.
See 3 for advantages and disadvantages.

4. Place components under multiple new namespaces
Advantage: No need to decide if it's a mx or spark component.
Disadvantages: Lots of new namespaces. More work on build scripts.

5. Don't care.
In which case I'll just check in what I've done in the patches branch.

Thanks,
Justin