From: james_b <james_b@...>
Date: 2003-07-04T07:40:06+09:00
Subject: Re: RubyScript munges up Windows command line operation

> If you look at the messages in this group, and any other
> group for that matter, probably the number one issue is
> trying to get something to run on a version of Windows. 

Well, there may be more concerning various flavors of Mac OS.
But either way, it's not a good indidcator of how many pople are having 
problems with an OS.


> It
> is impossible to fix something where the code is secret.

Maybe, though I doubt this is a Windows source code issue.  I think the 
trouble is the RubyScript installation package munging up file 
associations.  I imagine this can be repaired by poking about in the 
registry.

The better solution might be for the installation process to prompt the 
user for any registry changes.  I think it should be possible to have 
IIS or WSH know about RubyScript without farking the behavior of other 
ruby files.  Maybe it's a simple as using a different file extension, 
such as rbs or rbys or whatever.

I've been working on some IE context menu extensions, and looked into 
using RubyScript, but I've run into the same multple-Ruby conflicts on 
other machines and decided to pass.  (Though I have to say, I hadn't 
done any JavaScript coding in a while and it's fun.  It, like, Ruby, has 
some nice dynamic features.  But I was hoping to use my browser tools as 
a way to introduce more peope to Ruby. Oh well.)

> For myself, if I can't do it simply and easily, I have
> learned to give up fast.  99.9% of my computer problems are
> from Windows.  FreeBSD gives me the rest, and they are all
> fixable..  You are not alone.

I tried installing and configuring FreeBSD, but I couldn't do it simply 
and easily, so I gave up and stayed with Redhat Linux :)

James