Re: Domino (was List Archive Availability)

[email protected] wrote on 14/04/2004 01:04:33 PM:

> 
> Hi Andrew - I was right then that netWindows would be of interest to
> Domino developers :-)  I don't see that many of us around the net 
> (outside of Domino specific sites) - but I think the kind of 
> framework behind something like netWindows would appeal to us 
> because we know how much rich-client functionality we are missing 
> when we move from doing Notes apps to web apps. 

Oh yeah, face it, Domino standard HTML really sucks. But there's no reason 
not to plug a Notes back end-app to a smart web interface.

> I'd come across that some time ago, but it using XSLT and 
> not being cross-browser (there goes those principles again!), I 
> shied away from it. 

Cross-browserable is always a requirement for me. Yeah that project is not 
CB, but it illustrates a good domino concept. As for cross browser stuff 
netwindows is CB, and there are lots of other XML/XSL libraries that are 
too. I recently discovered Sarissa for CB XML documents, XSL 
transformation and XPath. https://sourceforge.net/projects/sarissa/

> The problem with ReadViewEntries (as I understand it) is just 
> produces a generic XML representation of the view's structure.

Yes that's right, but it doesn't mean it's unusable, it just needs some 
processing. Each row is a <viewentry/> containing <entrydata/> elements 
matching the columns. Each element contains attributes that explain what 
it is, if it's expandable and so on.

The openntf project contains a generic $$ViewTemplateDefault form which 
takes normal ?OpenView urls, changes them with JS to ?ReadViewEntries urls 
and renders teh XML using XSLT, it's pretty clever. It also shows a way to 
simulate a @DbLookup function in JS using ?ReadViewEntries and the '&
StartKey=xxxx' &   '&UntilKey=xxx' query strings arguments.

> Indeed, I think I would still be back to the problem of closing tags
> in a response hierarchy with any other XML representation of the 
> view.

I know what you mean. I've pulled all sorts of hacks to get around this 
problem. For example embed the view (with the first column categorised) in 
a page, in the view for the categorising column write a closing tag + an 
opening tag for your xml, then add a single opening tag above the embedded 
view and a single closing tag below the embedded view then in you JS ignor 
the empty categories.... YIKES! it's rather bad. BUT how about this: 
ignore the requirements of Notes and let JS sort out the XML. Make a view 
with 1 column, all the XML for each document is created in that column. If 
you need a response hierarchy then make sure you create XML that would 
identify the docs' parents' IDs. Once JS has imported the XML it can then 
sort out the hierarchy for you. Then you don't need to worry about closing 
tags for categories!

> When I get this working in a way that is generic I am aiming to 
> bring it to the attention of sites like codestore, notestips and 
> openNTF.  I've learned so much from those people, I'm itching to be 
> able to give something back.

Good luck!
 
> Bernard
Cheers,
Andrew Tetlaw

Bligh Voller Nield
http://www.bvn.com.au
p: (07) 3251 5778
f: (07) 3852 2544


<font face="Arial, Helvetica, sans-serif" size="2">
<b>
Please Note
</b>This document, including attachments, is only intended for the addressees and may contain privileged or confidential information. Unauthorised use, copying or distribution of the document or any part of its contents, is prohibited. If you receive this Email in error please notify us by return Email or telephone. We will reimburse you for any reasonable expenses incurred in meeting this request.</font> 


_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org