My Blackberry Enterprise Server Push Utility for the Lotus Notes Client, allows you to create Jobs for individual Channel, Message, and Browser Content Pushes, as well as allows you to delete Pushed Channel Icons from defined recipient devices.
Blogger, podcaster, writer, and geek Chris Toohey covers topics from application development to the latest must-have-gadgets.
More on Mailer...
More on Junction Lite...
More on Remote Console...
More on Controller API Utility...
Products & Applications
The idea is simple. At the start of your day - upon completion of your first task - create an entry highlighting what you did and whether you feel it was an efficient or inefficient use of your time. Based on several requests, you can also select the priority, apply categories, or even align your time against a project.
For Lotus Notes Client v8.0 and above, you can use the Time Tracker Widget to make this process even easier!
My Configuration-based Rich Text Mail Merge and Emailing Utility, Zephyr allows you to create rich, data-driven emails to support automated workflow - all via Microsoft Word Mail Merge-like architecture. Dear <firstname> allows you to personalize each email message not only to the individual recipient, but also to the individual application workflow event!
xCopy is a simple configurable xCopy client for the Lotus Notes client. By creating and defining xCopy Profiles, you can batch process your file backup or remote upload jobs. With the addition of the xCopy sidebar widget, you can easily kick-off these jobs, and modify both the xCopy Profiles and xCopy itself.
Community & Resources
The Lotus Technical Information & Education community is comprised of IBM, business partner, and customer subject matter experts who use product wikis, published articles, white papers, community blogs and the latest in social media to build and share high quality technical content.
OpenNTF is devoted to enabling groups of individuals all over the world to collaborate on IBM Lotus Notes/Domino applications and release them as open source.
Share your deployment experiences and best practices in our wikis and help IBM to create scenarios for successful deployments. Contribute to the community by collaborating on shared content and leverage the shared knowledge from that community.
XPages Resources via Themes or Custom Controls?
06/27/2012 02:34:00 PM by Chris Toohey
I've been pondering the following question for quite a while, and wondering if anyone else has some insight into what exactly a Best Practice would be:
To give you more information before you gut-check respond "Themes!", here's what I'm getting at...
The majority of the multiple-client XPages-based applications that I write use a technique that I first saw employed by Declan, as I'm a big fan of creating client-specific user interfaces and thus client-specific user experiences. The technique uses a core
xp:include Control with a computed
pageName property based on the UserAgent (which itself reports the client type). Basically, if I want a Home.xsp page for a web browser and an iPhone, I'll create 3 XPages: Home.xsp (which is blank, save for the
xp:include), and a Home_browser.xsp and Home_iphone.xsp which I load based on the reported UserAgent. All of the device-specific UI/UX is contained within the included XPage.
A benefit to this technique is to allow me to easily test a given XPage on a given client via a direct URL (eg., "Home_screen.xsp").
As I typically do, I'll create a layout Custom Control for my XPages application. Combining this technique, there is a
layout_screen.xsp and a
layout_iphone.xsp Custom Control, which are designed to be used in each "_browser" and "_iphone" XPage I need.
(Another aside, I often have a "_browserOLD" layout Custom Control and set of XPages to handle IE6/7/...8.)
Traditionally, I've used Themes (both at the Domino server level and in-NSF) to handle any Resource inclusion... but maintaining those Themes, their rendered logic, et al can be extremely tedious.
Lately, I've been including any Resources directly in my layout Custom Controls with great success. Since these controls are included in every page (specific to the device), I can better simplify the rendered logic... and quite frankly, it helps having things more easily surfaced in the layout controls when you return to update an XPages app 6 months since you've last touched it.
Themes still play a large role in my development and maintenance of these applications, mind you, but ironically not in the role that I feel most developers use them: they act more "globally", setting values on XPages (eg.,
createForm="false") and on individual "common" controls. And, of course, they manage styleClasses and other properties for various controls.
... I'm just not using them to include a Stylesheet anymore.
So what's your experience with including Resources? Using Themes or Custom Controls? Share in the comments below, and maybe we'll establish a true Best Practice!