I'm asking you because you're smart enough to use LLBLGen, OK?

First, I'm not as concerned at the moment about AJAX per se - that is, using XmlHttpRequest to eliminate postbacks. That's a separate issue to me.

I AM interested in knowing what UI libraries you LLBLGen'ers are using for animations, popups, positioning, style, opacity, rounded-corners, and general UI coolness, er, usability.

I have been using mootools (http://mootools.net/) over the past several months and it's pretty impressive. CNET.com (http://clientside.cnet.com/) has a more extensive library based on mootools.

Now I COULD just use ASP.NET AJAX, but my gut feeling is that it isn't as mature as some of these other frameworks in the effects department. And the whole control extenders thing is cool but hems you into using <asp: Panel /> controls all over the place, which I don't want to do.

What are you using?

(edit) I'm also concerned about supporting Firefox and Safari - another reason I'm not sure about ASP.NET AJAX.

I've been using ASP.NET AJAX extensively since the early betas. There is a very rich set of JavaScript classes underneath ASP.NET AJAX so you don't have to use the control extenders if you don't want to.

Personally I find the control extenders quite limiting and so do most of my work with the JavaScript API.

FireFox and Safari support is good. I use FireFox daily for development and I've never noticed any issues with it. I also use Safari from time to time and haven't noticed any problems there either. I think Microsoft have done a pretty good job with the cross browser support.

For more info on using the effects from JavaScript check out http://ajax.asp.net/ajaxtoolkit/Walkthrough/AnimationReference.aspx

Jez wrote:

I've been using ASP.NET AJAX extensively since the early betas. There is a very rich set of JavaScript classes underneath ASP.NET AJAX so you don't have to use the control extenders if you don't want to.

Right. I've been following it through the betas but only as an observer - I've never had time to play with the javascript classes. It's interesting that the namespaces, classes, and members all seem to "feel" .NET-like.

Jez wrote:

Personally I find the control extenders quite limiting and so do most of my work with the JavaScript API.

The library looks pretty cool at first-glance but I'd rather use widgets on the client-side than stuff on the server-side that spits out a bunch of client-side stuff I can't manage.

Jez wrote:

FireFox and Safari support is good. I use FireFox daily for development and I've never noticed any issues with it. I also use Safari from time to time and haven't noticed any problems there either. I think Microsoft have done a pretty good job with the cross browser support.

The stuff I've used has worked fine in Firefox, but it's good to hear someone else say it's up to snuff.

I've got to say that in terms of being concise, I love mootools in comparison still. Thanks for your feedback.

Any other frameworks in use out there?