hmm..
So -- ruby uses 'native' signals on win32 and perl rolls it own? Is that the
major issue?
Too bad.. it would be awfully nice to be able to 'borrow' any APIs that ruby
folks
write, and roll them up into CPAN.
Anyways, apparently HttpWatch has a generic COM interface (not a ruby-only)
hmm..
So -- ruby uses 'native' signals on win32 and perl rolls it own? Is that the
major issue?
Too bad.. it would be awfully nice to be able to 'borrow' any APIs that ruby
folks
write, and roll them up into CPAN.
Anyways, apparently HttpWatch has a generic COM interface (not a ruby-only)
On Fri, 10 Aug 2007, Ed S. Peschko wrote:
In particular, it looks like Win32::Setupsup and Win32::SAM are both sort of
orphaned modules that are fairly essential to controlling internet explorer in
a fine, granularized way (ie: firing up IE and populating both main windows
and closing
On Fri, Aug 10, 2007 at 09:39:46PM -0500, Randy Kobes wrote:
On Fri, 10 Aug 2007, Ed S. Peschko wrote:
In particular, it looks like Win32::Setupsup and Win32::SAM are both sort
of
orphaned modules that are fairly essential to controlling internet
explorer in
a fine, granularized way (ie:
On Fri, Aug 10, 2007 at 09:39:46PM -0500, Randy Kobes wrote:
On Fri, 10 Aug 2007, Ed S. Peschko wrote:
In particular, it looks like Win32::Setupsup and Win32::SAM are both sort
of
orphaned modules that are fairly essential to controlling internet
explorer in
a fine, granularized way (ie:
On Fri, 10 Aug 2007, Ed S. Peschko wrote:
In particular, it looks like Win32::Setupsup and Win32::SAM are both sort of
orphaned modules that are fairly essential to controlling internet explorer in
a fine, granularized way (ie: firing up IE and populating both main windows
and closing
