Thanks for the feedback. I will use
Win32::Automate::app
and I encourage others to use the same pattern in the future.
Chris
On Thursday, April 22, 2004, at 06:56 PM, Gabor Szabo wrote:
The Win32:: namspace is also quite established to applications
specific to
that platform so if the
The Win32:: namspace is also quite established to applications specific to
that platform so if the underlying application is Windows specific
I think using Win32:: would be a good idea.
I'd understand more something like Win32::Automate::app or
Win32::Drive::app.
less than 2c.
Gabor
Authors,
Using the handy Win32::GuiTest module, I'm automating control of a
particular Windows application which lacks a specific command line or
scriptable interface. (We're still unclear on licensing issues, so
forgive for simply calling it app instead of it's real name) What
sort of
Alternatively, it could simply be app::Mechanize, but that creates a
new top-level space for every application, which I'd like to avoid.
Also note that WWW::Mechanize has a pretty established mindshare in the
web app side of things. Might be confusing, or not.
xoa
--
Andy Lester = [EMAIL
