Codedrop™ Weblog » Ruby

jQuery Tooltips

admin — Wed, 11 Mar 2009 14:30:29 +0000

If your looking for a solid plugin library for doing tooltips jQuery style, check out cluetip. This library is based on the original jTip library created by Codey Lindley. Cluetip offers a solid set of customizable options and the dynamic positioning logic that is available through some of the reference libraries solves many of the problems I previously encountered with jTip, such as inaccurate positioning if you’ve scrolled a div containing a remote loaded tip resource.

Tweet This Post

How to install a specific software version using Mac Ports

admin — Tue, 09 Dec 2008 03:22:17 +0000

MacPorts is the preferred way of installing, managing, and upgrading ports of some the software I have on my Mac. Unfortunately mac ports does not let you specify a version. To mediate this you can create a local repository that is checked out to a specific version and install from there.

This example is how to install ruby version 1.8.5-p12.

1) Find out the svn revision number of the Portfile by looking in:

http://trac.macosforge.org/projects/macports/log/trunk/dports/lang/ruby/Portfile

In my case it is 21127.

2) Set up a local port repository. In the file /opt/local/etc/macports/sources.conf, add this line before the rsync line:

file:///Users/Shared/dports and create that directory.

3) Install the port into your local repository.

cd /Users/Shared/dports && svn co –revision 21127
http://svn.macports.org/repository/macports/trunk/dports/lang/ruby/
lang/ruby/

4) Run portindex so that ports now finds your new (old) version of ruby.

portindex /Users/Shared/dports

5) Now you should be able to see ruby @1.8.5-p12 in addition to @1.8.6 by running:

port list

6) Install Ruby

sudo port install ruby @1.8.5-p12

You should be up and running now, so to check, run:

ruby -v

You will see something like this:

ruby 1.8.5 (2006-12-25 patchlevel 12) [i686-darwin8.10.1]

Tweet This Post

Wine Debugging

groll — Tue, 07 Nov 2006 18:18:22 +0000

You can control the debug output that wine generates by manipulating the WINEDEUG environment variable. A detailed description of available options can be found here

Recently I encountered a scenario where running ruby watir tests through wine continually produced the following output:

err:rebar:REBAR_MoveChildWindows BeginDeferWindowPos returned NULL

err:rebar:REBAR_MoveChildWindows DeferWindowPos returned NULL

err:rebar:REBAR_MoveChildWindows DeferWindowPos returned NULL

err:rebar:REBAR_MoveChildWindows DeferWindowPos returned NULL

err:rebar:REBAR_MoveChildWindows DeferWindowPos returned NULL...etc...

Supressing these messages would mean defining the following env variable:

WINEDEBUG=-rebar

Another example that suppresses more common errors would be:

WINEDEBUG=fixme-all,-rebar,-local,-shell

Incidently, for this scneario, the variable needs to be set only in the local shell. However if you want to avoid having to re-enter this you might want to update ~/.bash_profile.

Tweet This Post