Windows style DateTime input and behavior

This is absolutely one thing that is missing in Web-based applications which has been major issue that prevents developers to migrate from Windows-based desktop application to Web-based application. End users have been very familiar with Windows date input control, where they can use the keyboard to select each element of the DateTime, and easily change only a part of DateTime element by either scrolling the value up and down or typing directly into that element, such as the day element or month element. In web application, there is only a textbox where the user has to write the full date and time without any keyboard controlled environment and often this could cause more human input errors which in the end causes application's to crash and database inconsistency.

With the availability of Intersoft WebInput.NET, developers can now consider web-based platforms as a primary decision for business and mission-critical applications. Along with Intersoft's vision to enable better and sophisticated web experiences, WebInput.NET is designed for that objective - that is to deliver the same rich and powerful User Interface components as in Windows platform. How does Windows? date input style enhance productivity

In traditional web textbox, end users would have to input the date and time elements as well as inputting the element's separator manually such as "-" or "/". However, it introduces many issues as there are many different date time formats even in the US alone. Name it short date short time, or long date and more, and still not to mention globalization-aware date formats and custom formats.

WebInput.NET also includes comprehensive value spinning for each DateTime element. That is, when each element exceeds the max of the value, it will increase the upper level of the element. For example: spinning through second, increasing minute, increasing hour, then day up to year.

Other input behaviors that are supported in WebInput.NET is the ability to press first character of month or day when using Long Date Format. For example, "m" for March or "a" for April. This capability is also Culture-aware and hence is not hard-coded in the core functions.