Bret Pettichord wrote:
I just installed Ruby 182-15 and then Watir 1.4 and did
not have any problems. All the unit tests (but the three frame tests --
a known issue) ran without problem. I did not need to add require
'rubygems'. I'm pretty sure that Fox was a gem in 182-14 as well.
The second problem cited below, regarding LoadLibrary not working when
there are spaces, would not be a Watir problem. But a Ruby problem. If
someone wants to track this down, they should report it to the Ruby
Installer team. If we confirm this doesn't work, i suppose we could
update our install docs.
For a while now, installing Ruby sets environment variable RUBYOPT to
rubygems. If someone did not have administrator privileges then they
would not get this setting and i could imagine that they would run into
problems like those detailed below.
* You must install as administrator on Windows NT,
2000, and XP in order for path and environment
variable settings to take effect.
So far, i haven't taken the time to understand how Ruby and Watir work
in a non-administrator environment and haven't taken the time to
support it. I see that this is not documented in the readme, so i can
update that. If someone wants to investigate running watir and ruby in
a non-admin environment and give a detailed report as to whether it can
be made to work, that would be appreciated. Do we want to support this
kind of environment? Wouldn't this mean that ruby would not be in your
path? Sounds like a headache to me.
Several people have suggested that we replace our current Watir
installer with a nullsoft installer (in addition to creating a Gem). I
think that's the general direction i'd like to move, rather than try to
bulletproof our current installer (which is admitedly shaky).
If there are more reports of problems, i would like to see them. Actual
error messages and details as to exactly when they occur would be
extremely helpful.
Bret
P.S. Since i teach classes on effective bug reporting, i thought i
might cite the second report below as a particular good example of a
common mistake than many people make in their bug reports. It is vague
on specifics around the actual error message ("or something to that
effect") and long on guesses as to what the source of the problem might
be.
At 10:32 PM 8/18/2005, Jeff Wood wrote:
Jonathan Kohl wrote:
I am getting some emails reporting a couple
of issues. The first is from folks trying to install Watir with Ruby
182-15. They get an error message about the installer not being able to
find Fox. Looks like Fox is now installed as a Gem, so one must also
require rubygems in the installer. We should figure out a way to clean
this up; I'm wondering how many new users are running into this, not
telling us and moving on in frustration.
Here are two issues that were last emailed to me:
I installed the 182-15 one-click Ruby build to start. When I tried to
install watir using install.rb, the install failed because the Fox gui
libraries couldn't be found. This seems likely to be a problem with the
ruby installation not working correctly. The installer mentioned
something about running a "command line" version of the installer, but
it wasn't obvious where that might be and your documentation didn't
mention anything about it either. So, I figured that 182-15 was shot
just like 182-13 is. :)
- After downloading and installing 182-14, I was able to get the watir
installer to start up and run. However, during the installation, I got
a dialog saying that a LoadLibrary("c:\Programs") failed (or something
to that effect). This is because I installed Ruby in "C:\Program
Files\Ruby" and watir in "C:\Program Files\Ruby\watir" initially (since
I don't like to clutter up C:\ and D:\). I'm guessing that the load
library call can't handle the space in the directory name. This could
be a watir install problem (improper string quoting/escaping) or a ruby
load library problem I guess.
These have been popping up on the email list as well lately. Any
thoughts or ideas on fixes?
Thanks;
-Jonathan
_______________________________________________
Wtr-general mailing list
<mailto:[email protected]>[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
The problem is quite easy to fix, simply add require 'rubygems' right
before the require 'fox' line.... Everything works from there.
j.
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
_____________________
Bret Pettichord
www.pettichord.com
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
BTW ... regarding the require
'rubygems' line ... it doesn't hurt anything to put it there ... and
some people don't have the possibility of running as Administrator.
Simply adding that line fixes the problem... I wish you'd reconsider it.
j.
|
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
