Re: Modifying DOM before netWindows tree widget created.

Hi Michael

Thanks for your suggestions.  I'm ashamed to say they were too elaborate for me :-)  I tried to understand them, and to search The Manual and the scripts themselves to see if I could understand them.  Luckily I saved myself the embarassment of having to ask you to explain them in more detail.  I re-read the manual, and realised that I had lost sight of when it was that nw gets called.  I then realised that my document was being rendered into a tree widget before my manipulation was performed. By calling my document manipulation at the end of the page (so before onLoad), it works beautifully.  Now on to your other point...

>>
This seems like a lot of work to do, 
especially if your discussion hierarchy is really large. My first 
thought is that you should really try and find a way to massage the 
Domino data outside of the browser
<<

I realise that re-structuring the document in the browser might be unworkable for large documents.  The other Domino user (Andrew) did initially suggest producing the requisite nw structure using XSL, but I'm loathe to do that because it means learning XSLT (which looks quite complex).  There are other programmatic approaches I could take on the server (such as a kinda cgi in Domino, or using a Java servlet).  I am trying to avoid this (initially) because Domino views are optmized in their responsiveness, and to restructure the data that way would be to add a delay and some extra load on the server.  Provided it is bearable, it seems more logical to me to offload this re-processing of the view to the browser [I really do subscribe to the netWindows philosophy here!]  If there is a significant delay in rendering the page, I can tune the size of the chunks in which the response hierarchy i
 s sent to the browser (Domino views are addressable in that manner). The users will  make a lot fewer trips to the server than they currently would using the normal Domino HTML rendering of the data, so it is just a question of how large the chunks can be before it becomes noticeably a slow on the client.  This still seems to me more rational than having the server continually programmatically re-structuring the view output.

As I understand that Alex is the one who works on this widget, I'm including some more details about speed differences in my response to him.

Again, thanks for your help - netWindows does some really cool things.  This is my first web application, and not being able to do this kind of stuff was driving me crazy.

Regards
Bernard

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