FreeRIDE - Way too many warnings


#1

Whenever I start FreeRIDE I get a ton of warnings. It takes a long time
to start as well, probably because it is I/O bound to the console
window.

Suggestions?

Jonathan

2.so: warning: already initialized constant FOLDINGLIST_ROOT_BOXES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant FOLDINGLIST_NORMAL
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_LOOKUPTIMER
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_HEADER_CHANGE
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_LAST
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_EXTENDEDSELECT
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_SINGLESELECT
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_BROWSESELECT
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_MULTIPLESELECT
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_AUTOSELECT
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_SHOWS_LINES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_SHOWS_BOXES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_ROOT_BOXES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant TREELIST_NORMAL
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_LOOKUPTIMER
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_LAST
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant DIRLIST_SHOWFILES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant DIRLIST_SHOWHIDDEN
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant DIRLIST_NO_OWN_ASSOC
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_REFRESHTIMER
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_SHOW_FILES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_HIDE_FILES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_TOGGLE_FILES
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_SHOW_HIDDEN
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_HIDE_HIDDEN
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_TOGGLE_HIDDEN
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_SET_PATTERN
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_SORT_REVERSE
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_SORT_CASE
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_REFRESH
C:/Program
Files/Ruby/lib/ruby/gems/1.8/gems/fxruby-1.2.6-mswin32/ext/fox12/fox1
2.so: warning: already initialized constant ID_LAST


#2

On Sun, 2007-01-21 at 03:32 +0900, Ab Cd wrote:

Whenever I start FreeRIDE I get a ton of warnings. It takes a long
time
to start as well, probably because it is I/O bound to the console
window.

Suggestions?

Yes 2 of them:

  1. Don’t post the thousands of repeated errors to the list
  2. Ask the fx ruby folks what the problem is.

#3

matt wrote:

On Sun, 2007-01-21 at 03:32 +0900, Ab Cd wrote:

Yes 2 of them:

  1. Don’t post the thousands of repeated errors to the list
  2. Ask the fx ruby folks what the problem is.

You mind telling me who the fx ruby people are and how to contact them?

All I have is the whatever came with the base installation at
www.ruby-lang.org, so I assumed it was something core to the language.


#4

On Sun, 2007-01-21 at 05:51 +0900, Jonathan A. wrote:

www.ruby-lang.org, so I assumed it was something core to the language.

I must be in a good mood. Didn’t even get laid last night…

http://www.google.com/search?q=fxruby&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:unofficial&client=firefox-a

returned this in position numero uno:
http://www.fxruby.org/

And this in numero treso:
http://rubyforge.org/projects/fxruby/


#5

matt wrote:

On Sun, 2007-01-21 at 03:32 +0900, Ab Cd wrote:

Whenever I start FreeRIDE I get a ton of warnings. It takes a long
time
to start as well, probably because it is I/O bound to the console
window.

Suggestions?

Yes 2 of them:

  1. Don’t post the thousands of repeated errors to the list
  2. Ask the fx ruby folks what the problem is.

They say its Ruby’s fault for putting the bug in v1.8.5 and FreeRide’s
fault for not upgrading to FX Ruby v1.6. Though I suppose they share
part of the blame for not making backwards compatible.

Now what?

Jonathan


#6

On 1/20/07, matt removed_email_address@domain.invalid wrote:

I must be in a good mood. Didn’t even get laid last night…

http://www.google.com/search?q=fxruby&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:unofficial&client=firefox-a

returned this in position numero uno:
http://www.fxruby.org/

What is this “Google,” and why have you been keeping it a secret from
the rest of us?


#7

matt wrote:

On Sun, 2007-01-21 at 05:51 +0900, Jonathan A. wrote:

www.ruby-lang.org, so I assumed it was something core to the language.

I must be in a good mood. Didn’t even get laid last night…

http://www.google.com/search?q=fxruby&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:unofficial&client=firefox-a

returned this in position numero uno:
http://www.fxruby.org/

And this in numero treso:
http://rubyforge.org/projects/fxruby/

Gee thanks for being ever so helpful. It was so nice of you to almost
point out which of the 148,000 pages returned by google the FX Ruby
developers hang out on. I’m not even annoyed that you didn’t mention
item 4, which actually had the correct mailing list.

And now I realize how hard it would have been to just go ahead and give
me the right URL when you originally suggested I contact them. For
crying out loud, you might have had to actually think about your
response to my question.

You see, I have been ever so spoiled by hanging out in the Microsoft
forums. I’m used to people answering questions with useful information
and links in case I want to know more.

Jonathan


#8

On Sun, 2007-01-21 at 09:13 +0900, Jonathan A. wrote:

returned this in position numero uno:

Yes, but I saved you from having to type “www.google.com” and then find
a text box to type in “fxruby” and then click submit.

See how many keystrokes I just saved you from typing? Not to mention
that your wrists are now at a reduced risk of developing carpal tunnel.

And to think that for a moment I thought you were implying that I was
self-serving and arrogant.


#9
  1. Fix the bug in ruby and submit patch
  2. fix FreeRides dependency to use a newer version of FXRuby
    or
  3. Find another IDE.

try VI or [X]Emacs or pico or notepad or word or works or OpenOffice
or…

ohh you want an all in one… try Eclipse or RadRails I’ve never used
either of them, but they (among others) have gotten good reviews.

Matt

Let me get this straight. You are telling a newbie with one day of
experience that if I need to track down and fix a bug in the core of the
language itself.

Anyone else want to pick up this thread. Maybe tell me how and where to
submit bug reports? Or do you guys not do that?

Jonathan


#10

On Sun, 2007-01-21 at 08:43 +0900, Jonathan A. wrote:

  1. Don’t post the thousands of repeated errors to the list
  2. Ask the fx ruby folks what the problem is.

They say its Ruby’s fault for putting the bug in v1.8.5 and FreeRide’s
fault for not upgrading to FX Ruby v1.6. Though I suppose they share
part of the blame for not making backwards compatible.

Now what?

Jonathan

  1. Fix the bug in ruby and submit patch
  2. fix FreeRides dependency to use a newer version of FXRuby
    or
  3. Find another IDE.

try VI or [X]Emacs or pico or notepad or word or works or OpenOffice
or…

ohh you want an all in one… try Eclipse or RadRails I’ve never used
either of them, but they (among others) have gotten good reviews.

Matt


#11

Timothy H. wrote:

Jonathan A. wrote:

Anyone else want to pick up this thread. Maybe tell me how and where to
submit bug reports? Or do you guys not do that?

Please accept my apologies, on behalf of the Ruby community, for your
reception on this mailing list. Normally we are quite civilized and
supportive of new Rubyists.

You don’t have to report this problem. It is well-known. Search the
Google archives for earlier discussions if you’re interested. I believe
this bug report
http://rubyforge.org/tracker/index.php?func=detail&aid=5701&group_id=426&atid=1698
addresses the problem.

Welcome to Ruby!

Thanks, I really appreciate that. It is so hard to find ones way around
a new community, especially when you run into problems right from the
start.

Do you know if anyone has of list of which components are still
supported and which are not?

If I’m ever going to use Ruby in production, knowing what stuff has
already reached end of life is vital. And apparently I cannot blindly
trust the main Ruby distribution to be up to date.

Jonathan


#12

On Sun, 2007-01-21 at 10:41 +0900, Timothy H. wrote:

this bug report
http://rubyforge.org/tracker/index.php?func=detail&aid=5701&group_id=426&atid=1698
addresses the problem.

Welcome to Ruby!

There’s no need to apologize on anyone’s behalf (I’m certainly not
sorry, and I don’t consider what I did rude either). Remember, I did his
homework for him, and presented several options of how to proceed. I
should be thanked for presenting the information on a hyper-text
platter. And we should pity and feel sorry for those that have
forgotten (or never knew) how to do research on there own. But don’t
worry, over time, they can be trained.

Welcome to reality.


#13

Jonathan A. wrote:

Anyone else want to pick up this thread. Maybe tell me how and where to
submit bug reports? Or do you guys not do that?

Please accept my apologies, on behalf of the Ruby community, for your
reception on this mailing list. Normally we are quite civilized and
supportive of new Rubyists.

You don’t have to report this problem. It is well-known. Search the
Google archives for earlier discussions if you’re interested. I believe
this bug report
http://rubyforge.org/tracker/index.php?func=detail&aid=5701&group_id=426&atid=1698
addresses the problem.

Welcome to Ruby!


#14

matt wrote:

On Sun, 2007-01-21 at 10:41 +0900, Timothy H. wrote:

this bug report
http://rubyforge.org/tracker/index.php?func=detail&aid=5701&group_id=426&atid=1698
addresses the problem.

Welcome to Ruby!

There’s no need to apologize on anyone’s behalf (I’m certainly not
sorry, and I don’t consider what I did rude either). Remember, I did his
homework for him, and presented several options of how to proceed. I
should be thanked for presenting the information on a hyper-text
platter. And we should pity and feel sorry for those that have
forgotten (or never knew) how to do research on there own. But don’t
worry, over time, they can be trained.

Welcome to reality.

Tell me something, why do you bother?

I mean, clearly the only “help” you are willing to offer to people like
me is to tell us how do google searches. So why not just ignore the
question and let someone else field the answer?

And does it really bother you that much that I was unable to find the
information on my own? Is not the purpose of this forum for helping
people use Ruby? 'Cause if its not, let me know and I will go elsewhere.

From where I stand, all you are doing is wasting both my time and yours.
Is you faith in the all mighty search engine really worth alienating a
new user?

Jonathan


#15

On Jan 21, 2:10 pm, matt removed_email_address@domain.invalid wrote:

Please accept my apologies, on behalf of the Ruby community, for your
reception on this mailing list. Normally we are quite civilized and
supportive of new Rubyists.

There’s no need to apologize on anyone’s behalf (I’m certainly not
sorry, and I don’t consider what I did rude either).

I offer my condolences too, Johnathan. Statistically, you’re very
likely to get a nicer response next time :slight_smile:

Cheers,
Gavin


#16

matt wrote:

On Sun, 2007-01-21 at 10:41 +0900, Timothy H. wrote:

this bug report
http://rubyforge.org/tracker/index.php?func=detail&aid=5701&group_id=426&atid=1698
addresses the problem.

Welcome to Ruby!

There’s no need to apologize on anyone’s behalf (I’m certainly not
sorry, and I don’t consider what I did rude either). Remember, I did his
homework for him, and presented several options of how to proceed. I
should be thanked for presenting the information on a hyper-text
platter. And we should pity and feel sorry for those that have
forgotten (or never knew) how to do research on there own. But don’t
worry, over time, they can be trained.

Welcome to reality.

I pity those that have forgotten (or never knew) the difference between
“there”, “their”, and “they’re”.


#17

On 1/21/07, Jonathan A. removed_email_address@domain.invalid wrote:

Tell me something, why do you bother?

I mean, clearly the only “help” you are willing to offer to people like
me is to tell us how do google searches. So why not just ignore the
question and let someone else field the answer?

The answer to that is quite simple, the only help you needed was knowing
who
to ask ‘the fx ruby people’ and how to find them. Personally I think I
think the help was presented in a light hearted manner, but feel free to
disagree.

Time is precious to each and every one of us, so doing some research
before
asking questions, is more than just a courtesy. Do your reseach, ask
clear
questions and most of the time your question gets answered.

Since Matt answered your second question, he really must have been in a
good
mood.

Johan Veenstra


#18

Jonathan A. wrote:

supportive of new Rubyists.
Thanks, I really appreciate that. It is so hard to find ones way around
Jonathan

To the best of my knowledge all the components in the 1.8.5 one-click
installer are completely supported. The problem you’ve encountered is
known. Apparently it is currently considered as a problem in Ruby
itself, not FreeRIDE. I see from the bug report that it is currently
assigned to Ruby’s inventor, Matz.

Typically the one-click installer goes through many pre-release versions
before the final. When it is next released you’ll have plenty of
opportunity to test the components and offer feedback. Instead of blind
trust you’ll have your own hands-on evaluation, and the rest of the
community will benefit from your work.


#19

On Jan 22, 2007, at 10:29 AM, Johan Veenstra wrote:

asking questions, is more than just a courtesy. Do your reseach,
ask clear
questions and most of the time your question gets answered.

Since Matt answered your second question, he really must have been
in a good
mood.

We really shouldn’t get into long threads discussing who was polite
and who wasn’t. Despite that, I can’t resist jumping to the posters
defense here and saying that I didn’t find Matt’s replies “light
hearted” at all. I found them to be on the rude side.


#20

On 1/21/07, Gavin S. removed_email_address@domain.invalid wrote:

I offer my condolences too, Johnathan. Statistically, you’re very
likely to get a nicer response next time :slight_smile:

+1