Taking the YAHOO.ext.Domino.View idea further we could go on to add a whole framework with which we can take Notes client applications to the web. Easily.

We could start by defining an object that all the others extend:

var db = new YAHOO.ext.Domino.Database();

Now we can do things like:

alert( db.title + " is at " + db.path + " on " + db.server);

Or what about:

db.search("find me", { view:"AnotherViewName", fuzzy: true, max:250} );

On Monday I showed you a demo database that loaded a frameset-like layout using Jack Slocum's BorderLayout code. Then, using my own code, loaded a Notes view "on the fly". Taking this one step further we could go on to load the navigation element of the page with an Outline object.

var outline = new YAHOO.ext.Domino.Outline("OutlineName")
outline.render("ContainerID");

This would load JSON for the Outline using a ?ReadDesign method and the render() method would convert it to a tree-based set of links in the specified navigation area.

This would have us looking at something more like a Notes app. What else is there though? Well, Forms and documents. Like, obviously.

So, let's extend the database object with a Form:

var frm = new YAHOO.ext.Domino.Form("MyFormName");

Methods of this object could be .create() to open a blank one in a new tab and .validate() to call a ported version of my validator functionality.

Extending the Form object there could be a Document object.

var myDocument = new YAHOO.ext.Domino.Document()

Opened either from a Database method:

myDocument = db.getDocumentByUNID("UNID");

Or a View method:

myDocument = view.getDocumentByKey("UNID").open();

The .open() method of the document could be used to launch a tab and place the document in there. You could pass it parameters such as "view to use" (default "/0/") and whether to force edit mode.

Still on documents, consider the following code:

if (myDocument.isBeingEdited) {
        alert(myDocument.DocumentUNID + " is in edit mode already");
}else{
        myDocument.edit()
}

And this:

if (!myDocument){ 
        alert("Can't find the document") ;
} else {
        myDocument.delete( { prompt: "Are you sure?", backto: "/" } );
}

We could go even further and port my name picking widget and have it interface with the specified address book.

nab = new YAHOO.ext.Domino.AddressBook("names.nsf");
nab.ChooseName();

Other things we could add include a session object with a username property and a login/out method. What about @PickList and all the other nice-to-haves? The possibilities are almost endless.

Lots of this could turn out to be fanciful dreaming and just not possible with old stuck in its way Domino. It's all a challenge though and that's what I love about my choice in career — there's always something new and exciting round the corner.