flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Reicher <danreic...@gmail.com>
Subject Re: [Proposal] New Component: Toast Notification
Date Thu, 08 Mar 2012 19:48:53 GMT
> 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/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message