Moving on from 4.0.*
Howdy, I've been using Tapestry since 2.*, and am currently working with the 4.0.12 release. I've been very happy until recently, and I guess now I'm looking for reassurance/guidance. My issue is that Tapestry 5 is still -- it appears to me -- changing significantly between releases, and I'm obviously wary of moving a production application to it while it's stabilizing and still completing features. Tapestry 4.1.* is appealing except it ships with a specific version of Dojo -- I've had to rely on Subversion/manual patches to Dojo to get a lot of my widgets/packages to work properly, and it appears to me that Tapestry 4.1.* requires that I use the shipped version or risk foregoing most of the reasons for switching to it, which would potentially screw with a lot of my existing dojo-based code, and also preclude me from upgrading to dojo 0.9/1.0 if I wanted or even needed to. Thus, I feel as if I'm in Tapestry limbo, indefinitely locked into the inactive 4.0.* release-branch. Am I suffering from misconceptions? Thanks! Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving on from 4.0.*
I can't speak to whether or not you should upgrade to T5 or how stable it is relative to your requirements, but can mention some things about Dojo versions. The packaged version of Dojo is sort of Dojo 0.4.3 but contains many local fixes not available in the official distribution - most being smallish bugs we've found in widgets / other things in various places. I'm not saying you are guaranteed to have your problems fixed in this version, but it may be worth looking at if you have the time / energy to do a quick glance. You can also attempt to replace the provided tapestry version with one of your own by overriding the AjaxShellDelegate renderer used in either the Shell or ScriptIncludes components: http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/dojo/AjaxShellDelegate.html I think Andy has something up his sleeve for 4.1.4 (4.1.5?) support for using different javascript libraries - which could possibly mean you can use Dojo 0.9 or similar. . It's really not ~that~ much work to make switching javascript libraries possible - it's just been low on my priority list and I've heard Andy mentioning doing something about it so I've ignored it The core supports using prototype dojo already, it's just a question of those few places that have library specific knowledge - such as the form related javascript. ...which I can see Andy has already been making generic for this purpose. I don't know, we can try and squeeze that feature in to the 4.1.4 release depending on what Andy has to say about it. It's really not as much work as people seem to think.. On Nov 7, 2007 3:55 PM, Jim [EMAIL PROTECTED] wrote: Howdy, I've been using Tapestry since 2.*, and am currently working with the 4.0.12 release. I've been very happy until recently, and I guess now I'm looking for reassurance/guidance. My issue is that Tapestry 5 is still -- it appears to me -- changing significantly between releases, and I'm obviously wary of moving a production application to it while it's stabilizing and still completing features. Tapestry 4.1.* is appealing except it ships with a specific version of Dojo -- I've had to rely on Subversion/manual patches to Dojo to get a lot of my widgets/packages to work properly, and it appears to me that Tapestry 4.1.* requires that I use the shipped version or risk foregoing most of the reasons for switching to it, which would potentially screw with a lot of my existing dojo-based code, and also preclude me from upgrading to dojo 0.9/1.0 if I wanted or even needed to. Thus, I feel as if I'm in Tapestry limbo, indefinitely locked into the inactive 4.0.* release-branch. Am I suffering from misconceptions? Thanks! Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving on from 4.0.*
Sounds perfect! Thanks, guys; I really appreciate the response. Jim Andreas Andreou wrote: Yes, I want to commit this for 4.1.4... I just want to polish what i have and send it in till the weekend - stay tuned ;) On 11/7/07, Jesse Kuhnert [EMAIL PROTECTED] wrote: I can't speak to whether or not you should upgrade to T5 or how stable it is relative to your requirements, but can mention some things about Dojo versions. The packaged version of Dojo is sort of Dojo 0.4.3 but contains many local fixes not available in the official distribution - most being smallish bugs we've found in widgets / other things in various places. I'm not saying you are guaranteed to have your problems fixed in this version, but it may be worth looking at if you have the time / energy to do a quick glance. You can also attempt to replace the provided tapestry version with one of your own by overriding the AjaxShellDelegate renderer used in either the Shell or ScriptIncludes components: http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/dojo/AjaxShellDelegate.html I think Andy has something up his sleeve for 4.1.4 (4.1.5?) support for using different javascript libraries - which could possibly mean you can use Dojo 0.9 or similar. . It's really not ~that~ much work to make switching javascript libraries possible - it's just been low on my priority list and I've heard Andy mentioning doing something about it so I've ignored it The core supports using prototype dojo already, it's just a question of those few places that have library specific knowledge - such as the form related javascript. ...which I can see Andy has already been making generic for this purpose. I don't know, we can try and squeeze that feature in to the 4.1.4 release depending on what Andy has to say about it. It's really not as much work as people seem to think.. On Nov 7, 2007 3:55 PM, Jim [EMAIL PROTECTED] wrote: Howdy, I've been using Tapestry since 2.*, and am currently working with the 4.0.12 release. I've been very happy until recently, and I guess now I'm looking for reassurance/guidance. My issue is that Tapestry 5 is still -- it appears to me -- changing significantly between releases, and I'm obviously wary of moving a production application to it while it's stabilizing and still completing features. Tapestry 4.1.* is appealing except it ships with a specific version of Dojo -- I've had to rely on Subversion/manual patches to Dojo to get a lot of my widgets/packages to work properly, and it appears to me that Tapestry 4.1.* requires that I use the shipped version or risk foregoing most of the reasons for switching to it, which would potentially screw with a lot of my existing dojo-based code, and also preclude me from upgrading to dojo 0.9/1.0 if I wanted or even needed to. Thus, I feel as if I'm in Tapestry limbo, indefinitely locked into the inactive 4.0.* release-branch. Am I suffering from misconceptions? Thanks! Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
