SharePoint 2013 has a powerful new feature known alternately as JSLink (when working in SharePoint)and Client-Side Rendering, or CSR (in the Microsoft literature). Either way, the point is the same… this code runs on the client side, meaning after the page loads. […] Client-Side Rendering is pretty straightforward, but takes a little understanding of how the JSLink functionality performs in order to get things just right.
This article will cover the changes between how we used REST in 2010 and what we need to ‚update‘ for using the streamlined interface in SharePoint 2013.
When creating SharePoint 2013 apps, you often need contextual information about the app and the user. This contextual information includes things like the URL of the host web or the account claim of the current user. […] To solve the problem, I created 2 libraries for managing context: one for SharePoint-Hosted Apps (wingtip.context.js) and one for Cloud-Hosted Apps (wingtip.remotecontext.js).
JS Link is a new web part property in many SharePoint 2013 web parts. It allows users and developers to create Client-Side Rendering (CSR) solutions within SharePoint 2013. In other words, it allows alternate formatting, data and functionality to be manipulated within a web part.
Covers several approaches for user interface customization in SP2013 – using JSLink to customize a list and/or view, creating custom Display Templates for the Content Search web part, and different approaches for customizing the search hover panel.
The client’s use case was as follows: they needed a way to be able to plot office locations on a map with contractually agreed to boundaries around them. These boundaries may be a specific radius around an office location or an irregularly shaped polygon. Once these are plotted on the map they required the ability to plot an address on the map to determine whether the address fell within any of the predefined boundaries.