This is the 3rd article in the introduction to the Domino Facelift. The first article's here if you need to start from the beginning.

Let's recap:

• we can get the DXL for a form and find more properties to reveal to the browser.
• we can turn that DXL information into a series of javascript calls
• we can create a javascript library of functions that provide implementations for those calls (such as a date picker)

But how do we get the function calls we create from steps 1 and 2 to the browser so that they can execute the implementations of step 3? That's what we'll talk about now.

Read More . . .
(100)

Now that Lotusphere is complete, it's time for some detailed explanations of the Domino Facelift. While Dwight and I were thrilled that a number of people "got it" and validated the concept, we're also disappointed in ourselves as there were many who didn't get it or failed to see the value in it. Here's the start on a series of articles and screencams to really go through it point by point.

Please remember, this is a framework that is being contributed to the community. This is not a "product in development". Yes, we hope to capitalize on this framework, but from the perspective of making it faster for us to accomplish things for our clients in our own consulting engagements, not from "selling" it. By extension, if it makes things faster and easier for us, and it's available to everybody to build upon, then others can also benefit and everyone should be happy

What is the Domino Facelift? The driving goal of the framework is to provide a consistent toolset that makes Forms and Views observe and use the properties specified in the Notes Designer. If a property is implemented by the Notes client, why shouldn't it also be implemented by the browser client. If there is a rich UI experience in the Notes client, why shouldn't there also be a rich experience in the browser.

Read More . . .
(2)

This is the 2nd article in the introduction to the Domino Facelift. The first article's here (updated link) if you need to start from the beginning.

Now that you've got the idea of what we're trying to accomplish with Facelift, let's move on to talk about Forms and how the framework addresses them. There are a LOT of properties in Form design that the Domino web engine doesn't recognize and render to the browser. Some examples:

• Date field: calendar picker
• Date field: selection of date only, time only, or date and time
• Names field: Address picker
• Dialog: Allow values not in list
• Dialog: Use View to select choices, Use ACL to select choices
• Number field: right justification of data
• Number field: numeric data provided
• All fields: width
• All fields: help description

There are many, many more. I'll get Dwight to provide a more complete list. What are your choices as a Notes developer for dealing with this?

Read More . . .
(5)

Here it is, its not pretty, but its here!

The image uploading on the FCKEditor is all messed up, the resizing web query save is not working.  It needs to be signed under unrestricted access and probably should have some type of handling for failed agent run
Sample Database is here

(0)