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)
Message-Id: <E4599C3A-5C8E-4AD3-BF45-76ADF6409F45@tink.ws>
From: Tink <flex@tink.ws >
To: flex-dev@incubator.apache.org
In-Reply-To: <3C66C415-073F-47FE-A323-DD0EDDBEF89F@classsoftware.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: MobileAlert - quetwo
Date: Fri, 16 Mar 2012 09:14:48 +0000
References: <A108139E-DF71-429E-BC14-AC0DCD817272@classsoftware.com>
 <CAEWfVJk_CQ-FQ4+BQCPPuaBmkKL28a8nhsRKX6gJEF7tXyAJgQ@mail.gmail.com>
 <CA124A9E-2B67-46EF-AC25-288DFC344D8F@classsoftware.com>
 <4F608EBF.5060007@dot-com-it.com>
 <CAEFz_vvkZHk33c=sqtz7c+1ExbKuzMhjMBTwQsnmHLAHNN5ymg@mail.gmail.com>
 <3C66C415-073F-47FE-A323-DD0EDDBEF89F@classsoftware.com>

I immediately noticed when looking at this is that it extends  
SkinnablePopUpContainer.

In my mind an Alert isn't a container. You do not create one and then  
put contents in it, and therefore you get unnecessary overhead with  
the container, and from outside the API will look like you can add  
elements to it.

I would suggest we add a SkinnablePopUpComponent, then and Alert can  
be added on top of that. Then do we need a MobileAlert and Alert, or  
can we not just have a different skin for the 2 versions?

Tink


On 16 Mar 2012, at 04:02, Justin Mclean wrote:

> Hi,
>
> So far I think we mostly agree that having real URLs is nice but  
> have no idea what those URL should be.
>
> Are spilt if we should have a small or large number of new namespaces.
>
> The one I've currently committed is http://www.apache.org/flex (look  
> in flex-config.template.xml and/or flex-config.xml) so until we come  
> up with something better that what it will be.
>
> Thanks,
> Justin
>