SNAPPS templates for Lotus Quickr available to download

 Dojo  10 Responses »
Jul 172007
 

It’s been nearly four months since IBM said “go” on the Lotus Quickr template project that you’ve read so much about on my and other blogs. Today, after an exhausting but very rewarding development cycle, we get to say “go” too. Code was complete June 29 (as promised to IBM), testing on Lotus Quickr Gold code was July 2-6, last week was CU and finishing the download system, and this weekend we put the final touches on and did a limited test with IBMers. Then yesterday we knocked out one last bug in the download system after flying to London for Collaboration University this week.

In these last months I and the team at SNAPPS had a lot of fun developing these templates. I learned new code and got to dig really deep into the Dojo Toolkit which, you know by now, I really like.

So after all that we’re happy to announce that the SNAPPS templates for Lotus Quickr are ready for you. Make absolutely sure you get the documentation, read it, and install and sign the prerequisite files. Then go have some fun!

I will continue posting on developing and digging deeper into both Lotus Quickr as well as the Dojo Toolkit code.

QuickrTemplates.com

Lotus Quickr Demo: QContacts

 Dojo, JavaScript  No Responses »
Jul 032007
 

For the ninth demo, QContacts, we are getting into some eye candy and heavy Dojo work. I showed you a preview of it in my post Embedded Domino forms with Ajax submit and JSON view refresh a couple of days back. From Rob Novak’s blog:

Contacts? Why would you need that when you have a member list? Good question, easy answer. You need more information than the member record can supply, or the project contact isn’t a member of the place, or you need to share role-specific information about this contact with the team. There’s nothing more frustrating than having an out-of-date, incomplete, or low-confidence contact list. QContacts help to solve these problems, centralizing contact information while automating much of the work involved in maintaining it.

The use case is simple. You’re running a project using Lotus Quickr, and you want to maintain a contact list with more comprehensive information than is available in the member list (which is, in fact, mostly for authorization). You also don’t want to re-enter information from the member list, and it makes no sense to duplicate information available about a contact that may be a member of another place, or not a member of a place at all. QContacts consists of a single form for the Lotus Quickr place, and a Domino database to coordinate, automate, and consolidate contact data. It lets you add information about people that can be shared across places including all pertinent addressing information, personal contact information, a photo, and place-specific comments that are kept in context even if the contact is a member of multiple contact lists.

Take a look at the QContacts demo.