incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Duane Nickull <>
Subject Re: Flex and names spaces in MXML
Date Sat, 17 Mar 2012 01:48:05 GMT

On 12-03-16 7:55 PM, "Justin Mclean" <> wrote:

>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=""
>	xmlns:s="library://"
>	xmlns:mx="library://"
>	xmlns:a=""
>	xmlns:as=""
>	xmlns:amx=""
>	xmlns:nc="">
This is assuming that someone would use both Adobe and Apache spark
components (same for halo) and also use custom components.  I can see that
if this group does it's job correctly, this would only be a temporary
situation at least.  IN any event, this would be required to tell the
compiler which s:button to actually use.  It's 4 extra lines of code.  Why
is this a bad situation?

What is "a" for?  An Apache version of FX?  Sorry to be naïve.

In any case, what do you see as an alternative?  I cannot see any other
than combining the a, as and amx into one.


President/COO ­ Überity Technology Corporation
Adobe LiveCycle ES & Enterprise Specialist
Blog |
Twitter | @Uberity @duanechaos

View raw message