Sorry for the delay in replying back, been busy developing with Shoes.
Responses below
On Wed, Dec 10, 2008 at 11:14 PM, _why <[email protected]> wrote:

>
> Would it help if I borrowed IE's proxy settings if HTTP_PROXY isn't
> defined? You see, I already had it in mind to do that. Or would I
> need to parse the PAC myself?
>

In this instance, yes it would certainly help me, but I might just be an
oddball case, so if the consensus was use the HTTP_PROXY environment
variable then so be it.

As to whether you'd have to parse the PAC file yourself, I'm afraid I'm too
ignorant to help you there. I would hazard a guess as to 'yes', in which
case this is seeming like a lot of work just to solve my problem.

On Wed, Dec 10, 2008 at 3:53 PM, Seth Thomas Rasmussen <
[email protected]> wrote:

>
> It could be nice to automate this. In the meantime you can `gem
> unpack` into your project directory and just use require instead of
> Shoes.setup.
>


Well, I've been trying this (partly why I'm so late in replying). From a
blog post I read:

http://blog.jayfields.com/2006/11/rubygems-absolute-paths.html

It seems this should work, but in my case because I'm using mechanize, it
doesn't. I.e. I can do:

> require './mechanize-0.8.5/lib/mechanize.rb'

but then this file itself has a require

> require 'www/mechanize'

which it then fails to find. I could manually change the paths in the gem -
but I don't think I will!

On Wed, Dec 10, 2008 at 6:35 PM, _why <[email protected]> wrote:

>
> I think the way I'll do it is to download all of the gems for a
> specific version and package those up with the app. So
> html-scraper.shy will include all the different platform gems.
> Before launch, it'll treat the collection of gems as a local
> repository.
>
> In the case of an EXE, it'll probably only include the gem for that
> platform, unless the user indicates otherwise. (And same for OS X
> and Linux packages.)
>
> _why
>

This kind of approach would be great for me.


Many thanks all,

Si

Simon Heywood
Super Up North, UK
i-5-m.net

Reply via email to