As new controls and features are added to some of the Telerik product suites, other suites are being left behind. I am in no way complaining about new features being added to anything, mind you. I am simply asking that some consideration be made for all suites when you add new features to one. Prepare yourself to be amazed by a series of logical arguments that will compel you to take action! Namely, the action I want you to take...
All About Me
(or, "The Most Interesting Thing You've Ever Read In Your Whole Life")
My main product makes heavy use of your ASP.Net AJAX controls. However, you have some goodies in your Silverlight controls that would really make some parts of my product shine. Specifically, the property grid
controls. Now, I know the diagrams control is very new, but the property grid has been available as a Silverlight control for quite some time, and there really is no (non-sucky) alternative out there on the market. Besides, I'd want it to use the Telerik controls for property value selection (RadColorPicker, RadDatePicker, etc).
Now I understand the complexity involved in porting something like the Diagrams control to the ASP.Net AJAX suite, but you guys are the masters! And as for the property grid.. Well, if it were crazy easy, I'd write it, but for you guys it should be a snap, right?
It's All About Love
(or, "Gimme Mah Features!")
I hate to come across as one of those
people what with their, "why isn't my
toolset getting any love?" whiny pitch, so let me try a logical angle here... The future of Silverlight looks... well, icky, Microsoft says it's their platform for development of Windows Phone applications
(check your analytics, everybody -- a responsive, mobile-friendly UI is a far better investment than writing a UI just for Windows Phone). Also, they refuse to confirm or deny whether there's even going to be another major release after 5 (read: they wouldn't blood well refuse to confirm the next major release of ASP.Net MVC or Web Forms, so make your own conclusion), and teetering on the edge of irrelevance
It doesn't even run inside the Windows 8 IE unless you drop to desktop.
(or, "Mating with a Corpse -- Why It's Unhealthy")
So, even using mix-and-match to embed the Silverlight controls in order to (kinda) integrate them into my product that makes use of the ASP.Net AJAX suite seems risky, especially since something like the property grid would be ubiquitous. The absolutely worst part of it is that I'd still have to write non-Silverlight code to duplicate the same functionality for those who cannot -- or choose not to -- install the Silverlight plug-in. And honestly, saying "no" to just about anything a browser asks you to install might not be a terrible recommendation to give non-tech-savvy web users these days.
Did I mention I'd still have to duplicate the functionality in HTML anyway?
KendoUI for Web
(or, "Why Am I Paying Some Other Guy To Sleep With My Wife?")
Before I forget, let me just ask: Why not clean up the ASP.Net AJAX controls? Why not make them all snazzy with whatever it is the KendoUI for Web stuff is supposed to offer that's so much better? I know it's tempting to scrap something that's become boring and start over with the latest and greatest, but for existing customers (us, in this case), why not do the right thing and re-plumb the old stuff? It makes me extremely nervous (like, a totally manly nervous) that you're dedicating resources to a new suite that looks like it wants to replace the existing suite, only it wants me to rewrite all my code for the same -- and often less -- functionality.
Really, KendoUI for Web doesn't have anywhere near the number of controls. Are we supposed to mix and match ASP.Net AJAX controls with KendoUI for Web? Where does that leave us Web Forms people?
Anyway, as far as KendoUI for Web is concerned, I'd just really love to see the resources that are being used/spent on that project redirected to making the ASP.Net AJAX suite(s) (WebForms/MVC) that much more awesome. And make them all HTML5 sparkly if you like, too.
I'll avoid writing a whole section on disliking the idea of my subscription funding something that's going to make the current suite I've built my product around obsolete. That would just get all emotional and petty.
I could have saved us all a whole lot of time by just saying, "Hey, Telerik. May I please, please, pretty please have the Property Grid included in the ASP.Net AJAX controls? Please? Oh and if you could find time for the Diagrams control, that'd be just peachy." But then I couldn't have made it seem like it was about bigger, more important things.
Thank you for your consideration, and for the attention that I desperately crave.