I've been using BX for ages and, naturally, am biased. But WinDig is obviously a great tool if you want to learn about your application as much as possible without breaking your fingers. It will save everything conveniently in a text file. In the end, you will find that each of these tools will something good for you! On 1/2/2009 1:24 AM, Geoff Chapman wrote: > Mighty scripters. > just wondering if any of you would care to comment on any user experiences > re strengths/weaknesses, pros/cons, easynesses/more difficultnesses between > these 4 application investigation tools in subject line above, for sussing > out how an application is behaving, with the view to taming it via > scripting? > i.e. in case of small subject screen area: > WinDig, bx, jls utilities, and homer? > > > like what do people reckon one can do, that, perhaps, the other cannot? > intuitiveness of interfaces? any comments welcome? > I'm just thinking it would really probly be good for me to dive in and learn > one of these investigative tools, but, just contemplating which one of the > above 4 I should start with? > > Authors may of course also rah rah about their own hard-sweated creations if > desired.<grin.> but obviously other user experiences/feedback would also be > most welcome > > thanks. > > geoff c. > > > __________ > Visit and contribute to The JAWS Script Repository http://jawsscripts.com > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts