Comments on: Power User Toolbox: JavaScript for SharePoint – Pt6

By: martin

martin — Sun, 15 Feb 2009 00:50:36 +0000

about using google ajax, you can just replace the javascript library url with https:// when having https sharepoint site

By: Michael Greth MVP SharePoint Blog

Michael Greth MVP SharePoint Blog — Mon, 05 Jan 2009 10:05:36 +0000

SharePoint Kaffeetasse #98…

Tools und Addons Custom Content Editor Web Part for SharePoint jQuery http://jquery.com/ jQuery is a…

By: JQuery for Everyone: Dressing-up Links | End User SharePoint

JQuery for Everyone: Dressing-up Links | End User SharePoint — Tue, 16 Dec 2008 12:52:52 +0000

[...] jQuery to your page (see previous article for different [...]

By: Power User Toolbox: JavaScript for SharePoint - Pt9 | End User SharePoint

Power User Toolbox: JavaScript for SharePoint - Pt9 | End User SharePoint — Fri, 12 Dec 2008 17:54:59 +0000

[...] I mentioned in part 6, you want to manage your code properly both in and out of SharePoint. But sometimes, your [...]

By: David Kitchen

David Kitchen — Wed, 10 Dec 2008 12:31:29 +0000

Yup, I’d seen that.

It’s interesting, but still creates a few problems:
1) You have to edit your master pages or .aspx pages in the 12 hive, and that results in breaking support from MS.
2) You have to edit those files, and that means the modifications are global, they’re on or off across the farm rather than just specific areas.
3) You still don’t have knowledge about the page you’re on, ShUIE gives you a client side context object that mimics SPContext.Current so in the JavaScript you know pretty much everything about the page
4) You can’t share settings, so if you have a common location for some web service you’re accessing, you have to embed the settings within the scripts… when (not if) the environment changes you now have a support issue.

From the view point of “jQueryScriptManager also centrally manages scripts”, there is a similarity. However that’s where it ends, ShUIE is designed to manage when the scripts are included (based on context) as well as to help the developer by giving them information about the page, and then enable centralised light-up, shared settings, minification, CSS as well as JS, and so on.

So yup, knew about it but they are significantly different things with different aims (that overlap on the edges).

By: AutoSponge

AutoSponge — Sun, 07 Dec 2008 20:38:02 +0000

@David,

Thanks for the heads up about ShUIE.

I found another codeplex project with some similarities: http://www.codeplex.com/jQueryScriptManager/

By: David Kitchen

David Kitchen — Sun, 07 Dec 2008 09:53:46 +0000

You listed three ways to manage libraries, but there’s a fourth: ShUIE.

ShUIE = SharePoint User Interface Extender

What it does in one line: It gives you the power of jQuery within SharePoint coupled with a central location to store customisations and enable them.

What it really does: It uses the AdditionalPageHead WebControl to inject jQuery and jQuery.UI. It also outputs at that point scripts that have been defined in a database against the context of the page.

You can define JavaScript (jQuery) and CSS customisations to run against a Site, Web, a specific user or admin permissions, a List, a page mode (New|Edit|Display|Invalid).

You can easily package up jQuery plugins, or write your own.

The Pros and Cons would look like this:
Pros:
* Fastest Load Time.

Cons:
* If you have many large customisations the JavaScript is inline so it’s using up bandwidth.

But even that con isn’t that bad… as ShUIE is open source anyone can contribute and add a layer that writes the customisations to a docroot to allow client side caching and network caching.

Anyhow, it’s over here:
http://www.codeplex.com/ShUIE/