• .NET Mobile

    Changes in RadInput in Q2 2012 version of RadControls

    As you already know we have introduced new rendering model for RadInput in Q3 2011. It was later set as default mode in Q1 2012. The initial idea behind this change was to remove 2 of the input elements from the output HTML of the control and use a span that to overlay the visible one in order to show the formatted value. With this approach we really have fewer elements on the page and in the same time we could show, validate and submit different values. We also removed the table in order to provide better styling potential and boost...
  • .NET Mobile

    Get Better Performing Input Fields in Your ASP.NET AJAX Apps

    November 18, 2011 Share
    As we are constantly trying to improve our controls, in Q3 2011 we are introducing new HTML rendering for Telerik’s ASP.NET AJAX Input control – single input rendering. First of all I should assure you that the old rendering is still available, so all your custom styles and complicated scenarios with RadInput will still work. Let’s check some of the advantages of the single input rendering mode comes with:  No table is used when having buttons and/or labels, which results in quicker rendering. Less HTML is rendered as a whole, which leads to less data transferred to the client. The control can show readable text when...
  • .NET

    Web 2.0 font sizes with RadInput

    April 22, 2009 Share
    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...
  • .NET Mobile

    The Right Tool for the Right Job: RadTextBox for ASP.NET AJAX

    There are many ways to collect user input in ASP.NET web forms. There is the traditional ASP.NET TextBox control, or the handful of extenders available in the ASP.NET AJAX Control Toolkit. Or, you could stick to straight HTML with the <input> and <textarea> elements. For developers using Telerik’s web controls, there are more (and better) options. The RadControls for ASP.NET AJAX contain a set of input controls collectively named RadInput controls. Included in this set are the RadTextBox, RadNumericTextBox, RadMaskedTextBox, RadDateInput, and RadInputManager. In this blog post I will discuss the features of the RadTextBox for ASP.NET AJAX, including those which make it...
  • .NET

    Optimization Tips: RadInput vs. RadInputManager

    January 29, 2009 Share
    In the Q3 2008 release, Telerik introduced a new control to the RadControls for ASP.NET AJAX suite called RadInputManager. Like RadInput, it is designed to enable you to provided textboxes to your users that give real-time validation and feedback based on the entered text. The big difference with RadInputManager, though, is that you don't have to add lots of Telerik Input controls on your page to get this real-time feedback. Instead, you can quickly convert "standard" ASP.NET TextBoxes to RadInput textboxes via the RadInputManager configuration- similar to how you can use RadAjaxManager to quickly ajaxify your page without littering it with...