Posts

First there were two different installations of gems because OSX and Netbeans each came with one. There were issues with updating them and differentiating which was getting update. Netbeans wouldn't see the right one. There were issues with one not running as root and so not getting updated.

Netbeans wouldn't change the path to what it was using.  Finally, after many hours of various people as well as myself working on it, the solution was to create the project on the command line and then to import it into Netbeans as a "new project from an existing source".  (Sarah Allen found the solution - thank you Sarah!)

I am understating the amount of pain getting this set up took.  At different times three separate engineers who were helping asked  "Why do you want to use Netbeans?" By then I wanted to use it simply to understand what I was doing wrong and out of sheer stubbornness or something...  I would still be struggling with it if not for so much super help!  I am very grateful to everyone who helped me.  I am very lucky to have so much support!

This song is about a little baby, which is what "chi chi" means in the Dominican Republic.  (It means different things elsewhere... )

UPDATE:
I found all the  href="javascript://return%20false;" and  href="javascript://return false;" and replaced them with href="javascript:void(0);" or href="javascript:void 0;".  I found that if the browser got to the href in some cases the javascript in the onclick was actually being voided, or the return being ignored, so it didn't work. 

If I added "return false;" on the end of whatever was in the onclick it was fine.  If you put "return false" at the end of the onclick to prevent the href being used, it doesn't matter very much what's in the href just so long as the browser never gets there.  For my purposes, I wanted to keep the browser from the href, but also wanted to put something in there that wouldn't cause trouble if the browser did get there by accident (the accident being me forgetting to put a "return false" in the onclick. Putting "return false" at the end of an external function didn't work).

I liked href="#null" because it isn't javascript and seemed to work fine.  One of my coworkers pointed out that it would mess up SEO because spiders would try to follow and index the bogus anchor. Users could bookmark it too. So #null is out.

href="javascript:;" didn't void anything and didn't seem to cause errors, so that's what I'm using.  I'm also adding "return false".

I had read that browsers are supposed to evaluate the onclick before the href.  Someone suggested that some browsers might evaluate them in their order of appearance in the link.  I have not looked into this much, but in my very limited testing it seems like the onclick does get evaluated first.

I found some old Kassav' videos on youtube.  Enjoy!