Build Web groupware with QuickPlace
|New QuickPlace projects are a SNAP|
|Q uickPlace shows its greatest promise in leveraging the robust programmability of the underlying Domino architecture. The QuickPlace designers used Notes objectsfields, forms, templates, and databasesas building blocks for the QuickPlace architecture. QuickPlace objects map to their Domino counterparts: a Place equals a file directory, a room corresponds to a database, and a page can be looked at as a combination of a data note, a form, and one or more subforms. |
Similarly, security fields store information about who can read or modify the page, and workflow settings, such as what stage the document has reached, and who's next in line to review it. Domino developers can then add their own logic to further customize the workflow, such as putting a page in a certain folder based on a particular field value. As demonstrated in the listing shown here, you can write a LotusScript agent that processes a text file to add new members to a QuickPlace.
The QDK also provides instructions on creating and registering external command listeners that intercept QuickPlace server commands and perform custom work before or after the command is executed. For example, every time a create user command is sent with a new user name and password, the data could also be passed to a function that registers that member in an LDAP directory. These DLLs must be written in C++ for the first release, but other support will follow in Version 2.
QuickPlace scenes do much of the heavy lifting. They walk users through designing pages, routing documents, and adding users. If you want to collect additional information about users as they're registered, the QDK provides the information needed to modify or insert additional scenes as needed. But don't divert too many resources to using the QDK to extend the QuickPlace modelVersion 2 will expose similar technology through the UI to a browser, letting end users do some customization.
Page 5 of 5