In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (David Cantrell) wrote:
> It matters not that he wrote Mac::Glue. He's published it, so I can use it > too. And I have just as much difficulty with using Mac::Glue as I do with > using Applescript. That difficulty is solely because Applescript and all > its trappings like the events and methods and stuff* that applications > expose, and how to call them, is so piss-poorly documented that it may as > well not be documented at all. > > * - so badly documented that I don't even know what the correct terminology > is Yeah, the majority of problems I have in Mac::Glue are as you say. The reason I sometimes test in AppleScript is not because it is easier, but because feedback is more immediate when I am trying to figure out why an app is not responding as I think it should. It's really a giant PITA, but it is mostly the fault of the design of Apple events, or the design of a given app, and not something either tool really makes that much easier. Speaking of documentation, something new with Mac OS X's Mac::Glue is gluedoc, a perldoc wrapper: % gluedoc Finder Tells you all the events, classes, etc. for the Finder. Those glue PODs were created for Mac OS version too, but now are more easily accessible. gluedoc -h for more info. -- Chris Nandor [EMAIL PROTECTED] http://pudge.net/ Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
