If annotations is kept as separate a separate module like portlets, I think it should be added. So, could the wording for a vote be something like:
"Vote to create a Tapestry 4 module to support Annotations" On that topic, I'm +1 (non-binding) Richard -----Original Message----- From: Ron Piterman [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 08, 2005 3:41 AM To: [email protected] Subject: Re: Adding annotation support to Tapestry 4 So why not vote on adding it as an (unmature) extention to the tapestry project? ציטוט Richard Lewis-Shell: > Hi, > > I think we should add annotation support to Tapestry 4. The initial > hard work has already been done by Joni > (http://paloalto.laughingpanda.com/mediawiki/index.php/Tapestry_Annotations) , > so this would mostly be a matter of merging his work (which has been > deliberately compatibly licensed BTW). The benefit seems clear - and we > can claim support for one of Java 5's most interesting features (and by > extension, thus Java 5 itself). The downside would be that we would > have to use Java 5 to build Tapestry. Is that going to be a problem? > > Because this is a completely new feature, I do not see a good reason to > wait. Does anyone else? > > There is another reason I am interested in seeing this incorporated into > Tapestry sooner rather than later - one of encouraging our user > community. It seems to me that we are a strange open-source project - > we have a very good/strong user community, but not such a strong > developer community. We are currently very Howard-centric - there is a > lot of looking to Howard to guide us/tell-us-how-it-will-be (eg. > recently it was suggested that template defaults were "in Howard's > hands", and this attitude permeates on the -user list). While Howard > has done an incredible job of getting us this far, there is only so much > one person can do, even if that person is Howard!!! I think we run the > very real risk of losing relevance to other popular projects in the same > space (JSF, struts etc) with more active developer communities. We are > the only ones who can change that, and we do it (IMO) by encouraging > users to contribute more to the project, and the obvious way to > encourage user contribution is to incorporate those contributions that > fit well with Tapestry into the framework itself. > > To bring this back to the here and now, annotation support is such a > user-contribution that I think fits well with Tapestry. > > Richard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
