I think there's a larger discussion to be had about "what belongs in core".
I think the original goal was "only things people couldn't live without" (Form, TextField, validations) and then grew from there: - Mega-components: BeanEditor, Grid - Client-side validations - Ajax components and mixins I really think core has evolved to be "things most projects can use as-is", or something to that effect. In fact, having a canonical way for services to record alerts to be presented to users would, itself, be a big bonus. I think it may have been premature at one time to include these things, but I think T5 now has a few years of real world experience to guide this ... including the projects I'm working on. So basically, I'm saying that I've found a specific use for this functionality and feel it can be generalized to most applications, and therefore it belongs. So we're going after "what makes people happy" rather than "pure". Alternately, perhaps we need to resuscitate the idea of a standard library (or libraries) beyond core. In T4, the library was a bit of a dumping ground for undocumented, untested code that people grew to depend on anyway. Perhaps this kind of thing belongs in TapX and we need to promote use of TapX more strongly. It originally started to fill needs caused by licensing issues, or desirable out-of-release-cycle changes (i.e., a standard library to patch prototype up to a more recent version). On Wed, Jan 19, 2011 at 2:35 PM, Andreas Andreou <[email protected]> wrote: > Well, with tapestry's extensibility it's not always straightforward > where such code better belongs to... Is there some guideline you're using > to decide? > Cause on the other hand, this SSO & service you're talking about would > also probably work with T5.2... that would imply that it'd better live outside > core, wouldn't it? > > > On Wed, Jan 19, 2011 at 22:56, Howard Lewis Ship <[email protected]> wrote: >> 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] >> >> > > > > -- > Andreas Andreou - [email protected] - http://blog.andyhot.gr > Tapestry PMC / Tacos developer > Open Source / JEE Consulting > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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]
