[
https://issues.apache.org/jira/browse/TAP5-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984304#action_12984304
]
Howard M. Lewis Ship commented on TAP5-1421:
--------------------------------------------
What I currently have associates a severity (info, warn, error) and a duration
(one_shot, or until_confirmed) with each message. Mostly, we use one_shot
(i.e., displayed to the user once, then forgotten).
Part of what I have is a component to display the alerts, along with a link
used to clear the alerts in place (an Ajax request that also clears alert data
on the server).
The final piece of the puzzle is support for Ajax updates to send additional
messages in the response that are updated in place.
With what I have, plus some prettier CSS, you have a pretty nice solution. The
only downside is that the messages are simply strings ... I want the option to
render rich text, possibly by having a Block or Component be the "message".
> Create a standard way to track messages to be presented to the user
> -------------------------------------------------------------------
>
> Key: TAP5-1421
> URL: https://issues.apache.org/jira/browse/TAP5-1421
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> For a client, I've created a GlobalAlerts SSO, along with a
> GlobalAlertsManager service, an Alerts component, even JavaScript client-side
> support for adding and clearing alerts. I'd like to generalize this code a
> bit ... currently Alerts messages are limited to strings (fully renderable
> would be better).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
