To 'install', save
form.html somewhere in your site.
I create a folder structure in
SiteAssets like so:
||This is where generic JS/CSS/HTML goes (e.g. jQuery, SPServices, generic SharePoint libraries).|
||This is where JS/CSS/HTML specific to a given project/app goes.|
||This is where JS/CSS/HTML specific to a given List goes.|
Doing this means you can use dynamic references elsewhere in your code, instead of hardcoding paths.
JS Link property of your
ListFormWebParts, add a link to
jslink_layout.js using a
i.e. using my folder structure, it would be
YOU CAN'T USE
../../ style relative paths with JSLink paths, they don't seem to work. Use tokens, root relative,
or absolute paths. Tokens are best because they're dynamic, so essentially relative.
Content Editor Web Parts to your
*Form.aspx pages. In the
Content Link property, add a link to your
i.e. using my folder structure, the link would be
CONTENT EDITOR WEB PARTS DON'T LIKE TOKENS, so use a relative or absolute path. (Yay, SharePoint.)
Haven't yet tested with
jslink js a b*%^h. Good luck.