2011-12-23 13:01, Javix: > Sure it is not the best solution. Unfortunately, Tapestry is not able to do > it as flexible as it does Ruby on Rails.
Yes, your solution is not the best one but the reason is not Tapestry! There are hundreds of components using JS in Tapestry libraries and all manage to do I18N in a good way (I mentioned the built-in DateField and tapestry-jquerys' DataTable as examples). > And the community is not so active either. You got answers to your questions so please dont' say that the community is not active. > Thanks everybody who participated in this discussion. And good tapesrting :) We tried our best. -- Chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
