The Original

The stock XPages date picker control leaves more room for user error than I prefer. Mark Roden originally came up with this excellent script in jQuery. I love jQuery, but it’s not the (client-side) JS library I always have available to me in my XPages work, and I’m not about to load yet another library after Dojo in an existing, Dojo-centric application for a comparatively trivial, one-off function. Since the function can be written in vanilla JS, or any decent JS library, I decided to re-write it into Dojo.

The Dojo Version

I have this in production on a few applications, and both I and the users love it. So once again, I’m glad to be privy to the fruits of a great community of fellow XPage developers. They’ve made my life easier on so many occasions and I’m hoping I can give back in a small way. Now, since I’m using Dojo, apparently this can be achieved in more-or-less the same way with the dijit.form.DateTextBox Dojo module (just set the field’s DojoType after specifying the resource), as highlighted in the comments on Mark Roden’s blog post. While this is certainly functional, it does achieve the picker launch on entering the field, it isn’t consistent with the native XPages date picker control, which is already all over every single XPage’d application in my company. So, for consistency and UX as decided by others in my organization, I rolled this Dojo version of Mark Roden’s script.

Here’s the gist:

Breaking It Down

We bootstrap the function via the dojo addOnLoad call and start by creating an array of the fields with an ID attribute containing ‘_Container’ and the class xspInputFieldDateTimePicker. We then iterate over these DOM nodes, getting a handle on their button, and connecting the click() event call for that button to the respective field during the onfocus and/or onkeypress events. I’m sure a more advanced user could improve the performance of my version of the function, and I welcome them to post a forked version; after all, why use GitHub/Gist if you don’t want your code improved via the aid of others?

Note, for this to work in Dojo 1.8, the dojo.connect and dojo.query calls I establish, which work perfectly fine in 1.6, must be converted to dojo.on and query calls, respectively. For more, I do recommend reading the Usage section of the Dojo 1.8 docs.

Eric McCormick

Software Developer, for the web, full-stack, Node virtuoso, git master, Docker acolyte, DevOps neophyte, IBM Champion.

edm00se edm00se

Disqus Comments