Hi Howard, and other readers, my 2 cents..
MAKE IT EASIER TO DONATE COMPONENTS & CODE Yes, but this has been discussed before a couple of times on this mailinglist, we definitely a central component / module hub where people can download and commit code to. Github is indeed the first candidate that comes to mind. We should not forget the Tapestry finder project (https://github.com/bobharner/Tapestry-finder) MOVE TOWARDS GREATER CLIENT-SIDE FOCUS I concur with you that the basic ajax stuff is do-able without too much hassle but once you get into the dirty details (multizone updates, adding extra javascript calls) its gets quite complicated and you need deeper insight into the Tapestry internals. Which is what some users (in our company) dont want , they just want it to work and then point me at the Jquery stuff... telling me how hard can it be ? Which gets me to the latest point: IS TAPESTRY JUST TOO WIERD/ESOTERIC/ENLIGHTENED FOR SOME/MANY JAVA DEVELOPERS? Yes, maybe for web developers that are used to other web frameworks (jsf, flash). I had the opportunity to find and select a web framework for our company and stumbled upon Tapestry and i liked it from the start. But other developers dont get (or dont want to get) the Tapestry way of thinking. And I dont really know what it is , because in the end , they can pump out web-apps (pages) faster than any other framework... It just some sort of hurdle you'll need to pass in order to fully embrace Tapestry. Good luck with 5.3 ! (im looking forward to it) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Feedback-from-Tapestry-users-tp4847427p4848167.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
