Regarding the callback-functionality, I would prefer the event based approach
over the old one where you provide the callbac functionality.
As far as I understood it, I can still programatically create Alerts and
addEventListeners for the CloseEvents. I would really like to be able to
continue to be able to create Alerts programatically.
Regarding the discussion of what Buttons the Allert should have, what about
implementing an abstract BaseAlert (or something similar that contains a
command-bar which can be filled with Buttons and a concrete subclass Alert that
mimics the functionality of the original Alert?
Chris
________________________________________
Von: Maxime Cowez [maxime.co...@gmail.com]
Gesendet: Montag, 10. Juni 2013 22:08
An: dev@flex.apache.org
Betreff: [DISCUSS] Alerts and dialogs in Flex 4.x / Spark (was: Alerts and
dialogs in FlexJS)
As we were discussing some options in the thread "Alerts and dialogs in
FlexJS", we started to elaborate on dialog implementation in general. This
was carrying us away from the initial question so I started this new thread.
One of the initial topics was the possibility to declare Alerts/Dialogs as
mxml tags instead of using the old static function, something like this:
<fx:declarations>
<s:Alert id="alert" title="myTitle" text="myMessage"
close="handleAlertClose(event)"/>
</fx:declarations>
<s:Button label="show alert" click="alert.open()"/>
I mentioned that I had already created such an implementation, which can be
found at https://github.com/RIAstar/SkinnablePopUpFx
There's also a live demo at http://riastar.github.io/SkinnablePopUpFx/
Some people seemed to like the idea and asked some questions, which I'll
try to answer next.
Max
