The inside scoop on what's happening with Tapestry ... from the creator of the Apache Tapestry framework. Plus all the normal, random thoughts on coding and technology.
Wednesday, November 19, 2008
Ready for 5.0.17?
Looks like 5.0.16 will not be the final release, there will be a very modest 5.0.l7 that addresses a couple of annoyances that didn't have good work-arounds.
Great job on this final push to GA, we have been using Tap since 5.0.2ish and could not be more happy with the framework. In the earlier days of developing with Tapestry we would stumble upon minor framework bugs and undoubtedly within a few minor releases that bug would be fixed!
Tapestry makes my job fun.
As an experienced Tap5 dev, one annoyance introduced in 5.0.16 that I hope makes 5.0.17 is the way that mixin render phases short circuit to the components counterpart render phases when the expected next render phase is the mixins counterpart render phase.
Please note that this is not a support forum for Tapestry. Requests for help will be deleted. Please subscribe to the Tapestry user mailing list if you are in need of support, or contact me directly for professional (for pay) support.
Spammers: Don't bother. I delete your comments and it's a waste of time for both of us. 垃圾邮件发送者：不要打扰。我删除您的评论和它的时间对我们双方的浪费
Great job on this final push to GA, we have been using Tap since 5.0.2ish and could not be more happy with the framework. In the earlier days of developing with Tapestry we would stumble upon minor framework bugs and undoubtedly within a few minor releases that bug would be fixed!
ReplyDeleteTapestry makes my job fun.
As an experienced Tap5 dev, one annoyance introduced in 5.0.16 that I hope makes 5.0.17 is the way that mixin render phases short circuit to the components counterpart render phases when the expected next render phase is the mixins counterpart render phase.
Keep up the awesome work!