Uninitialized constant error using Ruby in RubyMine

views:

103

answers:

+1 Q:

Uninitialized constant error using Ruby in RubyMine

Has anyone used RubyMine who could help me out?

I am new to RubyMine, and when I create my first project and add a few classes and wire them together for a simple meaningless application I am getting this error: "uninitialized constant RubyApp (NameError)"

But when I take all the classes and put them in one file then run it, it runs fine.

What am I missing about using RubyMine here?

Thanks for the help.

Not sure if this applies to your case, since I've only run into this issue with gems. But, Rubymine requires you to link the gems your using and what not into your project settings for things to work. At least that is how I remember it when I tried it out.

nowk 2009-12-22 03:04:49

hmmm... but how does this explain it working fine if I put all the classes in one file?

Alex Baranosky 2009-12-22 03:26:49

Well, you wouldn't put all the classes into one file. But you would configure the Rubymine project to know what to use and where to look for things. My basic understanding of how Rubymine works is that it creates an isolated env. within the app for your project. So if you need access to a gem you not only have to require "...", as usual, but you also have to add it to the list of gems available to the project.

nowk 2009-12-22 03:57:01

I used Rubymine during their beta, so not sure if things have changed since. So I could be totally off.

nowk 2009-12-22 04:00:14

+1 A:

Is "RubyApp" one of your classes? If so, it sounds like you're not requiring the other ruby files you're creating.

RubyMine pretty much doesn't get in your way at all, although it does like having gems 'attached' to the project.

Trevoke 2010-01-06 18:21:15

ansaurus

tags:

views:

answers:

Uninitialized constant error using Ruby in RubyMine

related questions