Telerik UI for Windows 8 HTML 2015 Q1 Components Demos » Developer.Team

Telerik UI for Windows 8 HTML 2015 Q1 Components Demos

Telerik UI for Windows 8 HTML 2015 Q1 Components Demos
Telerik UI for Windows 8 HTML 2015 Q1 Components Demos | 3 Mb


Telerik built UI for Windows 8 HTML to target Windows Store application development and deliver a unique experience based on the Microsoft UX guidelines for Windows Store apps. The suite offers controls and capabilities that are currently not available in the WinJS library as well as replacements for some of the default HTML controls (select, slider, etc.). Telerik UI for Windows 8 are available in both HTML and XAML flavors, offering the same user experience on both platforms, allowing you to select the development platform.

This document includes help and API reference for:

RadAutoCompleteBox
RadCalendar
RadChart
RadColorPicker
RadComboBox
RadDatePicker and RadTimePicker
RadDropDownList
RadGauge
RadGrid
RadHubTile
RadNumericBox
RadPagination
RadRadialMenu
RadScheduler
RadSlider
RadSparkline
RadTokenInput
RadZoomable
Telerik.Data.DataSource

Teleriks Storage implementation provides users with local database support backed with the fast and server-less engine of SQLite. With Telerik’s storage solution developers can take advantage of relational databases (not BLOB files only) for processing data in their Windows Store apps, which widens the scope of the application types they can develop.

The Storage engine exposes to the C# world LINQ to SQLite extensions that are Telerik’s entry-level LINQ-enabled ORM implementation for SQLite. LINQ to SQLite is a LINQ provider that includes ORM features in its own implementation. Bundled with the vividness of entity classes developers can create relational databases with tables that map plain old CLR object (POCO) entities. It is up to the users to choose the way of usage that is most suitable for the particular scenario and their skills. If the developer likes the expressiveness of LINQ standard or query syntax, he can prefer them instead of raw SQL queries. Still, the engine supports pure SQL syntax-based queries which can be used in case this is the preferred approach.

Home:
http://www.telerik.com


[/b]

[b] Only for V.I.P
Warning! You are not allowed to view this text.
SiteLock