On 7/20/05, Ben Wong <[EMAIL PROTECTED]> wrote: > I totally agree with others Tapestry has a high learning curve. I > considered myself an intermediate developer and have architected and written > many web applications. I still haven't figured out what exactly make > Tapestry such a hard framework to learn. I think part of it is that you are > exposed to and have to understand a lot of interfaces and design patterns > (e.g. IAsset, IRequestCycle, Delegate, IPropertySelectionModel).
This is why I like a lot of the new stuff involving injected pages and smart listener methods --- you see much less of this baggage. And I think the new binding prefixes are easier to grok; "bean:foo" vs. "ognl:beans.foo" requires an explanation of OGNL and where that "beans" property comes from. "bean:foo" simply means "the <bean> named 'foo'". -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
