Skip to main content
    Country/region select      Terms of use
     Home      Products      Services & solutions      Support & downloads      My account     

developerWorks  >  Lotus  >  Forums & community  >  Best Practice Makes Perfect

Best Practice Makes Perfect

A collaboration with Domino developers about how to do it and how to get it right in Domino

So, I don't know. A few weeks back I posted this Design Element Search tool to the sandbox. I think it's pretty useful, but there's been just one comment posted about it, so I wonder whether people are finding it useful.
I've been enhancing it some, as shown by the screenshot below, and in the porcess of teaching it to interpret static text on forms, I did a state machine built on the SAX parser. The state is based on which routines are currently registered to handle the different events, so as to minimize the amount of LotusScript code that executes at each step. I hope this will make it faster than if I had fewer but more complex routines that I leave as the event handlers all the time.
Are people using this tool, or have you tried it, and if so, what does it need to make it more useful? Should I bother to post "version 2.0" to the Sandbox?
I personally have been having a blast searching the designs of our internal apps for GetNthDocument and NoCache and other such performance reducing code.
Design Element Search dialog, improved.

Andre Guirard | 17 July 2007 11:20:30 PM ET | Plymouth, MN, USA | Comments (19)

Search this blog 


    About IBM Privacy Contact