Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Talk about why we return the jQuery selector instead of Kendo UI widget, from jQuery methods #511

Closed
wants to merge 26 commits into from

9 participants

Derick Bailey Mihai Bazon Brandon Satrom Atanas Korchev Bundyo Georgi Krustev Rosen Konstantinov Alex Gyoshev Alexander Valchev
Derick Bailey

This is one of the things that confused me the most when I first started working with Kendo UI's controls - I didn't understand how to get access to the control instances, and didn't understand why I needed to call the jQuery data method to get it. It took me a while to realize that we are just following the jQuery convention of always returning the original selector from the method, instead of our widget instance.

I've updated the Getting Started docs for widgets to mention this. Hopefully this (or some better version of what I wrote) will help others make the connection faster than I did. :)

akorchev and others added some commits
Mihai Bazon
Collaborator

I think the clarification is good. This got my eye though because it started to piss me off too — essentially, I'd be happier if the API just returned the Kendo Widget object, rather than the jQuery object. But it's too late to change this without major breakage (and maybe it's just me :-) and it wouldn't be so useful in general).

However, what I find really pissing is that you have to know what kind of widget was created on an element, in order to get it:

var stuff = $(...).kendoStuff({ ... }).data("kendoStuff");

Makes my teeth hurt. ;-( It's not a big deal usually, but sometimes you need to deal with widgets that were created elsewhere and you don't really know what kind of a widget is instantiated on an element. I'd propose to inject a kendoWidget function into the jQuery objects, that would allow to do the above as:

var stuff = $(...).kendoStuff({ ... }).kendoWidget();

Anyone else? :-)

Derick Bailey

It already exists: kendo.widgetInstance ... I don't know if it's documented anywhere, Petyo pointed it out to me, here: https://github.com/telerik/kendo/blob/master/src/kendo.core.js#L2632

Mihai Bazon
Collaborator

Yeah, I noticed that today but I wasn't sure what it does (it takes that suite argument which is rather confusing). Seems less convenient than what I'm proposing...

Brandon Satrom
Owner

@derickbailey can you change this to pull into master instead of production? I'll merge it there and then cherry-pick to
prod.

As for the more general API comment, I like the kendoWidget proposal. widgetInstance does to the same thing effectively, but the naming of kendoWidget seems cleaner.

Derick Bailey

sending a PR to master shows 38 files changed... someone needs to update master first, and then i'll re-create this PR to master

Brandon Satrom
Owner

http://www.reactiongifs.com/wp-content/uploads/2013/03/seriousd.gif

Or... kill this PR, checkout master and apply this commit there.

Petyo Ivanov underlog deleted the branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Mar 19, 2013
  1. Atanas Korchev
  2. Atanas Korchev
Commits on Mar 20, 2013
  1. Bundyo
  2. Bundyo

    Rename mobile FAQ file.

    bundyo authored
  3. Georgi Krustev
  4. Rosen Konstantinov
  5. Rosen Konstantinov
  6. Alex Gyoshev

    Add colorpicker dependencies

    gyoshev authored
  7. Bundyo

    Rename mobile FAQ file, again.

    bundyo authored
  8. Alexander Valchev
  9. Bundyo
  10. Bundyo
  11. Bundyo
Commits on Mar 21, 2013
  1. Alexander Valchev
  2. Alexander Valchev
Commits on Mar 22, 2013
  1. Alex Gyoshev
  2. Atanas Korchev
  3. Atanas Korchev
  4. Atanas Korchev

    Add jquery version change

    akorchev authored
  5. Rosen Konstantinov
Commits on Mar 25, 2013
  1. Alexander Valchev
  2. Bundyo
  3. Bundyo
  4. Atanas Korchev

    Merge pull request #509 from andreymladenov/production

    akorchev authored
    Updating VS Extensions documentation
Commits on Mar 26, 2013
  1. Atanas Korchev

    Add complete page source.

    akorchev authored
  2. Derick Bailey

    adding text about the jQuery plugin methods returning the selected el…

    derickbailey authored
    …ement instead of the Kendo UI widget instance
This page is out of date. Refresh to see the latest.
Showing with 556 additions and 337 deletions.
  1. +52 −0 api/mobile/modalview.md
  2. +3 −3 api/web/autocomplete.md
  3. +20 −16 api/web/treeview.md
  4. +5 −0 getting-started/changes-and-backward-compatibility.md
  5. +2 −2 getting-started/framework/globalization/overview.md
  6. +1 −1  getting-started/introduction.md
  7. +98 −39 getting-started/javascript-dependencies.md
  8. +8 −4 getting-started/{mobile/faq.md → kendo-mobile-faq.md}
  9. +3 −1 getting-started/mobile/scroller.md
  10. +99 −55 getting-started/technical-requirements.md
  11. +1 −1  getting-started/using-kendo-with/aspnet-mvc/introduction.md
  12. +15 −0 getting-started/using-kendo-with/aspnet-mvc/troubleshooting.md
  13. +42 −41 getting-started/using-kendo-with/aspnet-mvc/vs-integration/convert-project-wizard.md
  14. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/configure.png
  15. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/convert.png
  16. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/convert2.png
  17. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/data_access.png
  18. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/mvc_wizard.png
  19. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/new1.png
  20. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/no_master_page.png
  21. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/options.png
  22. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/options_kendo.png
  23. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/project_template.png
  24. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade1.png
  25. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade2.png
  26. BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade3.png
  27. +56 −54 getting-started/using-kendo-with/aspnet-mvc/vs-integration/new-project-wizard.md
  28. +54 −53 getting-started/using-kendo-with/aspnet-mvc/vs-integration/upgrade-wizard.md
  29. +53 −50 getting-started/using-kendo-with/aspnet-mvc/vs-integration/vsextensions-options.md
  30. +1 −1  getting-started/using-kendo-with/jsp/introduction.md
  31. +26 −0 getting-started/using-kendo-with/php/introduction.md
  32. +1 −1  getting-started/using-kendo-with/using-kendo-with-requirejs.md
  33. +3 −2 getting-started/widgets.md
  34. +2 −2 howto/add-charts-and-graphs-to-an-application.md
  35. +2 −2 howto/add-widgets.md
  36. +4 −4 tutorials/ASP.NET/asp-net-hello-jquery.md
  37. +1 −1  tutorials/ASP.NET/asp-net-hello-services.md
  38. +4 −4 tutorials/asp_part_1.html
52 api/mobile/modalview.md
View
@@ -56,6 +56,58 @@ Open the ModalView
## Events
+### close
+
+Fired when the mobile ModalView is closed by the user.
+
+#### Example
+
+ <div data-role="view">
+ <a data-role="button" href="#foo" data-rel="modalview">Foo</a>
+ </div>
+
+ <div data-role="modalview" id="foo" data-close="onClose">
+ Foo
+ </div>
+
+ <script>
+ function onClose(e) {
+ //handle event
+ }
+ </script>
+
+#### Event Data
+
+##### e.sender `kendo.mobile.ui.ModalView`
+
+The widget instance which fired the event.
+
+### init
+
+Fired when the mobile ModalView and its child widgets are initialized.
+
+#### Example
+
+ <div data-role="view">
+ <a data-role="button" href="#foo" data-rel="modalview">Foo</a>
+ </div>
+
+ <div data-role="modalview" id="foo" data-init="onInit">
+ Foo
+ </div>
+
+ <script>
+ function onInit(e) {
+ //handle event
+ }
+ </script>
+
+#### Event Data
+
+##### e.sender `kendo.mobile.ui.ModalView`
+
+The widget instance which fired the event.
+
### open
Fires when the ModalView is shown.
6 api/web/autocomplete.md
View
@@ -67,7 +67,7 @@ The animation played when the suggestion popup is closed.
### animation.close.effects `String`
-The effect(s) to use when playing the close animation. Multiple effects should be separated with a space.
+The effect(s) to use when playing the close animation. Multiple effects should be separated with a space.
[Complete list of available animations](http://docs.kendoui.com/api/framework/fx#effects)
@@ -108,9 +108,9 @@ The duration of the open animation in milliseconds.
The data source of the widget which is used to display suggestions for the current value. Can be a JavaScript object which represents a valid data source configuration, a JavaScript array or an existing [kendo.data.DataSource](/api/framework/datasource)
instance.
-If the `dataSource` option is set to a JavaScript object or array the widget will initialize a new `[kendo.data.DataSource](http://docs.kendoui.com/api/framework/datasource)` instance using that value as data source configuration.
+If the `dataSource` option is set to a JavaScript object or array the widget will initialize a new [kendo.data.DataSource](http://docs.kendoui.com/api/framework/datasource) instance using that value as data source configuration.
-If the `dataSource` option is an existing `[kendo.data.DataSource](http://docs.kendoui.com/api/framework/datasource)` instance the widget will use that instance and will **not** initialize a new one.
+If the `dataSource` option is an existing [kendo.data.DataSource](http://docs.kendoui.com/api/framework/datasource) instance the widget will use that instance and will **not** initialize a new one.
#### Example - set dataSource as a JavaScript object
36 api/web/treeview.md
View
@@ -278,11 +278,11 @@ TreeView.
#### Parameters
-##### nodeData `String|Selector`
+##### nodeData `Object`
A JSON-formatted string or selector that specifies the node to be appended.
-##### parentNode `Element` *(optional)*
+##### parentNode `jQuery` *(optional)*
The node that will contain the newly appended node. If not specified, the new node will be appended to the
root group of the TreeView.
@@ -304,7 +304,7 @@ Collapses nodes.
#### Parameters
-##### nodes `jQuery | Element | Selector`
+##### nodes `jQuery | Element | String`
The nodes that are to be collapsed.
@@ -356,7 +356,7 @@ Removes a node from a TreeView, but keeps its jQuery.data() objects.
#### Parameters
-##### node `Selector`
+##### node `jQuery | Element | String`
The node that is to be detached.
@@ -380,7 +380,7 @@ Enables or disables nodes.
#### Parameters
-##### nodes `Selector`
+##### nodes `jQuery | Element | String`
The nodes that are to be enabled/disabled.
@@ -404,7 +404,7 @@ Expands nodes.
#### Parameters
-##### nodes `jQuery | Element | Selector`
+##### nodes `jQuery | Element | String`
The nodes that are to be collapsed.
@@ -437,7 +437,7 @@ Applicable when the widget is bound to a [HierarchicalDataSource](/api/framework
var treeView = $("#treeView").data("kendoTreeView");
var node = treeView.findByUid("95c1925d-a779-47fc-8420-b4274f01c037");
-If you want to find a node by its `id`, use the [datasource.get()](/api/framework/datasource#get) method and supply its uid to the `findByUid` method.
+If you want to find a node by its `id`, use the [dataSource.get()](/api/framework/datasource#get) method and supply its uid to the `findByUid` method.
#### Parameters
@@ -466,11 +466,11 @@ TreeView.
#### Parameters
-##### nodeData `String | Selector`
+##### nodeData `Object`
A JSON-formatted string or selector that specifies the node to be inserted.
-##### referenceNode `Element`
+##### referenceNode `jQuery`
The node that will be preceed the newly-appended node.
@@ -491,11 +491,11 @@ TreeView.
#### Parameters
-##### nodeData `String | Selector`
+##### nodeData `Object`
A JSON-formatted string or selector that specifies the node to be inserted.
-##### referenceNode `Element`
+##### referenceNode `jQuery`
The node that follows the inserted node.
@@ -510,10 +510,14 @@ Gets the parent node of the item
#### Parameters
-##### node `Element`
+##### node `jQuery | Element | String`
The child node whose parent will be returned.
+#### Returns
+
+`jQuery` The parent node of the given parameter node.
+
### remove
Removes a node from a TreeView.
@@ -525,7 +529,7 @@ Removes a node from a TreeView.
#### Parameters
-##### node `Selector`
+##### node `jQuery | Element | String`
The node that is to be removed.
@@ -555,7 +559,7 @@ Gets or sets the selected node of a TreeView.
#### Parameters
-##### node `Selector | jQuery` *(optional)*
+##### node `jQuery | Element | String` *(optional)*
If provided, the node of a TreeView that should be selected.
@@ -592,7 +596,7 @@ Gets or sets the text of a node in a TreeView.
#### Parameters
-##### node `Selector`
+##### node `String`
The node of which the text is being retrieved.
@@ -619,7 +623,7 @@ Toggles the node of a TreeView between its expanded and collapsed states.
#### Parameters
-##### node `Selector`
+##### node `String`
The node that should be toggled.
5 getting-started/changes-and-backward-compatibility.md
View
@@ -14,10 +14,15 @@ publish: true
#### Breaking changes
+* jQuery is updated to 1.9.1.
* **Mobile:** Rename scrollTreshold option of the ListView to **scrollThreshold**.
* **AutoComplete/ComboBox/DropDownList:** Rename enable option to **enabled**.
* **TreeView/HierarchicalDataSource/Node:** The `children` field is initialized depending on the `hasChildren` field, as previously documented. Use the `append` and `load` methods to initialize it, and if accessing the children field directly, verify if it is present.
+#### ASP.NET MVC
+
+Some ASP.NET MVC applications may be broken if using other libraries incompatible with jQuery 1.9.1. Further details available in the [troubleshooting guide](/getting-started/using-kendo-with/aspnet-mvc/troubleshooting#javascript-error-that-live-method-is-unavailable,-undefined-or-unsupported)
+
## KendoUI 2012 Q3 SP1
### Changes from 2012 Q3 (2011.3.1114)
4 getting-started/framework/globalization/overview.md
View
@@ -22,9 +22,9 @@ First let's start by adding the required culture script:
<script src="kendo.culture.en-GB.js"></script>
<!-- or when using the Kendo CDN -->
- <script src="http://cdn.kendostatic.com/<version>/js/jquery.js"></script>
+ <script src="http://cdn.kendostatic.com/<version>/js/jquery.min.js"></script>
<script src="http://cdn.kendostatic.com/<version>/js/kendo.all.min.js"></script>
- <script src="http://cdn.kendostatic.com/<version>/js/cultures/kendo.culture.en-GB.js"></script>
+ <script src="http://cdn.kendostatic.com/<version>/js/cultures/kendo.culture.en-GB.min.js"></script>
Now, you just need to set the culture script, which kendo should use:
2  getting-started/introduction.md
View
@@ -165,7 +165,7 @@ Here is the complete example:
</div>
<script>
// Initialize a new Kendo Mobile Application
- var app = new kendo.mobile.Applilcation();
+ var app = new kendo.mobile.Application();
</script>
Here is the complete example:
137 getting-started/javascript-dependencies.md
View
@@ -45,11 +45,11 @@ The minified versions of all JavaScript files (except jQuery) are also available
## jQuery version
-The current official version of Kendo UI requires **jQuery 1.8.2**. Currently jQuery 1.9 is **not** supported unless the [jquery-migrate](https://github.com/jquery/jquery-migrate/) plugin
-is also included. There are occasions in which a new jQuery version is released, which introduces breaking changes and is not compatible with existing Kendo UI versions.
+The current official version of Kendo UI requires **jQuery 1.9.1**. There are occasions in which a new jQuery version is released, which introduces breaking changes and is not compatible with existing Kendo UI versions.
In such cases we recommend using the previous jQuery version until the next official Kendo UI release that resolves the problems. We normally do not change the jQuery version that is shipped
with Kendo UI for service packs. We can do this for major releases. The following list provides compatibility information about previous major Kendo UI releases:
+* Kendo UI 2013.1.319 (Q1 2013) - jQuery 1.9.1
* Kendo UI 2012.3.1114 (Q3 2012) - jQuery 1.8.2
* Kendo UI 2012.2.710 (Q2 2012) - jQuery 1.7.1
* Kendo UI 2012.1.322 (Q1 2012) - jQuery 1.7.1
@@ -72,7 +72,7 @@ can be included on a per-widget basis.
### AutoComplete
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.model.js (if binding to XML)
@@ -86,14 +86,14 @@ can be included on a per-widget basis.
### Calendar
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.fx.js (optional for animation)
1. kendo.calendar.js
### Chart
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.data.xml.js (if binding to XML)
@@ -108,7 +108,7 @@ can be included on a per-widget basis.
### ComboBox
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.model.js (if binding to XML)
@@ -119,10 +119,31 @@ can be included on a per-widget basis.
1. kendo.list.js
1. kendo.combobox.js
+### ColorPicker
+
+1. jquery-1.9.1.js
+1. kendo.core.js
+1. kendo.fx.js (optional for animation)
+1. kendo.userevents.js
+1. kendo.popup.js
+1. kendo.draganddrop.js
+1. kendo.slider.js
+1. kendo.data.js (if using MVVM)
+1. kendo.binder.js (if using MVVM)
+1. kendo.colorpicker.js
+
+### ColorPalette
+
+1. jquery-1.9.1.js
+1. kendo.core.js
+1. kendo.userevents.js
+1. kendo.data.js (if using MVVM)
+1. kendo.binder.js (if using MVVM)
+1. kendo.colorpicker.js
### DataSource
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.model.js (if binding to XML or editing)
@@ -132,7 +153,7 @@ can be included on a per-widget basis.
### DatePicker
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.fx.js (optional for animation)
1. kendo.popup.js
@@ -142,14 +163,14 @@ can be included on a per-widget basis.
### Drag and Drop
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.draganddrop.js
### DropDownList
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.model.js (if binding to XML)
@@ -163,8 +184,12 @@ can be included on a per-widget basis.
### Editor
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
+1. kendo.data.js
+1. kendo.upload.js (if imagebrowser is used)
+1. kendo.listview.js (if imagebrowser is used)
+1. kendo.imagebrowser.js (if imagebrowser is used)
1. kendo.popup.js
1. kendo.list.js
1. kendo.dropdownlist.js
@@ -172,12 +197,24 @@ can be included on a per-widget basis.
1. kendo.fx.js (optional for animation)
1. kendo.draganddrop.js (if popups are draggable and/or resizable)
1. kendo.window.js
+1. kendo.colorpicker.js
1. kendo.editor.js
+### FlatColorPicker
+
+1. jquery-1.9.1.js
+1. kendo.core.js
+1. kendo.userevents.js
+1. kendo.draganddrop.js
+1. kendo.slider.js
+1. kendo.data.js (if using MVVM)
+1. kendo.binder.js (if using MVVM)
+1. kendo.colorpicker.js
+
### Gauge
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.js (if using MVVM)
1. kendo.binder.js (if using MVVM)
@@ -189,7 +226,7 @@ can be included on a per-widget basis.
### Grid
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.data.xml.js (if binding to XML)
@@ -206,6 +243,7 @@ can be included on a per-widget basis.
1. kendo.filtermenu.js (if filtering is enabled)
1. kendo.pager.js (if paging is enabled)
1. kendo.sortable.js (if sorting is enabled)
+1. kendo.userevents.js (if grouping, resizing or reordering is enabled)
1. kendo.draganddrop.js (if grouping, resizing or reordering is enabled)
1. kendo.groupable.js (if grouping is enabled)
1. kendo.editable.js (if editing is enabled)
@@ -217,7 +255,7 @@ can be included on a per-widget basis.
### ListView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.data.xml.js (if binding to XML)
@@ -232,29 +270,43 @@ can be included on a per-widget basis.
### Menu
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.fx.js (optional for animation)
1. kendo.popup.js
1. kendo.menu.js
+### MultiSelect
+
+1. jquery-1.9.1.js
+1. kendo.core.js
+1. kendo.data.odata.js (if binding to OData)
+1. kendo.model.js (if binding to XML)
+1. kendo.data.xml.js (if binding to XML)
+1. kendo.data.js
+1. kendo.fx.js (optional for animation)
+1. kendo.popup.js
+1. kendo.list.js
+1. kendo.multiselect.js
+
+
### NumericTextBox
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.numerictextbox.js
### PanelBar
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.fx.js (optional for animation)
1. kendo.panelbar.js
### Slider and RangeSlider
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.userevents.js
1. kendo.binder.js (if using MVVM)
@@ -263,7 +315,7 @@ can be included on a per-widget basis.
### Splitter
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.userevents.js
1. kendo.draganddrop.js
@@ -272,7 +324,7 @@ can be included on a per-widget basis.
### StockChart
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.odata.js (if binding to OData)
1. kendo.data.xml.js (if binding to XML)
@@ -288,7 +340,7 @@ can be included on a per-widget basis.
### TabStrip
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.js
1. kendo.fx.js (optional for animation)
@@ -297,16 +349,23 @@ can be included on a per-widget basis.
### TimePicker
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.fx.js (optional for animation)
1. kendo.popup.js
1. kendo.timepicker.js
+### Tooltip
+
+1. jquery-1.9.1.js
+1. kendo.core.js
+1. kendo.fx.js (optional for animation)
+1. kendo.popup.js
+1. kendo.tooltip.js
### TreeView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.userevents.js
1. kendo.data.js
@@ -317,21 +376,21 @@ can be included on a per-widget basis.
### Upload
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.upload.js
### Validator
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.validator.js
### Window
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.userevents.js
1. kendo.fx.js (optional for animation)
@@ -342,7 +401,7 @@ can be included on a per-widget basis.
### Mobile Application
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -354,7 +413,7 @@ can be included on a per-widget basis.
### Mobile ActionSheet
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.popup.js
@@ -370,7 +429,7 @@ can be included on a per-widget basis.
### Mobile Button
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -384,7 +443,7 @@ can be included on a per-widget basis.
### Mobile ButtonGroup
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -398,7 +457,7 @@ can be included on a per-widget basis.
### Mobile ListView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.data.js
1. kendo.data.odata.js
@@ -415,7 +474,7 @@ can be included on a per-widget basis.
### Mobile ModalView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.popup.js
1. kendo.history.js
@@ -430,7 +489,7 @@ can be included on a per-widget basis.
### Mobile NavBar
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -443,7 +502,7 @@ can be included on a per-widget basis.
### Mobile PopOver
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.popup.js
1. kendo.history.js
@@ -458,7 +517,7 @@ can be included on a per-widget basis.
### Mobile Scroller
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -468,7 +527,7 @@ can be included on a per-widget basis.
### Mobile ScrollView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -481,7 +540,7 @@ can be included on a per-widget basis.
### Mobile SplitView
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -495,7 +554,7 @@ can be included on a per-widget basis.
### Mobile Switch
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
@@ -509,7 +568,7 @@ can be included on a per-widget basis.
### Mobile TabStrip
-1. jquery-1.8.2.js
+1. jquery-1.9.1.js
1. kendo.core.js
1. kendo.history.js
1. kendo.fx.js
12 getting-started/mobile/faq.md → getting-started/kendo-mobile-faq.md
View
@@ -1,8 +1,8 @@
---
-title: Kendo UI Mobile Frequently Asked Questions
-meta_title: Kendo UI Mobile FAQ
+title: Kendo UI Mobile FAQ
+meta_title: Kendo UI Mobile Frequently Asked Questions
meta_description: Answers to Frequently Asked Questions about how Kendo UI Mobile works and behaves
-slug: gs-mobile-faq
+slug: gs-kendo-mobile-faq
tags: getting-started, mobile, faq
publish: true
---
@@ -90,7 +90,11 @@ external CSS should load web fonts, but we were not able to confirm this. As a w
A: By default Windows Phone 8 highlights all links when they are active (hold down). Stopping this behaviour requires manually adding a meta tag to your application/site -
adding the tag through Javascript is ignored:
-### Stop link highlighting in WP8
+#### Stop link highlighting in WP8
<meta name="msapplication-tap-highlight" content="no" />
+### Q: When I change the Windows Phone 8 theme, my application starts to look different. Why?
+
+A: Kendo UI Mobile adapts to the current theme in Windows Phone 8 and changes the background and highlight colors of your application. In the browser this is
+semi-automatic when you click inside the application to focus it, but in PhoneGap it happens automatically on app resume after you change the theme.
4 getting-started/mobile/scroller.md
View
@@ -47,8 +47,10 @@ For the scroller to work, its element should have fixed dimensions (width and/or
}
</script>
+### Scroller Properties
+
The mobile Scroller widget exposes the following fields:
+* **scrollElement** - the inner Scroller element that holds the scrolling content. Use this field if you wish to change the element contents after the Scroller is initialized on it.
* **scrollTop** - the number of pixels that are hidden from view above the scrollable area.
* **scrollLeft** - the number of pixels that are hidden from view to the left of the scrollable area.
-
154 getting-started/technical-requirements.md
View
@@ -6,18 +6,44 @@ slug: gs-technical-requirements
publish: true
---
+<style scoped>
+ .stripes
+ {
+ border: 1px solid #E15613;
+ border-collapse: collapse;
+ }
+ .stripes th
+ {
+ background: #E15613;
+ color: #fff;
+ }
+ .stripes tr:nth-child(2n+1) td
+ {
+ background: #fed;
+ }
+ .stripes td:nth-child(n+2)
+ {
+ text-align: center;
+ }
+ .stripes th,
+ .stripes td
+ {
+ padding: 3px 5px;
+ }
+</style>
+
# Technical Requirements for using Kendo UI
Below are the system requirements for the Kendo UI Framework.
-## Browser support
-<table class="devices-platforms stripes">
+### Supported Desktop Browsers
+<table class="devices-platforms stripes" style="margin-top: 1.2em;">
<tbody>
<tr>
<th class="browsers"></th>
- <th class="browsers-windows">Windows</th>
- <th class="browsers-mac">Mac OS</th>
- <th class="browsers">Linux</th>
+ <th class="browsers-windows" style="width: 100px">Windows</th>
+ <th class="browsers-mac" style="width: 100px">Mac OS</th>
+ <th class="browsers" style="width: 100px">Linux</th>
</tr>
<tr>
<td><span class="ie"></span>Internet Explorer</td>
@@ -27,9 +53,9 @@ Below are the system requirements for the Kendo UI Framework.
</tr>
<tr>
<td><span class="firefox"></span>Firefox</td>
- <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a></td>
- <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a></td>
- <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a></td>
+ <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a> +</td>
+ <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a> +</td>
+ <td><a href="http://www.mozilla.org/en-US/firefox/organizations/">ESR</a> +</td>
</tr>
<tr>
<td><span class="chrome"></span>Chrome</td>
@@ -39,61 +65,79 @@ Below are the system requirements for the Kendo UI Framework.
</tr>
<tr>
<td><span class="opera"></span>Opera</td>
- <td>10.0 +</td>
- <td>10.0 +</td>
- <td>10.0 +</td>
+ <td>11.0 +</td>
+ <td>11.0 +</td>
+ <td>11.0 +</td>
</tr>
<tr>
<td><span class="safari"></span>Safari</td>
- <td>4.0 +</td>
- <td>4.0 +</td>
+ <td>-</td>
+ <td>5.0 +</td>
<td>-</td>
</tr>
</tbody>
</table>
-**Previous versions are supported with some limitations**
-**NOTE: Browsers in BETA stage are not supported. Also note that Internet Explorer Quirksmode is not supported as it uses IE 5.5 rendering engine. Always specify [DOCTYPE](http://reference.sitepoint.com/html/doctypes) on your pages!**
-
-## Platform support
- <table class="devices-platforms stripes">
- <tbody>
- <tr>
- <th class="platform"></th>
- <th class="platform-version">Version</th>
- </tr>
- <tr>
- <td style="width: 100px;"><span class="windows"></span>Windows</td>
- <td>XP / Vista / 7 /Server 2003,2008 R1,R2 32,64-bit editions</td>
- </tr>
- <tr>
- <td><span class="mac"></span> Mac OS</td>
- <td>OS X +</td>
- </tr>
- <tr>
- <td><span class="android"></span> Android</td>
- <td>2.0 +</td>
- </tr>
- <tr>
- <td><span class="ios"></span> iOS</td>
- <td>3.0 +</td>
- </tr>
- <tr>
- <td><span class="blackberry"></span>BlackBerry</td>
- <td>6.0+</td>
- </tr>
- <tr>
- <td><span class="webos"></span>WebOS</td>
- <td>2.2+</td>
- </tr>
-**Kendo UI Mobile currently supports iOS 3.0+, Android 2.0+ and BlackBerry touchscreen devices.**
-
-
-##Prerequisites:
-
-* JavaScript must be enabled on all browsers
+**NOTES:**
+
+* Browsers in BETA stage are not supported
+* Internet Explorer Quirksmode is not supported as it uses IE 5.5 rendering engine. Always specify [DOCTYPE](http://reference.sitepoint.com/html/doctypes) on your pages!
+
+### Kendo UI Platform support
+
+<table class="devices-platforms stripes" style="margin-top: 1.2em;">
+ <tr>
+ <th class="platform">Platform</th>
+ <th class="platform-version">Version</th>
+ </tr>
+ <tr>
+ <td style="width: 150px;"><span class="windows"></span>Windows</td>
+ <td>XP +, Server 2003 +</td>
+ </tr>
+ <tr>
+ <td><span class="mac"></span> Mac OS</td>
+ <td>OS X +</td>
+ </tr>
+ <tr>
+ <td><span class="android"></span> Android</td>
+ <td>2.2 +</td>
+ </tr>
+ <tr>
+ <td><span class="ios"></span> iOS</td>
+ <td>4.0 +</td>
+ </tr>
+ <tr>
+ <td><span class="blackberry"></span>BlackBerry</td>
+ <td>7.0+</td>
+ </tr>
+ <tr>
+ <td><span class="blackberry"></span>Windows Phone</td>
+ <td>8.0+</td>
+ </tr>
+</table>
+
+**NOTES:**
+
+* Kendo UI DataViz is not supported on Android 2.x.
+* Hybrid mouse and touch devices are supported (for instance IE10, Chrome and Firefox on Windows 8).
+
+### Kendo UI Mobile Device Compatibility
+<p style="margin-top: 1.2em;">Kendo UI Mobile currently supports the default browsers on</p>
+
+* iOS 4.0+
+* Android 2.2+
+* Windows Phone 8+
+* BlackBerry 7.0+ touchscreen devices.
+
+**NOTE:**
+
+* Chrome for Android is also supported.
+
+## Prerequisites:
+
+* JavaScript must be enabled on all browsers
For best performance:
-* 'Disable script debugging' in the browser's config options must be checked
-* Caching on Internet Explorer must be activated
+* 'Disable script debugging' in the browser's config options must be checked
+* Caching on Internet Explorer must be activated
2  getting-started/using-kendo-with/aspnet-mvc/introduction.md
View
@@ -311,7 +311,7 @@ You can include the JavaScript and CSS files from CDN. Don't forget to specify t
<link href="http://cdn.kendostatic.com/<version>/styles/kendo.common.min.css" rel="stylesheet" type="text/css" />
<link href="http://cdn.kendostatic.com/<version>/styles/kendo.default.min.css" rel="stylesheet" type="text/css" />
<!-- jQuery is not hosted on Kendo CDN - include from another location -->
- <script src="http://code.jquery.com/jquery-1.8.2.min.js"></script>
+ <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://cdn.kendostatic.com/<version>/js/kendo.web.min.js"></script>
<script src="http://cdn.kendostatic.com/<version>/js/kendo.aspnetmvc.min.js"></script>
15 getting-started/using-kendo-with/aspnet-mvc/troubleshooting.md
View
@@ -32,6 +32,21 @@ If the application is also using Telerik Extensions for ASP.NET MVC tell the `Sc
If using ASP.NET bundles make sure the `Scripts.Render("~/bundles/jquery")` block appears **before** the Kendo JavaScript files. In that case you should not include jQuery as a `script` element.
+## JavaScript error that live method is unavailable, undefined or unsupported
+
+This error occurs after upgrading jQuery to 1.9. The `live` method is no longer available in this version of jQuery.
+As a result some JavaScript libraries which are often used in ASP.NET MVC applications will throw errors.
+Those libraries are **jquery.unobtrusive-ajax**, **jquery.validate** and **jquery.validate.unobtrusive**. You need to update the following packages via [Nuget](http://nuget.org):
+
+* [jQuery.Validation](https://nuget.org/packages/jQuery.Validation)
+* [Microsoft.jQuery.Unobtrusive.Ajax](http://nuget.org/packages/Microsoft.jQuery.Unobtrusive.Ajax)
+* [Microsoft.jQuery.Unobtrusive.Validation](http://nuget.org/packages/Microsoft.jQuery.Unobtrusive.Validation)
+
+> **Important**: In ASP.NET MVC 3 applications **jquery.unobtrusive-ajax** and **jquery.validate.unobtrusive** are not installed as NUget packages.
+You would need to install them separately. The packages are [Microsoft.jQuery.Unobtrusive.Ajax](http://nuget.org/packages/Microsoft.jQuery.Unobtrusive.Ajax) and [Microsoft.jQuery.Unobtrusive.Validation](http://nuget.org/packages/Microsoft.jQuery.Unobtrusive.Validation).
+First you must delete **jquery.unobtrusive-ajax.js**, **jquery.unobtrusive-ajax.min.js**, **jquery.validate.unobtrusive.js** and **jquery.validate.unobtrusive.min.js**
+from your **~/Sripts** folder. Then install Microsoft.jQuery.Unobtrusive.Ajax and Microsoft.jQuery.Unobtrusive.Validation.
+
## Visual Studio IntelliSense does not show the Kendo HtmlHelper extension method
### Solution
83 getting-started/using-kendo-with/aspnet-mvc/vs-integration/convert-project-wizard.md
View
@@ -1,41 +1,42 @@
----
-title: Convert Project Wizard
-slug: mvc-vsx-convert-project
-publish: true
----
-
-#Convert Project Wizard
-
-This help topic shows how to convert an existing ASP.NET MVC Application to a Kendo UI for ASP.NET MVC Application.
-
-The Convert Project Wizard converts an existing ASP.NET MVC 3 or 4 Application to Kendo UI for ASP.NET MVC Application **(Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Convert to Kendo UI for ASP.NET MVC Application)**. The convert wizard has two steps - project settings page and master pages settings one.
-
-##Project Settings
-
-![Project Settings](images/convert.png)
-
-You can modify the following project-wide settings:
-
-- **Version** - Choose which version of Kendo UI for ASP.NET MVC to use
-- **Copy Editor Templates** - Copy the predefined editor templates to ~/Views/Shared/EditorTemplates
-- **Use CDN Support** - Enable or disable [CDN](http://docs.kendoui.com/getting-started/javascript-dependencies#cdn) support.
-- **Copy Global Resources** - Copy the localization files to ~/Scripts/kendo/{version}/cultures
-
-##Master Page Settings
-
-If you have layout and master page you can choose whether you want to apply the selected settings to both or only one of them:
-
-![update Project Resources](images/convert2.png)
-
-- **Theme** - Choose the visual theme for your Kendo UI for ASP.NET MVC Application
-
-In case you have neither a master page nor a layout page you have the opportunity to add one:
-
-![No Master Page](images/no_master_page.png)
-
-The wizard gives you the option to create a new master page or layout page so that the user can set the Master Page settings. Depending on the selected view engine the wizard will create master page for WebForms or layout page for Razor.
-
-##Converting existing Telerik MVC Extensions project
-
-If you have an existing Telerik MVC Extensions project, you can convert it to Kendo UI project with the aid of the Convert Wizard. This will add the Kendo UI components to the project without removing the existing Telerik MVC Extensions content. For compatibility reasons, the Kendo UI Convert Wizard will attempt to disable the Telerik MVC Extensions embedded jQuery usage because it might interfere with the Kendo UI jQuery inclusion.
-
+---
+title: Convert Project Wizard
+slug: mvc-vsx-convert-project
+publish: true
+---
+
+#Convert Project Wizard
+
+This help topic shows how to convert an existing ASP.NET MVC Application to a Kendo UI for ASP.NET MVC Application.
+
+The Convert Project Wizard converts an existing ASP.NET MVC 3 or 4 Application to Kendo UI for ASP.NET MVC Application **(Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Convert to Kendo UI for ASP.NET MVC Application)**. The convert wizard has two steps - project settings page and master pages settings one.
+
+##Project Settings
+
+![Project Settings](images/convert.png)
+
+You can modify the following project-wide settings:
+
+- **Version** - Choose which version of Kendo UI for ASP.NET MVC to use
+- **Add referenced assemblies to solution** - Choose whether to copy referenced assemblies to your solution folder. The assemblies will automatically get added to source control when using Microsoft Team Foundation Server
+- **Copy Editor Templates** - Copy the predefined editor templates to ~/Views/Shared/EditorTemplates
+- **Use CDN Support** - Enable or disable [CDN](http://docs.kendoui.com/getting-started/javascript-dependencies#cdn) support.
+- **Copy Global Resources** - Copy the localization files to ~/Scripts/kendo/{version}/cultures
+
+##Master Page Settings
+
+If you have layout and master page you can choose whether you want to apply the selected settings to both or only one of them:
+
+![update Project Resources](images/convert2.png)
+
+- **Theme** - Choose the visual theme for your Kendo UI for ASP.NET MVC Application
+
+In case you have neither a master page nor a layout page you have the opportunity to add one:
+
+![No Master Page](images/no_master_page.png)
+
+The wizard gives you the option to create a new master page or layout page so that the user can set the Master Page settings. Depending on the selected view engine the wizard will create master page for WebForms or layout page for Razor.
+
+##Converting existing Telerik MVC Extensions project
+
+If you have an existing Telerik MVC Extensions project, you can convert it to Kendo UI project with the aid of the Convert Wizard. This will add the Kendo UI components to the project without removing the existing Telerik MVC Extensions content. For compatibility reasons, the Kendo UI Convert Wizard will attempt to disable the Telerik MVC Extensions embedded jQuery usage because it might interfere with the Kendo UI jQuery inclusion.
+
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/configure.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/convert.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/convert2.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/data_access.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/mvc_wizard.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/new1.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/no_master_page.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/options.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/options_kendo.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/project_template.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade1.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade2.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
BIN  getting-started/using-kendo-with/aspnet-mvc/vs-integration/images/upgrade3.png
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
110 getting-started/using-kendo-with/aspnet-mvc/vs-integration/new-project-wizard.md
View
@@ -1,54 +1,56 @@
----
-title: New Project Wizard
-slug: mvc-vsx-new-project
-publish: true
----
-
-#New Project Wizard
-
-This help topic shows how to create a new Kendo UI for ASP.NET MVC Application.
-
-The New Project wizard is used for creation of a new Kendo UI for ASP.NET MVC Application (**Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Create New KendoUI Project**). The wizard consists of two steps. On the first page the user can specify some project-wide settings while on the second page he can configure the data access layer.
-
-##Project Settings
-
-![New Project Wizard](images/new1.png)
-
-Using the options in the Kendo UI for ASP.NET MVC Project Settings page you can modify various project-wide settings:
-
-- **Version** - Choose which version of Kendo UI for ASP.NET MVC to use
-- **Target ASP.NET MVC Version** – Choose the targeted ASP.NET MVC version
-- **View Engine** – Choose between Razor and WebForms
-- **Theme** – Choose the visual theme for your Kendo UI for ASP.NET MVC Application
-- **Copy Editor Templates** - Copy the predefined editor templates to ~/Views/Shared/EditorTemplates
-- **Use CDN Support** - Enable or disable [CDN](http://docs.kendoui.com/getting-started/javascript-dependencies#cdn) support.
-- **Copy Global Resources** - Copy the localization files to ~/Scripts/kendo/{version}/cultures
-- **Add Test Project** – Choose whether to add a test project to the solution.
-
-##Data Access Settings
-
-![Data Access Settings](images/data_access.png)
-
-On the next step the New Project wizard’s Data Access page offers you initialize the creation of your data access layer using Telerik OpenAccess ORM. You are given the following options:
-
-- **Create OpenAccess Fluent Library Project** - After you choose this option an OpenAccess ORM project will be added, enabling you to create your object mapping in a declarative way. With this Code-Only approach all the necessary persistent classes and mappings are defined manually – the project will initially contain only a sample declaration to get you started. You can find more information about the Fluent Library project type [here](http://www.telerik.com/help/openaccess-orm/getting-started-fluent-mapping-overview.html).
-- **Create OpenAccess Domain Model Library Project** - The Domain Model is an auto-generated and editable diagram of your persistent classes. This option will start the Add Domain Model wizard after exiting Project Configuration Wizard, so that you can configure your data layer without writing a single line of code. You can create a new model and define you classes later using the tools that OpenAccess Visual Designer is offering, or retrieve the schema of an already designed database and generate classes for the selected tables and views. The different scenarios are described in the articles below:
- - [Create an empty model – Model First](http://www.telerik.com/help/openaccess-orm/getting-started-root-getting-started-with-update-schema-tools.html)
- - [Generate the domain model from a database - Database First](http://www.telerik.com/help/openaccess-orm/getting-started-root-generating-model-mappings-taking-database-first-approach.html)
-
-- **Skip creating an OpenAccess Model Library Project** - No data access project will be added.
-
-##Creation of New Kendo UI web application
-
-When you click 'Finish', the creation of new Kendo UI web application will begin. The wizard will:
-
-- Create new ASP.NET MVC application
-- Copy all Kendo UI scripts, including the vsdoc script that enables the VS Intellisense feature (if CDN support is not enabled)
-- Copy all Kendo UI content files (if CDN support is not enabled)
-- Copy all Kendo UI global resources (optional)
-- Copy all Kendo UI editor templates (optional)
-- Add reference to the Kendo.Mvc assembly
-- Apply the pre-selected theme
-- Create test project (optional)
-
-
+---
+title: New Project Wizard
+slug: mvc-vsx-new-project
+publish: true
+---
+
+#New Project Wizard
+
+This help topic shows how to create a new Kendo UI for ASP.NET MVC Application.
+
+The New Project wizard is used for creation of a new Kendo UI for ASP.NET MVC Application (**Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Create New KendoUI Project**). The wizard consists of two steps. On the first page the user can specify some project-wide settings while on the second page he can configure the data access layer.
+
+##Project Settings
+
+![New Project Wizard](images/new1.png)
+
+Using the options in the Kendo UI for ASP.NET MVC Project Settings page you can modify various project-wide settings:
+
+- **Version** - Choose which version of Kendo UI for ASP.NET MVC to use
+- **Add referenced assemblies to solution** - Choose whether to copy referenced assemblies to your solution folder. The assemblies will automatically get added to source control when using Microsoft Team Foundation Server.
+- **Target ASP.NET MVC Version** – Choose the targeted ASP.NET MVC version
+- **View Engine** – Choose between Razor and WebForms
+- **Theme** – Choose the visual theme for your Kendo UI for ASP.NET MVC Application
+- **Copy Editor Templates** - Copy the predefined editor templates to ~/Views/Shared/EditorTemplates
+- **Use CDN Support** - Enable or disable [CDN](http://docs.kendoui.com/getting-started/javascript-dependencies#cdn) support.
+- **Copy Global Resources** - Copy the localization files to ~/Scripts/kendo/{version}/cultures
+- **Add Test Project** – Choose whether to add a test project to the solution.
+
+##Data Access Settings
+
+![Data Access Settings](images/data_access.png)
+
+On the next step the New Project wizard’s Data Access page offers you initialize the creation of your data access layer using Telerik OpenAccess ORM. You are given the following options:
+
+- **Create OpenAccess Fluent Library Project** - After you choose this option an OpenAccess ORM project will be added, enabling you to create your object mapping in a declarative way. With this Code-Only approach all the necessary persistent classes and mappings are defined manually – the project will initially contain only a sample declaration to get you started. You can find more information about the Fluent Library project type [here](http://www.telerik.com/help/openaccess-orm/getting-started-fluent-mapping-overview.html).
+- **Create OpenAccess Domain Model Library Project** - The Domain Model is an auto-generated and editable diagram of your persistent classes. This option will start the Add Domain Model wizard after exiting Project Configuration Wizard, so that you can configure your data layer without writing a single line of code. You can create a new model and define you classes later using the tools that OpenAccess Visual Designer is offering, or retrieve the schema of an already designed database and generate classes for the selected tables and views. The different scenarios are described in the articles below:
+ - [Create an empty model – Model First](http://www.telerik.com/help/openaccess-orm/getting-started-root-getting-started-with-update-schema-tools.html)
+ - [Generate the domain model from a database - Database First](http://www.telerik.com/help/openaccess-orm/getting-started-root-generating-model-mappings-taking-database-first-approach.html)
+
+- **Skip creating an OpenAccess Model Library Project** - No data access project will be added.
+
+##Creation of New Kendo UI web application
+
+When you click 'Finish', the creation of new Kendo UI web application will begin. The wizard will:
+
+- Create new ASP.NET MVC application
+- Copy all Kendo UI scripts, including the vsdoc script that enables the VS Intellisense feature (if CDN support is not enabled)
+- Copy all Kendo UI content files (if CDN support is not enabled)
+- Copy all Kendo UI global resources (optional)
+- Copy all Kendo UI editor templates (optional)
+- Copy the Kendo UI assembly to your solution folder (optional)
+- Add reference to the Kendo.Mvc assembly
+- Apply the pre-selected theme
+- Create test project (optional)
+
+
107 getting-started/using-kendo-with/aspnet-mvc/vs-integration/upgrade-wizard.md
View
@@ -1,53 +1,54 @@
----
-title: Upgrade Wizard
-slug: mvc-vsx-upgrade-wizard
-publish: true
----
-
-#Upgrade Wizard
-
-This help topic shows how to upgrade a Kendo UI for ASP.NET MVC Application.
-
-The Upgrade Wizard has two main purposes:
-
-- Check and retrieve the latest available Kendo UI for ASP.NET MVC release
-- Change the version of Kendo UI for ASP.NET MVC in the projects in the solution use.
-
-The Upgrade Wizard can be launched from **Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Upgrade Wizard**
-
-![Choose projects](images/upgrade_menu.png)
-
-##Choose which projects will be updated
-
-![update Project Resources](images/upgrade1.png)
-
-The page allows you to configure the following options:
-
-- **Version** - Select from all versions that have been previously installed or downloaded using the VS Extensions
-- **Download** – Launch the Latest Version Acquirer tool.
-- **Browse** - Browse to a location where the new version is manually downloaded and extracted
-- **Choose Projects** - Choose which projects will be updated (it is recommended to keep all Telerik projects the same version)
-
-> **Note:**
-The distribution, downloaded by the Upgrade Wizard contains only the "hotfix" files, e.g. the bare bone files, needed for a project to run correctly. It does not contain the documentation or the demo project.
-
-> **Note:**
-The listed projects use Kendo UI for ASP.NET MVC 4. If the solution contains any projects which use Kendo UI for ASP.NET MVC for other MVC version, they will be displayed on a separate page. When you complete the wizard all selected projects from the different pages will be updated.
-
-##Update Project Resources
-
-![Update Project Resources](images/upgrade2.png)
-
-The Update Project Resources page allows you to:
-
-- **Update Editor Templates** - Update the editor templates in ~/Views/Shared/EditorTemplates
-
-##Create Backup
-
-![Create Backup](images/upgrade3.png)
-
-The **Create Backup** page allows you to:
-
-- **Create a backup before converting** - backup your projects before upgrading it
-- **Backup location** - specify the backup folder
-- **Show upgrade log when the Upgrade Wizard finishes the update** - display the upgrade log after the Upgrade Wizard finishes
+---
+title: Upgrade Wizard
+slug: mvc-vsx-upgrade-wizard
+publish: true
+---
+
+#Upgrade Wizard
+
+This help topic shows how to upgrade a Kendo UI for ASP.NET MVC Application.
+
+The Upgrade Wizard has two main purposes:
+
+- Check and retrieve the latest available Kendo UI for ASP.NET MVC release
+- Change the version of Kendo UI for ASP.NET MVC in the projects in the solution use.
+
+The Upgrade Wizard can be launched from **Visual Studio | Telerik | Kendo UI for ASP.NET MVC | Upgrade Wizard**
+
+![Choose projects](images/upgrade_menu.png)
+
+##Choose which projects will be updated
+
+![update Project Resources](images/upgrade1.png)
+
+The page allows you to configure the following options:
+
+- **Version** - Select from all versions that have been previously installed or downloaded using the VS Extensions
+- **Add referenced assemblies to solution** - Choose whether to copy referenced assemblies to your solution folder. The assemblies will automatically get added to source control when using Microsoft Team Foundation Server
+- **Download** – Launch the Latest Version Acquirer tool
+- **Browse** - Browse to a location where the new version is manually downloaded and extracted
+- **Choose Projects** - Choose which projects will be updated (it is recommended to keep all Telerik projects the same version)
+
+> **Note:**
+The distribution, downloaded by the Upgrade Wizard contains only the "hotfix" files, e.g. the bare bone files, needed for a project to run correctly. It does not contain the documentation or the demo project.
+
+> **Note:**
+The listed projects use Kendo UI for ASP.NET MVC 4. If the solution contains any projects which use Kendo UI for ASP.NET MVC for other MVC version, they will be displayed on a separate page. When you complete the wizard all selected projects from the different pages will be updated.
+
+##Update Project Resources
+
+![Update Project Resources](images/upgrade2.png)
+
+The Update Project Resources page allows you to:
+
+- **Update Editor Templates** - Update the editor templates in ~/Views/Shared/EditorTemplates
+
+##Create Backup
+
+![Create Backup](images/upgrade3.png)
+
+The **Create Backup** page allows you to:
+
+- **Create a backup before converting** - backup your projects before upgrading it
+- **Backup location** - specify the backup folder
+- **Show upgrade log when the Upgrade Wizard finishes the update** - display the upgrade log after the Upgrade Wizard finishes
103 getting-started/using-kendo-with/aspnet-mvc/vs-integration/vsextensions-options.md
View
@@ -1,50 +1,53 @@
----
-title: Visual Studio Extensions Options
-slug: mvc-vsx-options
-publish: true
----
-
-#Visual Studio Extensions Options
-
-The Visual Studio Extensions options dialog provides settings allowing you to configure the Kendo UI for ASP.NET MVC Visual Studio Extensions to best suit your needs.
-
-It can be accessed through **Visual Studio | Telerik | VSExtensions Options…**
-
-![Options menu](images/options_menu.png)
-
-The Options dialog contains two sets of options that affect the Kendo UI for ASP.NET MVC Visual Studio Extensions.
-
-## General Settings ##
-The settings under the General category affect all of the installed **Telerik Visual Studio Extensions**.
-
-![Options Dialog](images/options.png)
-
-###Project Upgrade Notifications for Detected Local Distributions
-
-- **Suggest project upgrades for Telerik product version available on my computer** – When enabled, you will be prompted to upgrade upon opening a project, which is not using the latest version of Telerik products installed on your system.
-- **Suggest upgrades when an equal Dev release detected on projects using a Trial** – When enabled, you will be prompted to upgrade if a licensed version is available on your system, but the current project uses a trial version.
-
-###Other Notifications
-- **Notify me when a Telerik subscription I have is about to expire** – When enabled, you will receive reminders if any of your subscriptions expire within the next month.
-
->**Note:**
-You can benefit subscription reminders only if you have saved your credentials in the Latest Version Acquirer tool.
-
-###Select a folder for downloads
-Configures the path where the extensions look for and store distributions.
-
->**Note:**
-Changing the folder path will not move existing folder contents from your previous path. Please, move your previous folder contents manually in case you still want to use them.
-
-##Kendo UI for ASP.NET MVC Settings
-All settings under the KendoUI category affect only the Kendo UI for ASP.NET MVC Visual Studio Extensions.
-
-![Options Dialog](images/options_kendo.png)
-
-###Latest version retrieval
-
-- **Include internal builds in Latest Version update and retrieval** – When enabled, the Latest Version Acquirer tool will retrieve internal builds as well as official releases when checking for a new version.
-
-###Notifications
-
-- **Show me message when a newer version is available on www.telerik.com** - When enabled, you will receive notifications if a new version of Kendo UI for ASP.NET MVC is available on the Telerik website.
+---
+title: Visual Studio Extensions Options
+slug: mvc-vsx-options
+publish: true
+---
+
+#Visual Studio Extensions Options
+
+The Visual Studio Extensions options dialog provides settings allowing you to configure the Kendo UI for ASP.NET MVC Visual Studio Extensions to best suit your needs.
+
+It can be accessed through **Visual Studio | Telerik | VSExtensions Options…**
+
+![Options menu](images/options_menu.png)
+
+The Options dialog contains two sets of options that affect the Kendo UI for ASP.NET MVC Visual Studio Extensions.
+
+## General Settings ##
+The settings under the General category affect all of the installed **Telerik Visual Studio Extensions**.
+
+![Options Dialog](images/options.png)
+
+###Project setup
+- **Add referenced assemblies to solution and source control** – Sets the default value for the Add referenced assemblies to solution option in the Project Configuration Wizard.
+
+###Project Upgrade Notifications for Detected Local Distributions
+
+- **Suggest project upgrades for Telerik product version available on my computer** – When enabled, you will be prompted to upgrade upon opening a project, which is not using the latest version of Telerik products installed on your system.
+- **Suggest upgrades when an equal Dev release detected on projects using a Trial** – When enabled, you will be prompted to upgrade if a licensed version is available on your system, but the current project uses a trial version.
+
+###Other Notifications
+- **Notify me when a Telerik subscription I have is about to expire** – When enabled, you will receive reminders if any of your subscriptions expire within the next month.
+
+>**Note:**
+You can benefit subscription reminders only if you have saved your credentials in the Latest Version Acquirer tool.
+
+###Select a folder for downloads
+Configures the path where the extensions look for and store distributions.
+
+>**Note:**
+Changing the folder path will not move existing folder contents from your previous path. Please, move your previous folder contents manually in case you still want to use them.
+
+##Kendo UI for ASP.NET MVC Settings
+All settings under the KendoUI category affect only the Kendo UI for ASP.NET MVC Visual Studio Extensions.
+
+![Options Dialog](images/options_kendo.png)
+
+###Latest version retrieval
+
+- **Include internal builds in Latest Version update and retrieval** – When enabled, the Latest Version Acquirer tool will retrieve internal builds as well as official releases when checking for a new version.
+
+###Notifications
+
+- **Show me message when a newer version is available on www.telerik.com** - When enabled, you will receive notifications if a new version of Kendo UI for ASP.NET MVC is available on the Telerik website.
2  getting-started/using-kendo-with/jsp/introduction.md
View
@@ -107,5 +107,5 @@ You can include the JavaScript and CSS files from CDN. Don't forget to specify t
<link href="http://cdn.kendostatic.com/<version>/styles/kendo.common.min.css" rel="stylesheet" type="text/css" />
<link href="http://cdn.kendostatic.com/<version>/styles/kendo.default.min.css" rel="stylesheet" type="text/css" />
<!-- jQuery is not hosted on Kendo CDN - include from another location -->
- <script src="http://code.jquery.com/jquery-1.8.2.min.js"></script>
+ <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://cdn.kendostatic.com/<version>/js/kendo.web.min.js"></script>
26 getting-started/using-kendo-with/php/introduction.md
View
@@ -66,3 +66,29 @@ and check the [JavaScript Dependencies](http://docs.kendoui.com/getting-started/
// Output the datepicker HTML and JavaScript by echo-ing the result of the render method
echo $datepicker->render();
?>
+
+### Complete Source
+
+ <!DOCTYPE html>
+ <html>
+ <head>
+ <link href="styles/kendo.common.min.css" rel="stylesheet" type="text/css" />
+ <link href="styles/kendo.default.min.css" rel="stylesheet" type="text/css" />
+ <script src="js/jquery.min.js"></script>
+ <script src="js/kendo.web.min.js"></script>
+ </head>
+ <body>
+ <?php require_once 'lib/Kendo/Autoload.php'; ?>
+ <?php
+ // Instantiate a new instance of the DatePicker class and specify its 'id'
+ $datepicker = new \Kendo\UI\DatePicker('datepicker');
+
+ // Configure the datepicker using the fluent API
+ $datepicker->start('year')
+ ->format('MMMM yyyy');
+
+ // Output the datepicker HTML and JavaScript by echo-ing the result of the render method
+ echo $datepicker->render();
+ ?>
+ </body>
+ </html>
2  getting-started/using-kendo-with/using-kendo-with-requirejs.md
View
@@ -44,7 +44,7 @@ In practice, if you use RequireJS you will probably have some files of your own
});
require([
- "http://ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js",
+ "http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js",
"app/foo",
"app/bar",
"k/kendo.menu.min",
5 getting-started/widgets.md
View
@@ -76,8 +76,9 @@ This example sets the [height](http://docs.kendoui.com/api/web/grid#height-numbe
## Getting reference to a Kendo UI widget
-When you call a Kendo jQuery plugin method (e.g. `$("#autocomplete").kendoAutoComplete()`) a new instance of the widget is initialized. That instance is associated with the target element
-and can be retrieved later using the [jQuery data](http://api.jquery.com/data/) method.
+Kendo UI widgets are initialized with a jQuery plugin method, as shown above. Calling one of these methods will not return the Kendo UI widget instance, though. Instead, the jQuery convention of returning the selected DOM element is maintained. This allows jQuery methods to be chained on the selected element, but does not provide immediate access to the Kendo UI widget instance.
+
+To get a reference to a widget instance, use the [jQuery data](http://api.jquery.com/data/) method to ask for the control by specifying the control type, prefixed with "kendo".
### Example - get reference to a Kendo UI widget
4 howto/add-charts-and-graphs-to-an-application.md
View
@@ -56,7 +56,7 @@ The first step is to add script and stylesheet references for jQuery and Kendo U
</footer>
<!-- CDN-based script reference for jQuery; utilizing a local reference if offline -->
- <script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
+ <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/jquery.min.js"><\/script>')</script>
<!-- CDN-based script reference for Kendo UI DataViz; utilizing a local reference if offline -->
@@ -95,7 +95,7 @@ The next step is to declare a target element for a chart. This will be represent
</footer>
<!-- Google CDN reference for jQuery; utilizing a local reference if offline -->
- <script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
+ <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/jquery.min.js"><\/script>')</script>
<!-- Kendo UI HTTP CDN script reference for DataViz; utilizing a local reference if offline -->
4 howto/add-widgets.md
View
@@ -57,7 +57,7 @@ The first step is to add script and stylesheet references for jQuery and Kendo U
</footer>
<!-- CDN-based script reference for jQuery; utilizing a local reference if offline -->
- <script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
+ <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/jquery.min.js"><\/script>')</script>
<!-- CDN-based script reference for Kendo UI DataViz; utilizing a local reference if offline -->
@@ -103,7 +103,7 @@ Here's an example for a pair of [AutoComplete](http://docs.kendoui.com/api/web/a
</footer>
<!-- CDN-based script reference for jQuery; utilizing a local reference if offline -->
- <script src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>
+ <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="js/jquery.min.js"><\/script>')</script>
<!-- CDN-based script reference for Kendo UI DataViz; utilizing a local reference if offline -->
8 tutorials/ASP.NET/asp-net-hello-jquery.md
View
@@ -146,22 +146,22 @@ need to install them separately.
This will put the latest version of [jQuery](http://jquery.com/) in the **Scripts **folder.
There will be 3 files there.
-**1. jquery-1.8.2.js** – This is the full [jQuery][2] source file.
+**1. jquery-1.9.1.js** – This is the full [jQuery][2] source file.
-**2. jquery-1.8.2.min.js – **This is the minified version of [jQuery][2],
+**2. jquery-1.9.1.min.js – **This is the minified version of [jQuery][2],
which removes all whitespace and comments, as well as “[minifying][21]” the
script to make it as small as possible. This version is identical to the
first one in every way except that it is unreadable for debugging. This is
generally the file used when an application is in production. For
development, use the full [jQuery][2] version.
-**3. jquery-1.8.2-vsdoc.js** – This file provides Intellisense inside of
+**3. jquery-1.9.1-vsdoc.js** – This file provides Intellisense inside of
Visual Studio for [jQuery][2]. As long as this file is named in the same way
as the [jQuery][2] file, Intellisense will work.
Open up the **Site.Master** page. Drag the full [jQuery][2] source into the
**head** of the page, directly below the **link** tag to **Site.css**. This
-will create a new **link** tag pointing to the jQuery-1.8.2.js file.
+will create a new **link** tag pointing to the jQuery-1.9.1.js file.
[JQuery][2] has now been added to the project.
![jQuery Added To The Master Page](images/hello-jquery-jquery-added-to-master.png)
2  tutorials/ASP.NET/asp-net-hello-services.md
View
@@ -315,7 +315,7 @@ displaying each employee in an HTML table row.
Open the **Site.Master** file and drag the **jquery.min** file over to the
page just below the **Site.css** link tag in the head of the page. At the time
-of this writing, the current version of jQuery is **jquery-1.8.2.min.js**.
+of this writing, the current version of jQuery is **jquery-1.9.1.min.js**.
![Add jQuery To Master Page](images/hello-services-add-jquery-to-master-page.png)
8 tutorials/asp_part_1.html
View
@@ -39,10 +39,10 @@ <h3 class="code-title">btnSayHello Click Event</h3>
<p>To install <a href="http://jquery.com/">jQuery</a> from <a href="http://nuget.org/">Nuget</a>, right-click the project and select <strong>Add Library Package Reference</strong>.&nbsp; Select <strong>Online </strong>from the left-hand side and enter “<strong>jquery”</strong> in the search box.&nbsp; Click the <strong>Install </strong>button on the <a href="http://jquery.com/">jQuery</a> package.&nbsp; This will install the VSDoc files as well.&nbsp; There is no need to install them separately.</p>
<p><a href="http://www.kendoui.com/Libraries/MetaBlogLib/Windows-Live-Writer-07976fe46293_7C8A-nuget-jquery-search.sflb.ashx"><img style="display: inline; background-image: none; border-width: 0px; border-style: solid;" title="nuget-jquery-search" alt="nuget-jquery-search" src="http://www.kendoui.com/Libraries/MetaBlogLib/Windows-Live-Writer-07976fe46293_7C8A-nuget-jquery-search_thumb.sflb.ashx" width="707" height="215" /></a></p>
<p>This will put the latest version of <a href="http://jquery.com/">jQuery</a> in the <strong>Scripts </strong>folder.&nbsp; There will be 3 files there.</p>
-<p><strong>1. jquery-1.8.2.js</strong> – This is the full <a href="http://jquery.com/">jQuery</a> source file.</p>
-<p><strong>2. jquery-1.8.2.min.js – </strong>This is the minified version of <a href="http://jquery.com/">jQuery</a>, which removes all whitespace and comments, as well as “<a href="http://en.wikipedia.org/wiki/Minification_(programming)">minifying</a>” the script to make it as small as possible.&nbsp; This version is identical to the first one in every way except that it is unreadable for debugging.&nbsp; This is generally the file used when an application is in production.&nbsp; For development, use the full <a href="http://jquery.com/">jQuery</a> version.</p>
-<p><strong>3. jquery-1.8.2-vsdoc.js</strong> – This file provides Intellisense inside of Visual Studio for <a href="http://jquery.com/">jQuery</a>.&nbsp; As long as this file is named in the same way as the <a href="http://jquery.com/">jQuery</a> file, Intellisense will work.</p>
-<p>Open up the <strong>Site.Master</strong> page.&nbsp; Drag the full <a href="http://jquery.com/">jQuery</a> source into the <strong>head</strong> of the page, directly below the <strong>link</strong> tag to <strong>Site.css</strong>.&nbsp; This will create a new <strong>link</strong> tag pointing to the jQuery-1.8.2.js file.&nbsp; <a href="http://jquery.com/">JQuery</a> has now been added to the project.</p>
+<p><strong>1. jquery-1.9.1.js</strong> – This is the full <a href="http://jquery.com/">jQuery</a> source file.</p>
+<p><strong>2. jquery-1.9.1.min.js – </strong>This is the minified version of <a href="http://jquery.com/">jQuery</a>, which removes all whitespace and comments, as well as “<a href="http://en.wikipedia.org/wiki/Minification_(programming)">minifying</a>” the script to make it as small as possible.&nbsp; This version is identical to the first one in every way except that it is unreadable for debugging.&nbsp; This is generally the file used when an application is in production.&nbsp; For development, use the full <a href="http://jquery.com/">jQuery</a> version.</p>
+<p><strong>3. jquery-1.9.1-vsdoc.js</strong> – This file provides Intellisense inside of Visual Studio for <a href="http://jquery.com/">jQuery</a>.&nbsp; As long as this file is named in the same way as the <a href="http://jquery.com/">jQuery</a> file, Intellisense will work.</p>
+<p>Open up the <strong>Site.Master</strong> page.&nbsp; Drag the full <a href="http://jquery.com/">jQuery</a> source into the <strong>head</strong> of the page, directly below the <strong>link</strong> tag to <strong>Site.css</strong>.&nbsp; This will create a new <strong>link</strong> tag pointing to the jQuery-1.9.1.js file.&nbsp; <a href="http://jquery.com/">JQuery</a> has now been added to the project.</p>
<p><a href="http://www.kendoui.com/Libraries/MetaBlogLib/Windows-Live-Writer-07976fe46293_7C8A-jquery-added-to-master.sflb.ashx"><img style="display: inline; background-image: none; border-width: 0px; border-style: solid;" title="jquery-added-to-master" alt="jquery-added-to-master" src="http://www.kendoui.com/Libraries/MetaBlogLib/Windows-Live-Writer-07976fe46293_7C8A-jquery-added-to-master_thumb.sflb.ashx" width="708" height="242" /></a></p>
<h4>Using jQuery Directly In The Browser</h4>
<p>Run the application again.&nbsp; When it comes up, open the developer tools by selecting <strong>F12</strong>.&nbsp; Switch to the <strong>Console</strong> tab in the developer tools.&nbsp; The console allows a developer to execute arbitrary JavaScript commands at runtime.&nbsp; As a test, type <strong>alert(“Hello!”); </strong>in the console and press enter.&nbsp; </p>
Something went wrong with that request. Please try again.