Great!!! Thank you very much.
On 6/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I've been writing a new demo for 4.1. The only people that may have issues in the upgrade are those using Tacos. Everyone else shouldn't have to do much of anything else. I've gone through great pains to ensure it is very backwards compatible. There is no guarantee of course, but hopefully the upgrade process will be transparent, allowing you to "opt in" for using the new features when you choose. On 6/23/06, Cliff Zhao <[EMAIL PROTECTED]> wrote: > > Thank you very much. > > Do you have any write-ups on the incompatibilities between 4.0.2 and 4.1 ? > I > like to have an idea how much effort I should expect for upgrading my Tap > 4.0.2 application to Tap 4.1. > > I think that you may have already upgraded the Tap demos to 4.1. Could you > share how easy or difficult to upgrade them to Tap 4.1? > > Thanks. > > Best Regards, > Cliff Zhao > > On 6/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > 4.1 definitely uses dojo for any connection of events to ~anything~ in > > general in JS. I am very confident in the stability of the 4.1 js...In > > part > > because I have javascript based unit tests that confirm its > functionality, > > in part because I'm using dojo for everything and probably some > cockyness > > mixed in there somewhere. ..=p > > > > 4.1 has already been released, > > http://tapestry.apache.org/tapestry4.1/download.html . > > > > It's only snapshot builds for now, maybe a more complete release in the > > next > > couple of weeks. I'll keep the snapshots up to date with changes > > until/after > > then though. > > > > On 6/23/06, Cliff Zhao <[EMAIL PROTECTED]> wrote: > > > > > > I found that my Tapestry (4.0.2) application was causing memory leaks > in > > > IE. > > > > > > > > > I spent a lot of time trying to figure out why. I removed many parts > > from > > > my > > > page so that the page contains only one form with one Select > component. > > It > > > still leaks memory. I checked the Tapestry.js and saw it hooks up > three > > > attributes on form: events, onsubmit, onreset. Then, I added > > > dojo.event.browser.addClobberNodeAttrs(form,["events", "onsubmit", > > > "onreset"]) in my page. The IE memory leak went away. > > > > > > I will continue to check memory leaks with my application, if I find > > > anything related to Tapestry, I will post it here. > > > > > > Since Tapestry 4.1 is using dojo. Can I assume that this kind of > memory > > > leak > > > will not happen in 4.1? Or, are all Tapestry 4.1 event handlers based > on > > > dojo? When will Tap 4.1 be released? How confident the Tap committers > > feel > > > about Tap 4.1? > > > > > > Thanks. > > > > > > Best Regards, > > > Cliff Zhao > > > > > > > > > > > > -- > > Jesse Kuhnert > > Tacos/Tapestry, team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. > > > > > > -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
