Have you ever experienced difficulties with hitting a button on a touch screen because of the button’s small size? Haven’t you wished texts were larger so you don’t need to zoom-in to read?

No more troubles - our new MetroTouch skin for Telerik’s ASP.NET AJAX controls is coming on board with Q2 2012, expected in about a week!

 

 

The Dimensions

Fingertip - 11mm - 32px

Dimensions are the biggest difference introduced in the MetroTouch skin. Almost every UI element has its regions and boundaries adjusted to a touch-friendly size of around 11mm at 72dpi per clickable area.

Mean percentage of erroneous trials for each...

In order to make the usage of embedded Telerik skins even more transparent than before and reduce the size of the main Telerik AJAX assembly (Telerik.Web.UI.dll), we decided to introduce a separate dll for the AJAX skins (Telerik.Web.UI.Skins.dll) to attain both goals. This assembly will be commenced with the official Q2 2011 release and some of you may have already noticed it in the AJAX Q2 2011 BETA pack posted several days ago.

Telerik.Web.UI.Skins.dll will accommodate the new set of skins shipped with the AJAX Q2 2011 drop (Transparent + Office2010 Blue/Silver/Black) while the rest of the skins will remain wrapped...

Our third official release for the year 2010 will come with a major visual improvement for RadColorPicker for ASP.NET AJAX. While we focused on adding new functionality to the control the past few releases, we decided it was time for a thorough appearance review.

Without further ado, here is the comparison between the old the new look (click to open in a new page):



Apart from the polishing of the overall look & feel, we “rounded” corners for all palettes and added shadows for the popup palettes. Another major difference is the order of colors in the Default preset palette. I know...

The RadSlider is getting a subtle, but still important update for its visual appearance in the Q1 2010 release of RadControls for ASP.NET AJAX. We made the appearance of all skins be consistent so you can have more choice when it comes to picking the right one for your application.

Here is the comparison between the old an new look:

The first difference is that we have added a border at both ends of the slider track. The border is not part of the track itself. The second difference is that all slider arrows now have a background and look...

By design the progress indicator of the web report viewer is centered in the viewable area. However in some cases you might want to change its position (e.g. ReportViewer longer than a viewable page). To achieve that we would get the progress area through a few lines of javascript and change its position according to our needs:

 

A sample project showing this functionality is available in this code library article. For those of you who would also like to change the viewer's skin and progress indicator itself, please review Applying custom skin to the web report viewer code library.

Hope this helps!

Steve...

If you’ve spent much time visiting “web 2.0” sites, you know that large font sizes are totally “in vogue” for data entry forms. Not only are they easy for all audiences to read, but they also imply a certain level of simplicity on a website. In fact, there are even some UX experts suggesting larger font sizes are better now that high-resolution monitors are the norm and not the exception.

If you’ve got a “beautifully designed” web 2.0-style site, though, and you’re working with RadInput, you know that the default skins “force” their own font size. What do you do if you...