Hi !

I am pleased to announce the last release of Wooki : 0.4 ! After almost one year of development, all the features we have initially imagined have been implemented, you can use Wooki to

• Collaborate with friends on a single book resource
• Turn Wiki technology into a more interactive tool with direct feedback
• Follow user’s activities via RSS
• Get a printable version of your books via PDF generation
• Edit your content in a clean XHTML code without knowing anything about XHTML
• Get access to your action history and revert to a previous revision

So what’s next ?

It’s time to use it and stabilize it ! As a first experiment, I want to give to Wooki a concrete project to feed, thus i am eager to create a full demonstration application for Tapestry 5. This application will be based on the Seam Hotel Booking application. Objective of the experiment is to

1. Implement the application via Github
2. Compile the Tapestry 5 user’s experience via Wooki

Who wants to join ?

This is an opportunity for us to validate the user experience on Wooki, but we need people to work with. So, if you want to join this exciting experiment, please send me your github and wooki’s ids so i can give you committer and author’s rights. Tapestry 5 Newbies as Advanced are very welcome ! We need at last 4 people.

Thanks for reading.

After a few months of hard work to extract re-usable components from Wooki, the version 0.3 is finally out !

Along with Wooki improvements, we have created three major spin-off contributions that put the basis for a strong architecture that will make Wooki evolutive and ready for production soon:

• tapestry5-spring-tx allows you to benefit from Spring Platform Transaction management inside Tapestry
• tapestry5-installer provides a way to easily deploy and install tapestry 5 application
• tapestry5-db-migration, inspired from rails migrations, allows you to get full control over your database schema through your Tapestry 5 application lifecycle

All this work justifies this wooki version. It has been the opportunity to validate and polishing these different contributions in a real context.

Also the global code of Wooki has been reviewed to ease future evolutions and current features maintenance

• Move to Tapestry 5.2 that make development with Tapestry more and more confortable
• Integration of spring-acl to handle authorization on wooki’s resources
• Creation of an abstraction layer to handle DB query parameters like range, created since
• Centralize activity lookup for RSS feeds and front display
• Centralize application link management and improve the application security layer

To conclude, one important news is that wooki has moved to spreadthesource organization on github

We hope you will find inspiration from all these as a user or a Tapestry developer ! Give it a try !

Thanks for reading.