From our experience, upgrading has been smooth on about 5-6 of our customer projects. We have also done extensive unit testing to ensure compatibility. The only breaking change we did was to introduce the TagName property on IAjaxControl. That means custom developed server controls which did not inherit from any of the Gaia controls needs to implement this forward call to be upgraded.

Users report faster response times and in almost all cases -calls to ForceAnUpdate() can be removed :-)

I guess you've read about the DRIMR technology we've built, but we have not yet upgraded all of our extension controls to leverage the full potential which lies there. That's still on our todo list.

Because we are able to reuse controls rendered to the client, we are promoting a slightly different approach to control creation and that is to recreate new controls instead of reusing them by setting properties. By re-creating them fully, Gaia Ajax will diff the state with the previous instance thanks to a little function called GetReplacement() and then only serialize the state-diff without incurring viewstate overhead.

Good luck on the upgrade -should be well worth it as we move along here.

Ok, today is the day. I've got a couple of errors, so let's hope we can work it out.

1. What has happened with Effects in Scriptaculous? I used them quite a lot like:
$(ToggleName).appear({ duration: 0.2 }); or
new Effect.Morph(FVName, { style: 'margin-left: -5px;' }),
etc.

Now I've got errors on the client that Effect is unknown and appear is not a function.

I can see that you had in file AspectDroppable.js lines:
new Effect.DropOut(dragger.id, {queue:'parallel'});
new Effect.Pulsate(dropper.id, {queue:'parallel'});
back in v. 3.5. But in v.3.6 these lines are gone.

So the question is: What is the proper way of using Effects in 3.6?

Regards Pavol

EDIT: Ok, I figured it out. The effects.js file is in another project, so when I manually add this resource to the page, it works. I've got minor problems here and there, mostly fixed. The last major problem I noticed today is with Scheduler. It seems, that it can properly set left and top style properties, but completely ignore width and also when resized it gives me wrong height.

I will notify you about next progress, Pavol