Q2 skinning

by ASP.NET AJAX Team | Comments 3
I thought I should drop a line to let you know about our plans for changes in the common skins of the Asp.Net product line. For the upcoming Q2 release this September we are planning to refresh the default look of our controls, discontinue development of two common skins, and add two new common skins in their place.

Default Skin Refreshed
The current default skin (the look of the components when you drop them from the toolbox; browse a preview of all current common skins here) has served well, but the time has come for a fresher look. While we wanted to preserve the skin neutral and clean, we have added contrast and a more modern look:


The Q2 dlls will ship with this new look built-in, so when you update your projects all components that use the default skin (or have no skin set) will automatically assume the new look. If you want to preserve the old default look, we will have the outdated version available for separate download from http://www.telerik.com/skins.

Discontinued Common Skins
We will say good bye to the Outlook common skin – 7 years after the introduction of Outlook 2000 it is time we move on to better things. The Inox common skin will need to go too – unless we get an overwhelming no from you, we will no longer update this skin in the future releases. Both skins will still be available for download.

New Common Skins
We are adding a Black Vista skin to all components and another web-style common skin that is still under discussion. Now is the time to get back with requests for a new look – if you’ve spotted a style you would love to have, leave a comment here and we will consider it.

Apart from all these changes, we have a host of new product-specific skins coming with the Q2 release, which is promising to be a major uplift for our Asp.Net interfaces. While we’re still cooking it all, we will appreciate any feedback you might have for the direction you want to see us heading.

About the author

Stefan Rahnev

Stefan Rahnev

is the Unit Manager of the ASP.NET Telerik Division. He has been working for the company since 2005, when he started out as a regular support officer. His next steps at Telerik took him through the positions of Technical Support Director and co-team leader in one of the ASP.NET AJAX teams. Stefan’s main interests are web development, agile processes planning and management, client services and psychology.

3 Comments

Geoff Van Brunt
I think this is a great idea. One comment though, I really hope that the default skin looks "the same" for all controls. For example, the old default textbox and comboboxes actually look different even though they are the same skin name.
Clayton Powell
You inox skin is one of my favourites. I really like the glossy appearance of the tabs/buttons etc. If you are to replace it then I hope you at least have another skin like it.
Martin Bischoff
Hi, I'm not sure if this comment be noticed, but anyway:

I have some doubts regarding your plans to include a new default skin. From the single screenshot, it is not very clear how much this skin differs from the previous (current) default skin.

The problem that I see, is that when I update the telerik controls (DLLs) the new skin will not fit into the rest of the UI's design.
In that case I would have to do two thins:
1) deploy the previous default skin (which means a lot more files to copy)
2) add the Skin="..." attribute to all radcontrol tags on all pages (possibly a lot of work)

Unless I'm understanding something wrong, changing the default skin could result in a lot of work for some of your customers to update to the latest rad controls version.
Please reconsider your decision once again, to ensure a smooth and painless upgrade scenario for existing solutions.

Thanks a lot,
Martin

Comments

  1.    
      
      
       
  2. (optional, emails won't be shown on public pages)
  3. (optional)
Read more articles by ASP.NET AJAX Team - or - read latest articles in Developer Tools