Oh. Thanks for that. I was under the impression that even if you
packaged the app that shoes still needed to be installed on the
target machine. So just to make sure I understand, what you are
saying is that the target machines (say Windows) don't need Shoes
installed if on my development machine (OSX) I package up my app,
clicking the 'Include Shoes' option, and that _my_ (OSX) Shoes
installation (the one with Mechanize hacked in) would be included in
the package for Windows? Is that correct?
DZ
On Oct 29, 2008, at 1:19 PM, Jason Porter wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Oct 29, 2008 at 12:03, Daniel Zepeda <[EMAIL PROTECTED]> wrote:
I've got around my Mechanize problem for now by copying the
appropriate
files/directories from a standard ruby installation with the gem
installed
directly into the ruby distribution inside of Shoes. Obviously
this is a
short-term fix, and prevents wide distribution of any app that
depends on
this method, but for now this might work for you as well.
I did the same thing on my little trial of Mechanize. If you package
up your Shoes app and distribute the package (any of them, exe, dmg,
shy, etc) it should work. Granted, it's not as clean or sexy as using
the gem but it does work. I downloaded Ruby to a Windows VM and
installed the Mechanize gem just fine using the gem command. I did
this to see if it was just a windows problem, but it seems to be
related to Shoes and how Shoes is handling gems.
- --
Jason Porter
Real Programmers think better when playing Adventure or Rogue.
PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: http://getfiregpg.org
iEYEARECAAYFAkkIqTIACgkQEEbDm5Jsz/UGCwCg4UGPGMXC9cfyCqE4naZM90lH
BowAoOA10p22qPbLpldM598rqFIPmlwV
=O9j7
-----END PGP SIGNATURE-----
