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 01:23:35 GMT
> It's probably a bit early to be changing manifest files until we decide on
> new component namespaces and where they should live but you do have to
> compile it somehow.

Agreed. I hope this gets figured out as we go forward. I'll be honest -
part of the reason behind initiating this process is the desire to bring
some of these "gray" areas to light so they can be discussed and decisions
made. There seem to be a lot of questions being kicked down the road. I've
never built a theme that "inherited" from another theme, so I don't know
how easy or difficult that is. I've always assumed they were fairly
self-contained. Perhaps they need to share a project with different build

> Just not 100% sure if the popup is already showing do you need to restart
> the timer?

The thought process there was if you wanted to front end this with a
"ToastManager" singleton that only ever uses one instance of the Toast all
you would need to do is change the label and call show(). That would leave
the option open for queuing notifications, etc. Presumably, if you're
explicitly calling show() more than once you'd expect to get a "full"
showing; though, I may be off on that and open to discussion on behavior.
Ultimately, it was just a guess on desired behavior and I didn't look in to
how Android handles that case.

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