tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Callender <geoff.callender.jumpst...@gmail.com>
Subject Re: [SUCCESS] Thiago H. de Paula Figueiredo as Tapestry Committer
Date Wed, 18 Feb 2009 02:45:15 GMT
Great ideas and observations, Thiago. I especially like your points  
about adopting the Java EE transaction annotations (and I'd like to  
see a tapestry-jpa module), and modules for JFreeChart and  


On 17/02/2009, at 10:02 AM, Thiago H. de Paula Figueiredo wrote:

> Hi!
> I would like to thank all confidence you put on me. I'll do my best  
> to not let you down. :)
> It is a honor to me to join the Tapestry development team. I'm very  
> passionate about this framework and I recommend it every time I get  
> a chance. I've done two presentations about Tapestry in Belo  
> Horizonte local events, one of them back in August, 2007. Even my  
> professional life revolves around it. I worked a little with T4 and  
> I'm a T5 user since T5.0.5, even earlier. I work part time in a  
> commercial project that uses Tapestry and the Ars Machina Project (http://www.arsmachina.com.br/project

> ), which includes some T5-related packages. I have some personal  
> projects, all of them using Tapestry or having some relation to it.
> By the way, I invite everyone to take a look at the Ars Machina  
> Project, specially Tapestry CRUD. I started it as a way to provide  
> some concepts that are not present in Tapestry, but, in my humble  
> opinion, I think they would fit very well If you think it is worth,  
> I'm willing to donate it or parts of it to the Tapestry project. All  
> feedback is welcome, positive or negative.
> I have a dream of having a full application stack built on Tapestry  
> IoC, a little bit like Spring. I like Spring a lot, but T-IoC is  
> awesome. At the same time, very easy and very powerful. With its  
> distributed configuration and AOP support, T-IoC provides an almost  
> perfect infrastructure for building truly convention-over- 
> configuration, drop-a-JAR-in-the-classpath-and-it's-working packages  
> and applications. The first steps is already done with Tapestry- 
> Hibernate and its transaction support. But I think Tapestry would  
> benefit a lot to have an implementation-agnostic transaction  
> framework. We could reuse the Java EE transaction annotations for  
> better compatibility.
> We could also build some simple official integration with other  
> frameworks like JFreeChart and JasperReports. Marketing-wise, we  
> could attract more users when they visit the site and they read that  
> their favorite frameworks are supported by Tapestry, even when we  
> know how easy you can do the integration yourself.
> Besides these larger projects, I also want to help the team to  
> address some issues that could improve the Tapestry user experience.  
> I also want to contribute to the documentation. Some questions in  
> the mailing list are about things that are not easy to find in the  
> docs.
> See you!
> -- 
> Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message