Home » SharePoint 2013 » Wrapping Up Our Comments on jQuery Anatomy and Functionality Within SharePoint 2013

Wrapping Up Our Comments on jQuery Anatomy and Functionality Within SharePoint 2013

This post wraps up our comments on the second video tutorial included in our SharePoint-Videos.com training set, SP13-306 SharePoint 2013: JavaScript and jQuery Course. The title of this video is “jQuery Anatomy and Functionality Within SharePoint”. The instructor is Marc Anderson, SharePoint MVP and published author on this topic.

Marc Anderson’s presentation of HTML elements in this video tutorial is targeted to developers without any HTML coding experience. He explains the concept of tags, how elements work in pairs (including the self closing tags which have been in use since XHTML and HTML 4.0), and how (what HTML coders would refer to as “content”) values are stored between each iteration of an element pair in strings.

The example he uses to drill down into elements, is a form box for input to some sort of script (presumably a JavaScript, though the same syntax applies to ASP scripts or PHP scripts, etc). So he discusses the input tag, including why “id” must refer to a unique value, why “class” plays the role of a hook for CSS to plug into the form; attributes (meaning the type of form box, in the case of the example, a “checkbox”) as an opportunity for jQuery/JavaScript developers to customize a web page behavior with a unique feature (attribute); and, finally, “property” which is produced by the browser.

He then proceeds to present some basics of Cascading Style Sheets (CSS). In fact, developers with a good understanding of CSS generally take to jQuery very quickly and successfully. He notes jQuery “uses selectors that are very similar to CSS 3.0 Selectors”. Further, jQuery includes its “selectors” as a method the developer can use to select specific items on a page. He even remarks developers can discuss jQuery development issues with CSS experts to remediate problems. CSS experts will be able to provide greater insight into how similar features of jQuery should be implemented.

In sum, the combination of HTML, CSS and jQuery produces a very powerful capability developers addressing projects for SharePoint Server 2013 should use to their advantage.

If the viewer has considerable experience with HTML coding and CSS development (and understands the syntax of complex CSS selectors, in particular), most of this video can be skipped as Marc digs deeply into CSS components for most of the final 6 minutes of this video. But it’s worth viewing the last two minutes of the video for the points Marc makes about why developers should pick “unique” class and ID names in order to ensure styles intended for specific page components do not end up being incorrectly implemented, by SharePoint, on unwanted page components.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved