I think it's important to show reusability of a custom component in this tutorial.
It's better to be something practical. For example "ShortUserInfo" - a component that shows a user avatar, his name and date of registration. It can be used in the end of every forum post and every user article. > We have to keep in mind that the tutorial doesn't have to show all features. > It should satisfy the user in a way that he has finished a common use case > (list, create, update, delete), he should learn the general concept of > Tapestry and he should get a first impression that he can write large > enterprise application very efficiently with a minimum of duplicated. The > latter target is why I would like show component writing. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
