Showtime
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.
Contact Information
Blogger, podcaster, writer, and geek Chris Toohey covers topics from application development to the latest must-have-gadgets.
dominoGuru.com on Facebook
Latest Updates
Products & Applications
Time Tracker
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!
Zephyr
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
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
Lotus Technical Information & Education Community
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.org - Open Source Community for Lotus Notes Domino
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.
developerWorks Lotus : Wikis
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.
Domino Blog Template Update - Revised Architecture v0.01a
05/19/2008 12:07:29 AM by Chris Toohey
After many conversations with people like Nathan, Declan, and my soon-to-be-mentioned co-author on this project (which will be open source and available to the community - it's all about the show!) - I realized that I was taking the wrong approach with thinking that Web Services could do what I needed it to do. What I need to do, for the content management system that I have in mind, is facilitate the ATOM Publishing Protocol (or APP) via REST - that's full support of the POST, GET, PUT, and DELETE methods.
This of course, we know that the Domino HTTP Server won't allow - and now I know that this includes no matter what you say in the Internet Site Document.
I tested this by creating a simple HTML file, consisting of 4 Form objects - each with the POST, GET, PUT, and DELETE methods respectively - that used an Agent Design Element as their posting agent. The Agent Design Element, called "rest_test" for my examples, would simply run a session and return the submission method and some other information via plain text Printing.
The result - well, POST worked fine. GET worked fine. PUT and DELETE were translated to GET method calls. Now, the translation wouldn't bother me so much... but it's seamless. Too seamless. I don't know that the original request was via PUT/DELETE. If you consider what this means...
PUT and DELETE are methods that are designed to modify their target object - update and removal respectively. Such requests are returned as GET - which is designed to fetch an object. Sure, data can be passed along to that object (to Domino developers, think ?EditDocument, ?OpenAgent, QueryString parameters, et al). But that ain't gonna work for what I'm looking to do.
So, after many discussions with my co-author, I think we've got a plan. It's a solid plan. It's a righteous plan. And it's something that will invariably allow extended functionality far beyond the scope of "yet another Domino Blogging template". We're going to a full-on, true REST-compliant content management engine.
More details to follow...
|
Unless otherwise stated, this work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License. |
So you decided to give it a rest? Good idea. And remember, there's no rest for the wicked so I'm glad to hear your plan is righteous.
Peace,
Rob:-]