double-clickable *.llp

[Chuck Remes]

I need to create a double-clickable app. In a post to ruby-talk, someone suggested I use "limelight pack <proj dir>" to create a *.llp file. This file could then be double-clicked to launch the GUI.

However, when double-clicking it on OSX or Windows the OS doesn't know how to find the program necessary to launch it. What do I need to do to get this working?

Also, this particular project requires a few gems. Is it sufficient to have them installed as part of the jruby installation or do I need to "freeze" them as part of the project to make it work?

cr

[Chuck Remes]

Is it a better option to use rawr to pack everything up into jars?

cr

[Micah Martin]

Chuck,

On machines that need to open production, Limelight should be installed as an application.  The installers register file extensions with the OS make Limelight feel more like a native app.  Installers are available here: http://limelight.8thlight.com/download

Gems:  Gems should be bundled inside the production.  Anything inside your production directory will be "packed" along with your production.  Bundler has to ability to create standalone gem repo.  Here's what I typically do:

* Gemfile: specify all the required gems

* Install all the gems in a standalone repo inside the production dir (this feature is broken an Bundler 1.0 so you might need to install the prerelease where it's hopefully fixed.)

 $ bundle install --standalone --path=gems  

* Include the standalone gem repo in your production.  In production.rb I have:

def production_opening  require File.expand_path(File.dirname(__FILE__) + "/gems/bundler/setup") end

Alternatively, you can go old school and use rubygems and install all the gems locally:

* $ gem install -i gems <gem names>

* In production.rb:

def production_opening

  require 'rubygems'

  Gem.path << File.expand_path(File.dirname(__FILE__) + "/gems")

end

I would avoid the "freeze" command.  It's been removed in master because Bundler is a much better solution.

Micah

On Oct 24, 2011, at 9:23 AM, Chuck Remes wrote:

[Chuck Remes]

On Oct 24, 2011, at 10:06 AM, Micah Martin wrote:

Chuck,

On machines that need to open production, Limelight should be installed as an application.  The installers register file extensions with the OS make Limelight feel more like a native app.  Installers are available here: http://limelight.8thlight.com/download

I am getting a stacktrace trying to open any *.llp file after installing the Windows download. Here's a screenshot:

http://skitch.com/cremes/gdn4q/screen-shot-2011-10-24-at-12.13.40-pm

Also, I noticed that Limelight is using JRuby 1.4.0 internally. That was released in February of 2010 and is nearly 2 years old. My project needs the 1.9 syntax support in the JRuby 1.6x series. Any chance those binaries can get updated to 1.6.4 at least?

Alternatively, you can go old school and use rubygems and install all the gems locally:

* $ gem install -i gems <gem names>

* In production.rb:

def production_opening

  require 'rubygems'

  Gem.path << File.expand_path(File.dirname(__FILE__) + "/gems")

end

I'll probably use this "old school" way. For such a key piece of technology like bundler, it sure breaks a lot. :(

cr

[Chuck Remes]

On Oct 24, 2011, at 12:19 PM, Chuck Remes wrote:

On Oct 24, 2011, at 10:06 AM, Micah Martin wrote:

Chuck,

On machines that need to open production, Limelight should be installed as an application.  The installers register file extensions with the OS make Limelight feel more like a native app.  Installers are available here: http://limelight.8thlight.com/download

I am getting a stacktrace trying to open any *.llp file after installing the Windows download. Here's a screenshot:

http://skitch.com/cremes/gdn4q/screen-shot-2011-10-24-at-12.13.40-pm

I forgot to mention that this is on Windows7 x64. I don't know if that's relevant, but it might be if Win7 wasn't "common" in the wild when limelight was last released.

cr

[Micah Martin]

The problem in the screen shot is from a missing directory.  Limelight really aught to create that directory for you.  In fact, if you just open Limelight without clicking a .llp (Start > Program > Limelight) it might create the needed directory.  Otherwise, you can manually create it: <user home>/Application Data/Limelight/Productions  (C:\Documents and Settings\micah\Application Data\Limelight\Productions)

To use a newer version of JRuby, we'd have to create a new installer for that release of Limelight, which is not out of the question.  

Chuck, could you email me at micah at 8thlight dot com to discuss further?

Micah