Adobe is on holiday this week so I will answer for Peter.
There are org.apache.flex.html.Alert and SimpleAlert classes. SimpleAlert
wraps JavaScript alert and has no options. Alert is more like
mx.controls.Alert.
Other than Panel, there is no "base class" for dialogs. Feel free to make
one if
Hi Peter,
Is there anything I can use for dialogs or should I create something?
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Alerts-and-Dialogs-in-FlexJS-tp27505p53755.html
Sent from the Apache Flex Development mailing list archive at Nabble.com
I'd like to reply to some questions asked in this thread, but we seem to
have moved away from the original question too much. So I'll start a new
one to do so.
M
On Mon, Jun 10, 2013 at 4:59 PM, Christophe Herreman <
christophe.herre...@gmail.com> wrote:
> Hi Peter,
>
> 2013/6/10 Peter Ent
>
>
Hi Peter,
2013/6/10 Peter Ent
> One of the things I have disliked about Flex is the over-complication of
> some things. The majority of the time I think most developers are looking
> for a quick alert to the user (with a message and a button to dismiss the
> alert) and a question with two or thr
One of the things I have disliked about Flex is the over-complication of
some things. The majority of the time I think most developers are looking
for a quick alert to the user (with a message and a button to dismiss the
alert) and a question with two or three choices. Adding multiple buttons,
othe
Regarding the buttons, I would find the following interesting:
- option to define the order in which the buttons appear (e.g. Mac vs
Windows [1]). The flags approach doesn't work for this, so perhaps replace
this by an array.
- extra buttons: Yes, No, Cancel, OK, Retry, Ignore, Abort, ...
- custom
On 6/9/13 1:45 PM, "Carlos Rovira" wrote:
>Hi Maxime,
>
>very cool alert spark implementation. I was navigating the source code and
>have mainly a question about buttons. The eligible buttons in your version
>are 3 (commit, discard and cancel). In mx alert we have different options
>(Ok, Cancel
Hi Maxime,
very cool alert spark implementation. I was navigating the source code and
have mainly a question about buttons. The eligible buttons in your version
are 3 (commit, discard and cancel). In mx alert we have different options
(Ok, Cancel, Yes, No). I Think is the only point I miss. Have y
Alex, the mxml for my test case looks like this with minimal attributes:
For a demo of more attributes, have a look at
http://riastar.github.io/SkinnablePopUpFx/; it contains a code panel that
shows you the required mxml code as you pick values from the UI.
This mxml code is the equivale
Sounds interesting. If one of you can sketch out what the MXML would look
like, it would help clarify what you're thinking.
-Alex
On 6/8/13 12:13 PM, "Maxime Cowez" wrote:
>@Carlos: Interesting idea. I had already created a Flex 4 implementation
>of
>PopUp / Alert that can be used in a declara
Right, that turned out to be harder than I anticipated. To get this to work
I had to do the following things:
- redeclare all event metadata that is declared by the Alert component and
its base classes (to be able to use mxml event handlers)
- extend EvenDispatcher and relay all events dispatched b
@Carlos: Interesting idea. I had already created a Flex 4 implementation of
PopUp / Alert that can be used in a declarative way (see
https://github.com/RIAstar/SkinnablePopUpFx). I'll see if I can tweak it to
leverage your idea; don't think it should be too hard.
Max
On Sat, Jun 8, 2013 at 4:30 P
2013/6/8 Alex Harui
>
> Good point, we forgot about that. It might be possible to use includeIn
> to defer its instantiation or add some other attribute that works like
> that but isn't tied to states.
>
>
So from your response seems you're thinking in a state implementation
similar to what we h
My immediate thought on the delegate pattern is that it feels a little awkward.
As a flex dev, I feel the event flow would be more familiar, but I guess we
need to ask ourselves whether these api's will be used by old flex hats or
whether we're appealing to a new group of developers.
Maybe you
On 6/7/13 3:00 PM, "Carlos Rovira" wrote:
>Hi Peter,
>
>how this will show up? calling "foo.show()"?
>
>I use to like this kind of UI Object declaration, but in this particular
>case a problem I'm seeing is that we will generate the Alert although it's
>not called by the user, isn't it? (callin
Hi Peter,
how this will show up? calling "foo.show()"?
I use to like this kind of UI Object declaration, but in this particular
case a problem I'm seeing is that we will generate the Alert although it's
not called by the user, isn't it? (calling Alert.show() in the old way was
generating the obje
16 matches
Mail list logo
