Notes/Domino XPages Development Forum - Re: Setting dojo version at application level

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

~Karl Kigerosterikle

Feb 23, 2011, 6:17 PM

122 Posts

Re: Setting dojo version at application level

Category: Dojo and Client Side JavaScript
Platform: All
Release: 8.5.2
Role: Developer,Administrator
Tags: Dojo,Runtime
Replies: 3

Just to follow up, for Lotusphere I tried using xsp.properties in the nsf. That didn't work. I also extending djConfig by using the 8.5.2 xp:head tag, again it didn't work.

I noticed xspClientDojo always gets loaded, regardless of dojoParseOnLoad settings. So effectively the Xsp Command Manager needs to load xspClientDojo in order to handle partial refreshes, typeahead etc. So it looks like there's something in there to load the relevant server version. That happens before the code in your nsf or XPage runs, so overrides any dojo version settings.

I spoke to Paul Hannan at the time, but in the lead-up to Lotusphere everything was manic. I'll see if there's an update, but I wouldn't expect it to be feasible in 8.5.2, I can imagine it being a big job to expose the functionality, though I appreciate the requirement.

If it's individual dojo modules you MAY be able to reproduce the functionality in a previous version of Dojo by extending relevant modules, but that may or may not be possible, depending on the functionality.

~Dean Umjipychekoopsi

Feb 23, 2011, 7:51 PM

40 Posts

Re: Setting dojo version at application level

You can do it, but you basically have to tell domino to not use any of the dojo code by setting xsp.client.scriptlibraries=none in your xsp.properties file, then you have to mimic everything domino loads (including dojo and the xsp class) through the use of themes and csjs. Mimic it exactly (ie run what they say when they do) and you can get it to work. This would only work for going backwards in versions... if you go forward, Domino will load the latest version for everything not just the "official version" ... Dojo provides pretty decent forward compatibility. If you need to reference specific files in your dojo build, ie dojox css or something you can avoid hardcoding the dojo version in the path using /.imbxspres/dojoroot/dojox/... and that will reference the current version for future compatibility. I'd try to avoid referencing version specific things otherwise.