On Mar 16, 2012 8:55 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > Hi, > > If we make no changes it probably means that down the track we're likely to end up with this: > > <s:Application width="100%" > xmlns:fx="http://ns.adobe.com/mxml/2009"; > xmlns:s="library://ns.adobe.com/flex/spark" > xmlns:mx="library://ns.adobe.com/flex/mx" > xmlns:a="http://flex.apache.org/ns"; > xmlns:as="http://flex.apache.org/sparkns"; > xmlns:amx="http://flex.apache.org/mxns"; > xmlns:nc="http://flex.apache.org/ncns";> > > Which I'd like to avoid somehow. > > Thanks, > Justin > > PS "nc" is new component model that someone's come up.
This is exactly why namespaces should be well planned and rarely added. Also you'd only get that many namespaces if you used a variety of different component sets in a single mxml document. More than likely you'd have far fewer actually in use at once.
