Awesome advice, Jarmo. Thank you so much for getting me past that
problem! On to the next hurdle, which I will post in a separate thread.
Thanks again!
Liz
On Thursday, November 28, 2013 12:52:43 AM UTC-6, Jarmo Pertman wrote:
> Hi!
>
> The problem is with current version (1.9.3) of ffi gem.
Hi!
The problem is with current version (1.9.3) of ffi gem. Downgrade it to
1.9.0.
Jarmo Pertman
-
IT does really matter - http://itreallymatters.net
On Monday, November 25, 2013 6:31:31 PM UTC+2, Liz Goodson wrote:
>
> I am doing a feasibility study on using watir classic to automate our
I would also strongly recommend log4r gem as it is really good tool for
logging.It has really nice outputter types and log levels.
http://log4r.rubyforge.org/manual.html
--
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@google
Might be worth looking at the standard ruby logger instead of trying to
reinvent it as well?
http://www.ruby-doc.org/stdlib-1.9.3/libdoc/logger/rdoc/Logger.html
On Wednesday, March 6, 2013 2:06:36 PM UTC-5, Chuck van der Linden wrote:
>
> I think this is your first clue *"warning: already initi
I think this is your first clue *"warning: already initialized constant
LogApp "*
Ruby expects anything you define starting with an upper-case character to
be a constant, and it is complaining that you are re-initializing or
changing the value of LogApp after it has been defined.
trying refac
Could you put more information?
Your OS, fileutil gem version and etc
Have you tried different ruby and gem versions?
I can see something similar, but very old and on linux:
http://www.ruby-forum.com/topic/60495
--
--
Before posting, please read http://watir.com/support. In short: search befor
Thanks, John. I just need some simple GUI from Tk. It seems that I
can't do it with watir. So I may just go for watij (Java).
On Jan 11, 4:20 pm, John Fitisoff wrote:
> Not sure what's going on there but probably worth mentioning that there are
> some existing alternatives. I think Test::Unit ha
Prior to this error, I installed MySQL 5.1, so I uninstalled 5.1 and
installed 5.0 and I didn't run into this issue. I'll update this if I
do, but it seems to be the solution.
-Original Message-
From: watir-general@googlegroups.com
[mailto:watir-gene...@googlegroups.com] On Behalf Of
