Rating:        Based on 2 ratings
Reviewed:  1 review
Downloads: 5028
Released: Dec 13, 2009
Updated: Dec 23, 2009 by ken_le
Dev status: Beta Help Icon

Recommended Download

Source Code
source code, 85K, uploaded Dec 15, 2009 - 4082 downloads

Other Available Downloads

Source Code jPoint.min.js
source code, 38K, uploaded Dec 15, 2009 - 397 downloads
Source Code jPointLoader.js
source code, 10K, uploaded Dec 15, 2009 - 292 downloads
Source Code jPoint-0.8.js
source code, 118K, uploaded Dec 15, 2009 - 257 downloads

Release Notes

  • - Recommended download
  • jPoint.mins.js - minified jPoint 0.8.js file to be used in production
  • jPointLoader.js - explanation below
  • jPoint-0.8.js -expanded version for learning and debugging
This is the first version of jPoint that has been labeled, "Beta". It is more robust, feature complete, and the foundation has been laid for an enterprise framework.
Functions were added to the Form class and a few functions under the Lists and List object were re-named for better readability and easier understanding.
jPointLoader was improved to better manage the scripts on the page and to allow the developer more flexibility on how to reference jQuery and jPoint while giving ultimate control and governance to central IT who manages the central javascript document library.
A new template, called jPart.Template, allows developers to paste their code inside to create a deployable and user configurable webpart, which we call a jPart.

jPoint 0.8 Summary of Updates

jPoint is now in Beta

jPointLoader has been improved:

  • View the comments in the file to understand how IT can centrally manage the file path variables while giving developers some flexibility when moving from dev to production.
  • Better management of multiple scripts on the page because jParts are referenced more generically by position rather than by a specific name.

jPointLoader Parameters

  • Parameters can now be added to the end of the src attribute in the script tag to dictate the source of either jQuery or jPoint files. Parameters include:
    • jQueryPath, jQueryFile, jPointPath, jPointFile, and jQueryForceLoad and jPointForceLoad
    • IF IT has left the file path variables empty, then developers can use parameters to determine the location of the jQuery and jPoint files.
<!-- Example where developer wants to use a particular version of jPoint and is okay with loading jquery from Google's servers [default]. -->
<script scr="//"></script>

<!-- Example where developer is already using jquery on the enterprise server and has downloaded jPoint library to a development site -->
<script scr="/servername/development/ScriptLibrary/jPointLoader.js?jQueryPath=/servername/CentralScriptLibrary/jquery/"></script>
  • Note: Only the first jPointLoader reference from on a page with multiple jParts is searched to grab the parameters.

jPart Template

  • A new template has been created so you can write code and create a jPart in 3 easy steps.
    1. Plug your code into the body of the jPart-Template.js where it says "jPart user code goes here"
    2. Fill out showConfigDefaults array, which determine what settings the user can change for your script.
    3. Save the file with a new name and you have just created a jPart script file. To deploy this script to a SharePoint page, simply reference jPointLoader.js and your new jPart file from a Form Web Part.

Newly Added Public Functions

  • jP.Form.field(HTMLElemOrJqueryObj) //returns the jPoint field that contains the passed in HTML element or jQuery object
  • jP.Form[<FieldName>].find(expr) //returns a jQuery object of the element inside of a jPoint field item that matches expr. expr can be itemrow, itemlabel, itemdata, or itemfield
  • jP.Form[<FieldName>].inputs(expr) //same as .find("iteminputs") except that expr can be ":visible" to further filter the returned jQuery object
  • jP.Lists.getList( [<SiteURL>] , ListName) has replaced now deprecated setSPObject(siteURL, listName)
  • jP.Lists[<ListName>].getSchema() has replaced now deprecated getSPListFields()
  • jP.Lists[<ListName>].getSPItemByID(listItemID) has replaced getSPItemID

Reviews for this release

very sleek and reduced my development time. there are some great ideas, particularly the ability to make the jPoint configurable via a simple GUI as a webpart. This essentially extends my webpart options without touching the server. documentation can be better, but what is available is expected.
by tuannyc on Aug 20, 2010 at 11:36 PM