views:

111

answers:

1

I work with many diverse technologies, and don't possess the time to evaluate every single UI framework, so I'd appreciate hearing other coders' experiences with various frameworks.

The stuff I've worked with so far (and my perceptions):

  1. WinForms: DevExpress (love the looks, hate the API and bloat), Krypton (free!, looks good, but limited), Telerik (don't like the looks)
  2. WPF: have only used WPF Themes pack :)
  3. Asp.Net: Telerik MVC Controls (love it), jQuery UI (looks great)
+2  A: 

I can really only offer WinForms experience, but I'll give a quick rundown:

I have used DevExpress fairly extensively on WinForms projects, and have been pleased with the quality of the components. I have actually been (generally) happy with the user API, though writing anything that extends their functionality is usually a substantial undertaking. Their visuals and feature set, however, are top-notch.

My last WinForms project was based on the Telerik WinForms suite, mostly because the developer who started the project (before I got there) came from an ASP.NET background, where the Telerik controls are evidently pretty popular and solid. This, unfortunately, is not true of the WinForms suite. The designers were extremely buggy (though more recent releases have helped this) and the feature set was...odd. I wouldn't recommend it.

I've also dabbled with Infragistics, mainly when we were searching for a suitable grid control at my last job (where we settled on DevExpress). I can't go into much detail, but a cursory examination felt like it was lacking both aesthetically and in the API department. They were a no-go for us pretty quickly.

Adam Robinson
Well, your experiences seem to mirror mine. However, my experience with the DevExpress API was less than pleasant - I remember having to spend several days to learn how to use the Grid control.
Dmitri Nesteruk
Do you happen to remember what gave you the trouble specifically?
Adam Robinson
DevExpress' GridControl API can be confusing to get the hang of, but is easy to use once you understand how it works. It's designed this way to avoid creating objects for every row (or, worse, cell) to improve performance for very large datasets.
SLaks