RadWindowManager's client-side API provides radalert(), radpropmt()
and radconfirm() functions that can be used to replace the standard
browser's dialog boxes window.alert(), window.prompt() and window.confirm(). Just
like RadWindow, RadWindowManager's dialogs are
completely customizable and can be used in various scenarios.
Here are the main RadWindowManager's dialogs advantages:
Full customization of the window look to blend into the design of the site, thus
Control the initial size of the popup by providing width and height as extra parameters.
- Richer user experience by using HTML content for the dialogs.
Differences from browser's dialogs:
RadWindow dialogs are modal, e.g., they block the content underneath and prevent
the user from interacting with it, but there are ways to work around this behavior.
If it is absolutely necessary that a popup is modal, then the default browser popups
should be used.
Just like any other DHTML element, RadWindow dialogs exist only in the context of
the page in which they are created. They cannot leave the boundaries of the browser's
radalert, radconfirm and radprompt cannot block the execution thread like the standard
popups. That is why a callback function is added as a second parameter in radconfirm
and radprompt functions.
The radalert and radconfirm allow to easily control the content
image by passing an optional argument at the end of the method call. The argument
or absolute url and if empty string is provided - the image is removed.
The radalert provides client callback support. If a client callback
function is specified, the returned argument is true if the alert
was closed by the OK button and null if the [X] button was used.
The client callback function can also be used as a close handler.
The predefined dialogs (radalert, radconfirm and radprompt)
can be now called by using the new server methods RadAlert, RadConfirm
and RadPrompt of the RadWindowManager. Note, that
matter whether you show the dialog from the server or from the client.