RE: Re: Reading column values with LotusScript will be faster than either Erik C. Brooks 18.Aug.05 02:56 PM Lotus Notes Domino Designer 6.5.3Windows XP
I have rewritten about 60% of the report calculation code, but actually the example I gave was for shopper post-login information lookup. It used to be handled by an @DbLookup with their FullName, which scaled horribly due to the view size and reader's fields involved -- especially with this other bug I've uncovered.
They now authenticate as the UNID of their document (e.g. CN=12345678901234567890123456789012/O=Whatever). As a result, @Name([CN]; @Username) quickly allows you to get the UNID of the appropriate doc, allowing @GetDocField or a WQO NotesDocument.GetDocumentByUNID() access. MUCH faster.
The coolest Domino thing I've done recently, though, is this -- I've got an AJAX/DHTML solution that completely replaces the Java view applet. It works (and is in production) in IE 5.0+, FireFox 1.0+, and Netscape 6.1+. It's completely dynamic. It pulls down the view design XML on-the-fly, renders the data columns appropriately, allows drill-down, is completely CSS-enabled, etc. You can feed it all sorts of parameters like RestrictToCategory, show/hide selection margin, target frames/window handles, enable/disable "Starts with..." quick-goto-navigation, etc. The user can even select how many rows to display at a time and it's saved as a cookie for later use. You can have multiple views shown in one frame at a time, and nest them in tables quite nicely.
If IBM will add the few simple things I've asked for under the DXL/XML features thread it will be the ultimate view navigation tool over the web. Maybe they'd even want to buy it and include it in the core product? Who do I need to talk to about that? Ed? Are you reading this? :-)