bezel 0.1.0

data/HISTORY

@@ -0,0 +1,12 @@
+= Release History
+
+== 0.1.0 / 2010-02-19
+
+This is an alpha release of Bezel, an alternate load
+system for Ruby, just to put it out there and get
+some feedback.
+
+Changes:
+
+* Happy Frakn Birthday!
+

data/MANIFEST

@@ -0,0 +1,25 @@
+HISTORY
+MANIFEST
+README
+lib/bezel.rb
+meta/homepage
+meta/name
+meta/ruby
+meta/suite
+meta/summary
+meta/title
+meta/version
+test/demos
+test/demos/01_example.rdoc
+test/fixtures
+test/fixtures/gems
+test/fixtures/gems/tryme-1.0
+test/fixtures/gems/tryme-1.0/lib
+test/fixtures/gems/tryme-1.0/lib/tryme
+test/fixtures/gems/tryme-1.0/lib/tryme.rb
+test/fixtures/gems/tryme-1.0/lib/tryme/extra.rb
+test/fixtures/gems/tryme-1.1
+test/fixtures/gems/tryme-1.1/lib
+test/fixtures/gems/tryme-1.1/lib/tryme
+test/fixtures/gems/tryme-1.1/lib/tryme.rb
+test/fixtures/gems/tryme-1.1/lib/tryme/extra.rb

data/README

@@ -0,0 +1,60 @@
+= Bezel
+
+* home: http://proutils.github.com/bezel
+* work: http://github.com/proutils/bezel
+
+== DESCRIPTION
+
+The idea of Bezel is to overcome the limitations of using different
+versions of the same package in the same Ruby process.
+
+== USAGE
+
+It works like this. Let's say I wrote a library called TomsLib. Now I
+want to use TomsLib in my new fancy app, FancyApp. In my FancyApp
+namespace I have to create a reference to TomsLib.
+
+    module FancyApp
+      TomsLib = lib('tomslib', '1.5')
+      ...
+ 
+Now I have access to TomsLib, but it is localized to my application.
+If Jane comes along and wants to use a different version of TomsLib
+but also utilizes my FancyApp, she could do so:
+
+    module JanesProgram
+      TomsLib  = lib('tomslib', '1.0')
+      FancyApp = lib('fancyapp')  # use newest available
+      ...
+
+How does this work? When you call lib(), Bezel looks for the package
+in the current Gem paths (and in the future, Roll ledger) then it
+reads the primary package file (eg. tomslib.rb) from the package and
+evals it into an anonymous module.
+
+This has a some important effects on how you write your Ruby programs:
+
+1. Any reference to core/standard libraries must be referenced via '::'
+prefix (eg. ::Enumerable).
+
+2. Core extensions are not version isolated. So avoid them when
+possible, or depend on highly stable standardized bases such as
+Ruby Facets and ActiveSupport.
+
+3. Since Bezel is a completely different alternative to Ruby's normal
+load system, your program will require Bezel be installed by your
+users. 
+
+4. Within Bezel dependent libraries #import must be used instead of
+#require or #load in order to keep the code within the current module.
+
+Despite the minor limitations and necessary practices required for its
+use, Bezel is highly advantageous to the developers and end-users alike
+in that it puts an end to the dreaded Dependency Hell.
+
+== COPYRIGHT
+
+Copyright (c) 2009 Thomas Sawyer
+
+Bezel is distributed under the terms of the Ruby License.
+

data/lib/bezel.rb

@@ -0,0 +1,130 @@
+# The idea of Bezel is to overcome the limitations of using
+# different versions of the same package in the same Ruby
+# proccess.
+#
+# It works like this. Let's say I wrote a library called TomsLib.
+# Now I want to use TomsLib in my new fancy app, FancyApp. In my
+# FancyApp namespace I have to create a reference to TomsLib.
+#
+#   module FancyApp
+#     TomsLib = lib('tomslib', '1.5')
+#     ...
+# 
+# Now I have access to TomsLib, but it is localized to my
+# application. If Jane comes along and wants to use a different
+# version of TomsLib but also utilizes my FancyApp, she
+# could do so:
+#
+#   module JanesProgram
+#     TomsLib  = lib('tomslib', '1.0')
+#     FancyApp = lib('fancyapp')  # use newest available
+#     ...
+#
+# How does this work? When you call library(), Bezel looks for
+# the package in the current gem paths (and, in the future, Roll ledger)
+# then it reads the primary package file (eg. tomslib.rb) fro the package
+# and evals it into an anonymous module.
+#
+# This has a some important effects on how you write your Ruby programs:
+#
+# 1. Any reference to core/standard libraries must be referenced via
+#    :: prefix (eg. ::Enumerable).
+#
+# 2. Core extensions are not version controlled. So avoid them when
+#    possible, or depend on highly stable standardized bases such as
+#    Facets and ActiveSupport.
+#
+# 3. Since Bezel is a completely different alternative to Ruby's normal
+#    load system, your program will require Bezel be installed by your
+#    users. 
+#
+# Despite the limitations and necessary practices required for its use
+# Bezel is highly advantageous to the developers and end-users alike
+# in that it puts an end to the dreaded Dependency Hell.
+#
+class Bezel < Module
+  require 'rubygems'
+
+  # Cache of loaded modules. This speeds things
+  # up if two libraries load the same third library.
+  TABLE = Hash.new{|h,k|h[k]={}}
+
+  # Load stack keeps track of what modules are in the process
+  # of being loaded.
+  STACK = []
+
+  #
+  def self.gem_paths
+    @gem_paths ||= (
+      Gem.path.map do |dir|
+        Dir[File.join(dir, 'gems', '*')]
+      end.flatten
+    )
+  end
+
+  #
+  def self.select(name)
+    gem_paths.select do |path|
+      File.basename(path) =~ /^#{name}-/
+    end
+  end
+
+  #
+  def self.find(name, version=nil)
+    if version
+      basename = "#{name}-#{version}"
+      select(name).find do |path|
+        File.basename(path) == basename
+      end
+    else
+      select(name).max
+    end
+  end
+
+  #
+  #def self.main(name, version=nil)
+  #  path = find(name, version)
+  #  File.join(path, 'lib', name + '.rb')
+  #end
+
+  #
+  def initialize(name, path)
+    @__name__ = name
+    @__path__ = path
+  end
+
+  def __name__
+    @__name__
+  end
+
+  def __path__
+    @__path__
+  end
+
+end
+
+#
+def lib(name, version=nil)
+  path = Bezel.find(name, version)
+  main = File.join(path, 'lib', name + '.rb')
+
+  return Bezel::TABLE[main] if Bezel::TABLE.key?(main)
+
+  mod = Bezel.new(name, path)
+
+  Bezel::STACK << mod
+
+  mod.module_eval(File.read(main), main, 0)
+
+  Bezel::STACK.pop
+
+  Bezel::TABLE[main] = mod
+end
+
+# When using Bezel, rather than use #require or #load, you use #import.
+def import(fname)
+  mod = Bezel::STACK.last
+  file = File.join(mod.__path__, 'lib', mod.__name__, fname)
+  mod.module_eval(File.read(file), file, 0)
+end
+

data/meta/homepage

@@ -0,0 +1 @@
+http://proutils.github.com/bezel

data/meta/name

@@ -0,0 +1 @@
+bezel

data/meta/ruby

@@ -0,0 +1 @@
+1.8.7

data/meta/suite

@@ -0,0 +1 @@
+proutils

data/meta/summary

@@ -0,0 +1 @@
+Alternate loading system for Ruby allowing version multiplicity.

data/meta/title

@@ -0,0 +1 @@
+Bezel

data/meta/version

@@ -0,0 +1 @@
+0.1.0

data/test/demos/01_example.rdoc

@@ -0,0 +1,46 @@
+= Bezel
+
+First Bezel must be loaded, of course. This will also load
+RubyGems as Bezel presently uses the +Gem.path+ to locate
+Ruby libraries.
+
+  require 'bezel'
+
+We are going to use a dummy Gem location for this example.
+
+  Gem.path.unshift(File.expand_path('../fixtures'))
+
+Now we can try it out. The dummy location houses two libraries
+of the same name but different versions.
+
+  module Example1
+    TryMe = lib('tryme', '1.0')
+  end
+
+TryMe has a class method called #report and we should see that
+it works as expected.
+
+  Example1::TryMe.report.assert == "You are using version 1.0!"
+
+It also imports a method called #extra from a seperate file.
+
+  Example1::TryMe.extra.assert == "Something extra from version 1.0!"
+
+Now we should be able to do the same for TryMe v1.1 without any
+issues of interference betwee the two versions.
+
+  module Example2
+    TryMe = lib('tryme', '1.1')
+  end
+
+Again we should see that the #report method works as expected, but this
+time reported form the new version.
+
+  Example2::TryMe.report.assert == "You are using version 1.1!"
+
+And that it also imports a method called #extra from a seperate file.
+
+  Example2::TryMe.extra.assert == "Something extra from version 1.1!"
+
+That's all folks!
+

data/test/fixtures/gems/tryme-1.0/lib/tryme.rb

@@ -0,0 +1,11 @@
+# TryMe 1.0
+
+VERSION = "1.0"
+
+def self.report
+  "You are using version #{VERSION}!"
+end
+
+import("extra.rb")
+
+

data/test/fixtures/gems/tryme-1.0/lib/tryme/extra.rb

@@ -0,0 +1,5 @@
+
+def self.extra
+  "Something extra from version #{VERSION}!"
+end
+

data/test/fixtures/gems/tryme-1.1/lib/tryme.rb

@@ -0,0 +1,10 @@
+# TryMe 1.1
+
+VERSION = "1.1"
+
+def self.report
+  "You are using version #{VERSION}!"
+end
+
+import("extra.rb")
+

data/test/fixtures/gems/tryme-1.1/lib/tryme/extra.rb

@@ -0,0 +1,5 @@
+
+def self.extra
+  "Something extra from version #{VERSION}!"
+end
+

metadata

@@ -0,0 +1,80 @@
+--- !ruby/object:Gem::Specification 
+name: bezel
+version: !ruby/object:Gem::Version 
+  prerelease: false
+  segments: 
+  - 0
+  - 1
+  - 0
+  version: 0.1.0
+platform: ruby
+authors: []
+
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2010-02-19 00:00:00 -05:00
+default_executable: 
+dependencies: []
+
+description: ""
+email: 
+executables: []
+
+extensions: []
+
+extra_rdoc_files: 
+- README
+files: 
+- HISTORY
+- MANIFEST
+- README
+- lib/bezel.rb
+- meta/homepage
+- meta/name
+- meta/ruby
+- meta/suite
+- meta/summary
+- meta/title
+- meta/version
+- test/demos/01_example.rdoc
+- test/fixtures/gems/tryme-1.0/lib/tryme.rb
+- test/fixtures/gems/tryme-1.0/lib/tryme/extra.rb
+- test/fixtures/gems/tryme-1.1/lib/tryme.rb
+- test/fixtures/gems/tryme-1.1/lib/tryme/extra.rb
+has_rdoc: true
+homepage: http://proutils.github.com/bezel
+licenses: []
+
+post_install_message: 
+rdoc_options: 
+- --title
+- Bezel API
+- --main
+- README
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      segments: 
+      - 0
+      version: "0"
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      segments: 
+      - 0
+      version: "0"
+requirements: []
+
+rubyforge_project: bezel
+rubygems_version: 1.3.6.pre.3
+signing_key: 
+specification_version: 3
+summary: Alternate loading system for Ruby allowing version multiplicity.
+test_files: []
+