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: domain of danreicher@gmail.com
 designates 209.85.214.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAd0WraNCGfEoLrN2fq1-qpfMGWuauGoimWjTozcowGbJbC9UA@mail.gmail.com>
References: 
 <CAE0mPOtNPZG+Mu-DBgWcz7OovzE8OL52mk3qOeb2dJhyZR3nFg@mail.gmail.com>
	<F7CC117B-5B7B-4274-AC2A-C256BE18CE04@classsoftware.com>
	<CAE0mPOva5LbEgCKS6uF0yqxJ9kZi7tO201PBKsz=5gYOoPmFqw@mail.gmail.com>
	<9EDF7605-4DFA-4FBC-BCA1-BA7454CAD4F0@classsoftware.com>
	<CAE0mPOvjTGxVNS6CrmJXn_UgPftOJb=ciiKjTTFBszF2OzSHxQ@mail.gmail.com>
	<3CEDB192-A693-4266-ACE2-A17A6D67D578@classsoftware.com>
	<CAAd0WraNCGfEoLrN2fq1-qpfMGWuauGoimWjTozcowGbJbC9UA@mail.gmail.com>
Date: Thu, 8 Mar 2012 11:48:53 -0800
Message-ID: 
 <CAE0mPOtxLJECjaJb9E1eR5gwey-2d1sn2-yCQ+eCAhpfeXD-3A@mail.gmail.com>
Subject: Re: [Proposal] New Component: Toast Notification
From: Daniel Reicher <danreicher@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d0447f2d0d83ba204bac090df

--f46d0447f2d0d83ba204bac090df
Content-Type: text/plain; charset=ISO-8859-1

>
>
> This idea of a toast component, which I'm not totally sold on in the SDK,
> got me to thinking. If there would be a reason to include well made ANEs
> into the SDK.
>
> For something like toast it would use the Android toasts on android
> devices, ios for ios, etc. And if running on the web just fall back to the
> "flex toast" for web.
>
>
I think that developing and maintaining ANEs should be something the
community strives for and I agree that there are situations where an ANE
would be a better fit. I think instead of keeping them in the SDK, they
should be leveraged by a tool like AIR Launchpad [1] where they can be
proactively included in a project based on the need of the project.

As for visual components, I think ANEs serve a purpose when you are trying
to achieve a *native* look across multiple platforms; whereas, built-in
components are for achieving a *uniform* look across multiple platforms.

Like you, I'm not sure where something like a toast fits in to that. I
think both cases are valid and cosmetically I feel like Flash/Flex devs are
more, shall we say picky, about UI consistency than your average folk. I,
for one, like the control that comes with using a built-in mechanism in
terms of styling. The last thing I would want is to use a very specific
font/color scheme only and jar the user out of that with a notification
that respects neither - or worse leads to confusion as to whether a
notification even "belongs" to the app they are using.


[1] http://labs.adobe.com/technologies/airlaunchpad/

--f46d0447f2d0d83ba204bac090df--