I'm also very keen to know the answer to this. Considering that Tap 4.1 is "round-the-corner", we're wondering whether to go ahead and use Tacos in our projects, and be able to refactor then with minimal effort when they become a part of Tapestry 4.1? Also any Tacos components that might get deprecated?
Essentially we want to make our applications 4.1 friendly ... Any pointers/answers would be of most help! Thanks!! On 8/2/06, Murthy Parthasarathi <[EMAIL PROTECTED]> wrote:
Hi All. If I have a Tapestry 4.0 application, that uses Tacos, what will be the effort involved in moving this app to Tapestry 4.1? Are Tacos components going to be available as-is, or will there be a lot of changes needed to the existing components? i.e. Should we limit ourselves from not using Tacos in 4.1? Cheers Murthy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thanks, Karthik