TurboRuby 2.0 Release Notes

By: Mark Deckert

Abstract: Release Notes

    TurboRuby™ Release Notes

These notes apply to the TurboRuby 2.0 release.

For updates to these notes, see https://dn.codegear.com/article/38878.

    Post Installation Instructions

    Confirm the Installation

To confirm a good installation from the command prompt or the shell:

  1. Run ruby -v. This should return: Ruby version 1.8.5 or higher.

    Configure the Ruby Interpreter

After installing and launching TurboRuby you will need to specify a “workspace”, which is a container directory for your projects. You can create new workspaces and switch workspaces from within TurboRuby. For every new workspace you will need to specify a Ruby interpreter.

From the IDE to configure the Ruby interpreter:

  1. Select Window->Preferences->Ruby->Interpreters.
  2. Either try the Search... button or Add and browse for the ruby executable file in the Ruby installation directory. On Mac if you've launched from the finder, /usr/local/bin won't be in the path but /usr/local/bin/ruby is the installed interpreter.
  3. Once the installed Ruby interpreter is shown in the Ruby Interpreters list, ensure its checkbox is checked and click OK.

Note: Selection lists for gem install and script/plugin install may be slow during their initial use.

    New Features in this Version

In this release, we have continued to add support for new Ruby features. For more information see the "What's New" Help topic.

    Product Updates

The TurboRuby team expects to update the product regularly. You can check for updates using the Update Manager, found under the Help menu.

    Reporting Bugs

Please report bugs and make suggestions for improvements to TurboRuby via Quality Central at https://qc.codegear.com.

    Known Issues

These issues may affect your projects:

ID Number Summary
2158 Reading characters from STDIN within irb (ruby console) hangs the console.
3709 Intermittent long pauses when editing Ruby files under Linux Ubuntu and Ruby 1.8.5. Upgrading to Ruby 1.8.6 with i686 ISA alleviates this problem.
4980 Gem installation fails on Mac OS X if prerequisites are not met. Workaround: Install XCode.
5181 [Show Logical Structures] button in the debugging perspective does not work.
5777 Setting Visual Effects on Ubuntu 7.10 results in an empty installer window. Workaround: Set [System]|[Preferences]|[Appearance]|[Visual Effects] to "None".
5910 Lack of support for UTF-8 encoded documents results in the corrupted display of Japanese characters on the Windows platform when the display of a document encoded in this manner is requested (e.g. running "rake notes" from the Workspace Commander).
6075 If TurboRuby has been launched from a terminal, required password entry for external processes (e.g. repository access without cached credentials) must be entered from the terminal which launched TurboRuby.
6109 EUC-JP locale on Ubuntu causes errors in the display of the Welcome Page.
6296 Due to an issue with the ruby-debug gem version 0.10.1, step return does not pause execution when the fast ruby debugging engine is enabled. Workaround: choose "Basic Ruby Debugging Engine" from Ruby->Debug->Engines in the Preferences Menu.
6322 In some cases on Ubuntu linux the Welcome Page appears without any background or formatting. Closing and reopening the Welcome page sometimes resolves this.
6365 If a missing gem fails to install from using the "Quick Fix" option but the gem command returns success, the error marker will no longer be displayed. Workaround: rebuild project to get error marker. Project | Clean...
6457 When run as an unprivileged user, the uninstaller fails to ask permission to execute as the superuser and instead fails to uninstall correctly. Workaround: execute the uninstaller using sudo.
6466 The installer does not execute correctly if run from within a mounted iso. Workaround: copy the contents of the iso to a local directory and run from there.
6532 Due to an issue with Subclipse, renaming an SVN Project which has been imported from another workspace (or otherwise had its working copy moved) fails. Workaround: run `chflags -R nouchg {PROJECT_DIRECTORY}` and then "Refresh" inside Eclipse.
6562 [Use Step Filters] tool bar button is disable in [Debug] view.
6567 With [Use Step Filters] enabled, the debugger may step into a filtered class it should step over.
6635 Basic Ruby debugger does not work with JRuby
6692 Ruby script cannot be profiled with jruby. The Profiler only supports MRI.
6832 Console view cannot display UTF-8 encoded output. Workaround: This will work as expected, if you explicitly set "Console Encoding" to "UTF-8" for the Run Configuration.

Copyright ™ 2007-2008 Embarcadero Technologies, Inc., All Rights Reserved.

Server Response from: ETNASC01