if you know how to do xml transoformations in IE you should be able to understand the following snippet. it returns a text output that js can convert. the FF source is there too for comparison:

this.query=function(udef_xpath, udef_resultType){

var result=false;

if(!udef_resultType) var udef_resultType="string";

if( browser.isIE()==true ){

var tmpStyleSheet='';

var p=this.asXML();

var newXML=new erjXMLDocument( p );

newXML.loadXSLDocument( tmpStyleSheet );

var q=newXML.transform();

newXML=null;

switch(udef_resultType.toLowerCase()){

case "number":

result=parseFloat(q);

break;

case "bool":

result=( (q.indexOf("TRUE") > -1) || (q.indexOf("true") > -1) || (q.indexOf("1") > -1) ? true : false );

break;

default:

result=q;

break;

}

}else{

udef_resultType=( udef_resultType.toLowerCase().indexOf("number") > -1 ? XPathResult.NUMBER_TYPE : ( udef_resultType.toLowerCase().indexOf("bool") > -1 ? XPathResult.BOOLEAN_TYPE : XPathResult.STRING_TYPE ) );

result=xmlDocument.evaluate( udef_xpath, xmlDocument, null, udef_resultType, null);

switch(udef_resultType){

case XPathResult.NUMBER_TYPE:

result=result.numberValue;

break;

case XPathResult.BOOLEAN_TYPE:

result=result.booleanValue;

break;

default:

result=result.stringValue;

break;

}

}

return result;

}

--randall

Of related interest: XPather, https://addons.mozilla.org/firefox/1192/

It helps finding a XPath from the Web page.

Regards :)

{Link}

The guy there has built a handy js library that provides IE 5+ with the document.evaluate() method. The code (a single .js file) is release under GPL, you can download it from sourceforge.

I haven't played around with it yet, only tested the example html page that comes along with the code. Seems to work fine!

Jerry. There's some interesting XPath in the Linkify script (turns plain text links in to actual clickable links) which would give us something like this for finding the word "test" in a P (I think):

//text()[(parent::p) and contains(.,'test')]

Search highlighting is an interesting one. Hadn't thought of that. Codestore's search results don't use &highlight= because I use HTML for the view. GM could easily add this parameter back in. Another script could then do the actual highlighting (Domino won't do it as I am using PTHTML!). If only I had the time...

Unfortunately, the only useful ideas immediately coming to mind all revolve around variations of 'Mad-Libs' where I might use a regexp to look for certain words within p nodes and replace them with certain other words... actually, not useful, but amusing.

Come to think of it, a while back, Julian was workign on a text highlighting function that was intended to enhance domino search results pages to be more googlish (ala cache view). I played with that quite a bit on my own - it would make a great GreaseMonkey add on, extending Firefox's highlight to fuzzy search phrase - word highlighting.

It's a really nice way to integrate and process information between different systems.

In most cases you don't need spend big $ on a big "bloated" middleware product to share information between domino and other systems/technologies (unless the integration between the systems plays a major part and contains a complex set of rules and involves many systems in different flavours)

For 1 to 1 integration/communication, XML over HTTP or similar often solves the problem.