Not certain; I think the base implementation of the SSO and service would suffice for most projects, and the component could be easily augmented with CSS or replaced entirely.
On Wed, Jan 19, 2011 at 12:51 PM, Andreas Andreou (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TAP5-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983883#action_12983883 > ] > > Andreas Andreou commented on TAP5-1421: > --------------------------------------- > > Isn't it best to keep something like this out of the core? > >> 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. > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
