On Tuesday 19 July 2005 16:25, Patrick Casey wrote: > I'm with you on this point and I'm wondering if part of that may be > due to the way Tapestry is perceived in the broader community. I consider > myself a pretty damn experienced servlet developer, and Tapestry definitely > wasn't easy to get ahold of. Frankly, without the ability to slog through > (and understand) a lot of Howard's source I don't know if I'd have been > able to pick up how a lot of things worked just from the doc and Tapestry > in Action.
No offense, but your servlet experience may have been your downfall. I had limited servlet experience -- enough to know that I was sick of sync'ing things with my JSPs. I had considerably more Swing experience though. When I saw Tapestry, I immediately drew the analogue to GUI development, and it just made sense to me. Others have said the same thing. So, really, I think it largely has to do with your programming background in general, rather than just simply your webapp background. Just to add to this, Tapestry did take some time to pick up, but mostly just because it was a new framework for me. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
