> What is it going to take to make the Tapestry user/developer community > happy? I'm probably going to continue to fight and try to justify T5's > design as the best choice to bring Tapestry into the future, but if it's > just upgrade worries then I think we might have something to work with.
I've been pretty quiet on the issue thus far, so now seems as good a time as any to hop in. One concern I have is the new DI framework. I've just recently become accustomed to HiveMind, and that was a big pill to swallow to begin with. I'm really not looking forward to learning a whole new way of doing things. That's not to say I don't mind things that ultimately are cleaner, but let's face it, there's something simple and easy about subclassing rather than figuring out where and how to make contributions. Howard's code sample for T5 seems to get rid of a bit of the complexity of HiveMind, but the code sample with per argument injections was quite difficult to read. The other problem is components. Even now I scan Tassel and see components that work fine in T3, but don't in T4. Normally if the source is available, I can make the necessary changes in a short amount of time. But, that really defeats the whole point of having a component. I should be able to just take it and use it. If the learning curve is really small this time, then it may be fine. I think people really underestimated how much moving to HiveMind complicated matters for Tapestry developers, however. So, it may be worthwhile to get outside thoughts on this prior to release. Additionally, if your library can make old components work with the new version, there may not be a problem there. Given that there is no T3 -> T4 library though, I have my doubts about a T4 -> T5 one. FWIW, we're not a large development shop. Man hours are a very important resource for us. They're better spent producing a Web app rather than learning the new way to do XYZ in Tapestry. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
