1. November 7, 2009

    Installing Ruby on Ubuntu

    Ubuntu seperates many standard ruby components. The following console command installs many of the necessary ones for Ruby 1.8:

    sudo apt-get install ruby1.8 ruby1.8-dev libruby1.8 irb1.8 rdoc1.8 ri1.8 rubygems1.8 libreadline-ruby1.8

    Afterwards update ruby gems:

    sudo gem update —system

    That’s it!

  2. November 7, 2009

    Installing Ruby on Mac OS X

    The good news is you probably don’t have to. The following releases of Mac OS X already have ruby:

    • Leopard ships with ruby 1.8.6 (2008-08-11 patchlevel 287)
    • Snow Leopard ships with ruby 1.8.7 (2008-08-11 patchlevel 72)

    Great! Don’t forget to update ruby gems:

    sudo gem update —system

    Assuming that you already have Ruby 1.8, the easiest way to install Ruby 1.9 and manage your versions is to use rvm: Ruby Version Manager

  3. November 7, 2009

    Installing Ruby on Windows

    There are two compilers that allow you to build Ruby for Windows:

    • MinGW which uses Native Windows libraries
    • Cygwin which replicates a POSIX (Unix) environment

    In this tutorial we are going to use RubyInstaller, which is the quickest way to install MinGW-compiled Ruby. We’ll install Ruby 1.8

    1. Download and run RubyInstaller 1.8.6 Patch 383 from their RubyForge Files page. The latest version is Preview 2.
    2. Follow the Development Kit QuickStart Installation. This is necessary to build certain ruby packages (gems), which many ruby-based applications need.

    That’s it!

    RubyInstaller allows you to have Ruby 1.8 and 1.9 installed simultaneously. You can easily switch between them using pik. Follow the installation directions in the README

  4. November 2, 2009
    Code Red: How software companies could screw up Obama’s health care reform

    Phillip Longman describes his concerns with proprietary health IT systems in this article for Washington Monthly.

    Some of the Human-Computer Interaction research questions of interest to the Telios Group is how doctors use these new tools. Our first deployment, the PNG system for Share Our Selves in Costa Mesa, returns provider usage information, e.g. ‘who clicked where’, ‘what time was a picture taken’, to Calit2 for analysis. In this way, we can identify “hot spots” in our User Interface (UI) which may be due to popular use or confusion caused by poor design. We can interview providers for feedback and make appropriate changes for a following release.

    Since Telios-based applications are Software as a Service (SaaS), new releases are not dependent on user download and installation. The Web Browser immediately downloads the newest version when pointed at the application.

    By adopting Web 2.0 practices, Telios applications espouse open protocols and third-party interactivity. We hope to make problems associated with traditional systems a thing of the past.

    HGP

  5. September 9, 2009
    Hospital Rooms of the Future

    hectorparra:

    It’s a shame they don’t have more information on the team that put this together.