I think that's an excellent introduction and I look forward to your contributions.
Speaking for myself, I've long wanted to introduce more CRUD behavior into Tapestry, and tapestry-hibernate is only supposed to be the first step down that line. In terms of other integrations; those with proper licenses should be supported as part of the Apache Tapestry project; others can live on Tapestry360 (yes, it's still not quite ready!). On Mon, Feb 16, 2009 at 3:02 PM, Thiago H. de Paula Figueiredo <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
