Telephone 01926 333686
Point customers can download the latest version of Point as a zip file from our Online License Manager at https://licensing.widgit.com/. If you are a Point customer and haven't received a login for this site, please contact firstname.lastname@example.org. The zip file contains all the code you need and full installation instructions.
Since version 2.1, Point has been able to infer information about a word from the context. For example, if the sentence "I drink a drink" was present in a Point-enabled page, the first symbol in the Point tooltip for the first "drink" would be the symbol for the verb form of "drink", while the first symbol in the Point tooltip for the first "drink" would be the symbol for the noun form of "drink".
Point customers can enable this for their site using a configuration option in point_config.js:
Point.symboliseContext = true;
|This feature depends on contextual symbolisation being enabled.|
Point has supported idioms since version 2.1. This means, for example, that when the user hovers over any word in the phrase "fish and chips", the whole phrase is highlighted and symbols for the whole idiom are displayed.
Point customers can enable this for their site using an option in point_config.js:
Point.symboliseIdioms = true;
Point works by surrounding each word in Point-enabled areas of a page within an HTML <span> element. For most pages, these <span>s cause no harm, but for some pages it may be desirable to remove these <span> elements when Point is not enabled. There are two Point configuration options in point_config.js that control this behaviour:
Point.spanifyOnLoad = false; Point.despanifyWhenDisabled = true;
Point.spanifyOnLoad controls whether Point should create its <span>s immediately after the page loads. If set to false and the Point is switched off (because the user has previously switched it off or not switched it on), no Point <span>s are created until the user switches Point on.
Point.despanifyWhenDisabled controls whether Point should remove its <span>s when Point is switched off. Setting this to true will have a slight impact on performance when the user switches Point off.
Point can be switched on and off using an access key. By default, this is set to "P". Access keys are built into browsers, and the actual keypresses required vary:
The access key used can be specified in point_config.js:
Point.accessKey = "W";
This may be a misconfigured proxy URL. The problem occurs if you use a fully qualified proxy URL in point_config.js, such as
Point.proxyUrl = "http://www.example.com/point/point.php";
This works fine so long as you browse to the site http://www.example.com/, but goes wrong if the site is accessible on different domains (www.example.com and example.com count as different domains) and you browse to the site via one of these alternative domains. The solution is to use a relative URL instead:
Point.proxyUrl = "/point/point.php";
This could be due to a number of issues:
Point.useFlashProxy = false;
If Point no longer works when you reload the page, the server proxy is broken. Follow the installation instruction that came with Point to get it working.
You can test your set-up on a Point-enabled page by adding #pointtest to the end of the URL and reloading the page. Point will test both proxies and report its results.
Point.useCloudFrontForSymbols = false;
There are a couple of potential causes for this:
*The most likely is that some content in the page is layered top of other content using the CSS z-index property and is obscuring the Point tooltips. This is easily fixed: the point.css file in the Point zip and uploaded to their server is supplied for the purpose of fixing up any problem Point may have in interacting with your site's CSS. You can edit this file and add a z-index declaration to the div.point_sym_tooltip rule at line 8 so that the top of the file looks something like:
border: 2px solid #ccc;
z-index: 1000; }
Point.useCloudFrontForSymbols = false;
One ASP.NET site using Poitn displayed a problem where the literal code of the proxy file was displayed rather than Point tooltips. The eventual solution was to use an .aspx file instead of an .ashx file. We now bundle both files in the ASP.NET version of Point, so if there is a problem with the .ashx file you can use the .aspx file instead.