|Latest 7 Posts
| Custom JSON Serialization With GSON|
Mon, Jan 23rd 2017 5
| Recapping 2016|
Mon, Jan 16th 2017 8
| Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 9
| Scripting Server Upgrades|
Fri, Nov 11th 2016 6
| Everything Old is New Again|
Mon, Oct 24th 2016 9
| Git Squash|
Thu, Oct 20th 2016 6
| MWLUG Success|
Wed, Aug 24th 2016 7
| Building Java Objects From JSON|
Thu, Jan 22nd 2015 24
| IoT and Raspberry Pi|
Fri, May 20th 2016 11
| Enhanced Editors|
Fri, May 27th 2016 11
| Git History Searching|
Tue, Jul 12th 2016 10
| Notes in 9: Docker + SonarQube|
Wed, Feb 24th 2016 9
| Eric and the Quest for More Coffee, pt.2|
Fri, Jul 15th 2016 9
| Everything Old is New Again|
Mon, Oct 24th 2016 9
| Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 9
| REST is Best|
Wed, Sep 17th 2014 8
| When You Need a Comparator|
Thu, Jan 8th 2015 8
||Fixing Dojo 1.6.1 in Domino 8.5.3
This all stems form an issue with Dojo less than 1.6.2 in Chrome 29 and any browser that used the same child node reference. This post specifically covers how to fix this (as it occurs with Domino 8.5.3) and get one of the most popular web standards compliant browsers back in the game with Domino and the ExtLib/UP1 controls.
Fixing Dojo 1.6.1 in Domino 8.5.3
I ran into a situation recently that required a bit of determination to fix. The BLUF: my implementation of the Dojo Enhanced DataGrid was breaking when applying the dojox.grid.enhanced.plugins.Filter due to an issue with the Dojo queries of elements rooted at the specified element. For example:
dojo.query('> *', dojo.byId('container'))
Thankfully, that doesn’t keep a good developer down.
Domino 9, 8.5.3 UP1, and my Woes
IBM Domino 9 brings a great many changes to the Domino server and has been fairly well received. Stuck, for now, with 8.5.3, I was at least able to get Upgrade Pack 1 applied, giving me the basic level of the majority of the same new controls.
That being said, I still had the controls I wanted to play with, so I still tried the “play at home” version of Brad Balassaitis’ excellent series on Dojo Grids in XPages. When I hit Part 14: Enhanced Filtering with No Coding, I found that the Filtering plugin would cause my control to break in a rather unexpected fashion.
Domino 8.5.3 has Dojo 1.6.1. The culprit in question, as I found out from attempting to use Chrome with the Enhanced Grid, the issue was with the child selector call.
After finding what the issue was, followed by some intense Google searching, I had found the fix for this in Dojo 1.6.2. The fix was small enough, I thought, “why can’t I implement this?” So I did.
Doing Something About It
Starting about Domino 8.5.3, the Dojo library inclusion migrated from the usual source path in datadominojsdojo-1.x.x folder structure on the file system to a JAR deployment. The 1.6.1 source can be found in osgisharedeclipsepluginscom.ibm.xsp.dojo_184.108.40.20631121-1400.jar. To begin, we need to extract the 1.6.1 source files out of the JAR, I recommend using 7zip, though any method of un-zipping the JAR will suffice. The folder structure is in the resourcesdojo-version directory. Extract that to the older format js directory in the Dominodata path and you now have a working version of the 1.6.1 Dojo library. I recommend giving your extract Dojo library a better name than my very boring 1.6.1.source; like .modified ;-)
2. Apply the Fix
Per the relevant commit in Dojo 1.6.2, which addressed this issue, we need to make our change to the dojo.js file in two locations. I recommend making a backup copy of:
You can see there are actually three files, one minified, one minified and gzip’d, and one un-minified. Per the description in the commit message, we need to find the root[childNodesName] references and replace them with root.children || root.childNodes, found in two locations. They specified two line numbers, but mine turned out to be lines 8644 and 8925. I’m chalking up the variance to our 1.6.1 version coming to us via IBM (I’m guessing comments). Since the lines we change are those directly dealing with our issue, the child dependency handling, I know we’re good. Save your file over the dojo.js.uncompressed.js file.
3. Apply Again
Now that the original, un-compressed version has its updates, it’s time for those minified and minified and gzip’d versions. If you’re using an editor like Notepad++, you can use a plugin such as JSTool to perform the JSMin operation.
Save that file over the dojo.js file. Now for the gzip’d version. With 7zip, you can perform a right-click on the dojo.js file and select 7zip > Add to Archive. For the settings, select the correct archive format, ensuring the .gz extension gets applied and overwrite the existing dojo.js.gz file.
4. Restart and Use
Now you only need to restart the Domino server and you can start using it. Just restarting the http task doesn’t quite do it, as Domino needs to fully re-register all its known libraries (not just re-initialize the handling of http connections). If you don’t, but you set the library in the Xsp Properties, you will not be able to load your new version, as the selected library will return a runtime error, as the server hasn’t registered it yet.
To use it in an NSF, open the Xsp Properties file and specify your modified name in the Dojo version field. If you prefer the source, it’s applied by xsp.client.script.dojo.version=1.6.1.modified (or .source, whichever you call it). Note to leave off the dojo- prefix.
You are now able to use the Dojo Enhanced DataGrid with the dojox.grid.enhanced.plugins.Filter!
Sep 02, 2014
| Recent Blog Posts
Custom JSON Serialization With GSON|
Mon, Jan 23rd 2017 2:00p Eric McCormick
Mon, Jan 16th 2017 3:00p Eric McCormick
Per usual, I’ve had a little break between things and decided to catch up with a bit of a summary of some recent things that each didn’t necessitate their own post.
2017 IBM Champion
For starters, I’m honored to be named an IBM Champion in Collaboration Solutions (/ Social Business) for the third time. This would be a hat trick in (ice) hockey 🏒. I’m happy to be recognized with a group of people, developers and more, who are passionate about both their work and the plat
Rebirth: An App of Ice and Fire|
Wed, Dec 14th 2016 4:00p Eric McCormick
If you read my blog for any of the Saga of Servlets series, then I hope that you’re excited I’m returning to the application I put together for it. This time, it’s as a conversation piece in regards to some of the build process modernization I engaged in recently, in order to unify the code base in its git repository. In any case, it’s helping pave the way forward before I update some of the back-end elements, when it will again be a talking point for some additional rework and
Scripting Server Upgrades|
Fri, Nov 11th 2016 2:00p Eric McCormick
This one might be slight departure from my usual, but those that have followed my blogging this past year will have noticed a bit more of a leaning towards DevOps in some of my posts. This echoes a lot of what I’ve been concluding as increasingly a necessary part of development; that we need to consider a picture large enough to encompass the themes surrounding development functions and, like any good developer (DRY ~= “lazy”), automate the heck out of it.
I had p
Everything Old is New Again|
Mon, Oct 24th 2016 8:00p Eric McCormick
Every so often, it’s good to reassess one’s position. This is good from both a standpoint of being inquisitive and even interrogative, but when it comes to the ever changing landscape of the front-end development space, it’s not only inevitable, but must be embraced for what feels the need to “stay afloat”. I’m changing theme of my blog, hopefully for the better. The previous theme was good and did a great job of getting things started, but while I had forked a copy of a good
Thu, Oct 20th 2016 8:00a Eric McCormick
If you’re just here to learn a little about how to “squash” commits with git, skip down a ways. Otherwise, hold on, and I will catch you up on a couple of personal notes before we get there.
On the Blog
It’s been a little while since I blogged last. This has been due to a combination of reasons; specifically, I’ve been busy with:
my family, it was the end of summer with lots of things going on
a number of projects around the house (a deck removal and basement remodel
Wed, Aug 24th 2016 8:37a Eric McCormick
MWLUG was a great success as far as I’m concerned. Each time I’ve gone I’ve had the great enjoyment of being able to attend some high quality sessions, meet with lots of colleagues and friends from the community, and get a view into products and solutions many people are undertaking, over conversations and interactions outside of the sessions. This is always a great way of interacting with others who were able to make it. Unlike the IBM conference of Connect(EDsphere), this is purel
Manually Renewing HTTPS w/ Let's Encrypt|
Wed, Jul 27th 2016 10:40a Eric McCormick
A while back, I rolled a personal project, which is a Node app, to Bluemix for lightweight use. I managed to make use of Let’s Encrypt for the HTTPS certificate, but only after realizing that there was a bit of a manual aspect to it that is the antithesis of an automated script for such things. Ultimately, after finding some information in a blog post form Marky Roden (of all people), I was able to get moving. The only downside wound up being that time passed, and it came time to renew
Eric and the Quest for More Coffee, pt.2|
Fri, Jul 15th 2016 4:17p Eric McCormick
Posted in the “aside” category.
There were three submissions via the Google Form, and a couple more form messages via social media. Honestly, I had debated either a nondescript or far more overt mug w/ the likeness of one of the more iconic of H.P. Lovecraft’s imaginations, but this seemed a bit over the top.
a replacement for my alma matter
a Go Army, Beat Navy mug (which was never my thing)
this gem from shop.Scotch.io (again, pretty overt)
Git History Searching|
Tue, Jul 12th 2016 10:00a Eric McCormick
First, A Shout-Out
The recording of the session called “Normalizing XPages Web Development” that Shean P. McManus and I gave at the 2-day, virtual ICONUS (formerly IamLUG) event this year is now available from “Archive and Replays”. If you missed it, I recommend checking it out, it’s a great benefit of ICONUS and I hope that those who did get a chance to attend enjoyed the subject material. We covered a lot of ground and were able to demonstrate what is, in my opinion, one of the grea