meta_types 0.0.1

data/config/routes.rb

@@ -0,0 +1,2 @@
+MetaTypes::Engine.routes.draw do
+end

data/db/migrate/20120507130230_create_hstore.rb

@@ -0,0 +1,9 @@
+class CreateHstore < ActiveRecord::Migration
+  def self.up
+    execute "CREATE EXTENSION hstore"
+  end
+
+  def self.down
+    execute "DROP EXTENSION hstore"
+  end
+end

data/db/migrate/20120507130237_meta_type.rb

@@ -0,0 +1,19 @@
+class MetaType < ActiveRecord::Migration
+  def up
+    # we have a type column to allow STI to have a ProductType, a CustomerType and the like
+    execute <<-CREATE_SQL
+      create table meta_types (
+        id          serial PRIMARY KEY,
+        sid         character varying not null UNIQUE,
+        type        character varying,
+        title       character varying not null UNIQUE,
+        created_at  timestamp without time zone,
+        updated_at  timestamp without time zone
+      );
+    CREATE_SQL
+  end
+
+  def down
+    execute "DROP TABLE meta_types"
+  end
+end

data/db/migrate/20120507130255_meta_type_property.rb

@@ -0,0 +1,23 @@
+class MetaTypeProperty < ActiveRecord::Migration
+  def up
+    execute <<-CREATE_SQL
+      create table meta_type_properties (
+        id                serial NOT NULL PRIMARY KEY,
+        sid               character varying,
+        label             character varying not null,
+        property_type_sid character varying not null,
+        required          boolean not null default false,
+        system            boolean not null default false,
+        dimension         character varying null default null,
+        default_value     character varying null default null,
+        choices           character varying,
+        created_at        timestamp without time zone,
+        updated_at        timestamp without time zone
+      );
+    CREATE_SQL
+  end
+
+  def down
+    execute "drop table meta_type_properties"
+  end
+end

data/db/migrate/20120507130303_meta_type_member.rb

@@ -0,0 +1,18 @@
+class MetaTypeMember < ActiveRecord::Migration
+  def up
+    execute <<-CREATE_SQL
+      create table meta_type_members (
+        id            serial PRIMARY KEY,
+        meta_type_id  integer references meta_types(id),
+        meta_type_property_id integer references meta_type_properties(id),
+        position      integer,
+        created_at    timestamp without time zone,
+        updated_at    timestamp without time zone
+      );
+    CREATE_SQL
+  end
+
+  def down
+    execute "drop table meta_type_members"
+  end
+end

data/lib/meta_types.rb

@@ -0,0 +1,9 @@
+require "meta_types/engine"
+
+module MetaTypes
+
+end
+
+Dir[File.join(File.dirname(__FILE__), 'meta_types', '*.rb')].each do |fn|
+  require fn
+end

data/lib/meta_types/active_record.rb

@@ -0,0 +1,48 @@
+module MetaTypes::ActiveRecordAddons
+
+  module ClassMethods
+    def meta_typed(nam, hstore=nil)
+      hstore ||= "#{nam}_hstore"
+      raise "No column named '#{hstore}' found." unless attribute_names.member? hstore
+      vnam = "@_meta_properties_#{nam}"
+      belongs_to :meta_type
+
+      define_method nam do
+        return nil unless meta_type
+        m = instance_variable_get(vnam)
+        m ||= instance_variable_set(vnam, MetaTypes::MetaProperties.new(self, hstore))
+      end
+
+      define_method "#{nam}_attributes=" do |hash|
+        self.send(nam).update_attributes(hash)
+      end
+      attr_accessible "#{nam}_attributes"
+
+      self.define_singleton_method "where_#{nam}" do |conditions_hash|
+        conditions_hash.inject(where("1=1")) do |relation, (k,v)|
+          relation.where("#{hstore} @> (? => ?)", k.to_s, v.to_s)
+        end
+      end
+
+      self.define_singleton_method "where_#{nam}_like" do |conditions_hash|
+        conditions_hash.inject(where("1=1")) do |relation, (k,v)|
+          relation.where("#{hstore} -> ? LIKE ?", k.to_s, v.to_s)
+        end
+      end
+
+      # validate do
+      #   v = self.send(nam).valid?
+      #   errors.add(nam, v) if v.present?
+      # end
+    end
+  end
+
+  class << self
+    def included(by)
+      by.send :extend, MetaTypes::ActiveRecordAddons::ClassMethods
+    end
+  end
+
+end
+
+ActiveRecord::Base.send :include, MetaTypes::ActiveRecordAddons

data/lib/meta_types/engine.rb

@@ -0,0 +1,5 @@
+module MetaTypes
+  class Engine < ::Rails::Engine
+    isolate_namespace MetaTypes
+  end
+end

data/lib/meta_types/meta_properties.rb

@@ -0,0 +1,93 @@
+class MetaTypes::MetaProperties
+
+  include Enumerable
+
+  attr_accessor :_model
+  attr_accessor :_hsname
+  attr_accessor :_props
+
+  def initialize(model, hsname)
+    self._model = model
+    self._hsname = hsname
+    self._props = meta_type && meta_type.meta_type_properties.ordered.inject({}) do |h, mp|
+
+      h[mp.sid] = MetaTypes::MetaProperty.new(self, mp.sid)
+
+      self.define_singleton_method mp.sid do
+        h[mp.sid].value
+      end
+
+      self.define_singleton_method "#{mp.sid}=" do |v|
+        h[mp.sid].value = v
+      end
+
+      h
+    end
+  end
+
+  def update_attributes(hashh)
+    hash = hashh.dup
+    date_keys = hash.keys.select{|k| /\([123]i\)\Z/.match(k) }.map{|k|
+      k.split("(").first
+    }.uniq.each{|k|
+      dats = (1..3).map{|i| hash.delete("#{k}(#{i}i)")}.join("-")
+      self.send "#{k}=", dats
+    }
+    hash.each do |k,v|
+      self.send "#{k}=", v
+    end
+  end
+
+  def validate
+    raise "saa"
+  end
+
+  def valid?
+    inject([]) do |e, v|
+      v.required && v.value.blank? ?
+        e << "#{v.label} must be present" :
+        e
+    end.join(", ").presence
+  end
+
+  def persisted?()
+    false
+  end
+
+  def each()
+    _props.each { |k,v| yield(v) }
+  end
+
+  def length
+    _props.length
+  end
+  alias_method :count, :length
+
+  def meta_type()
+    _model.meta_type
+  end
+
+  def set_value(sid, val)
+    _model.send "#{_hsname}=", (_model.send("#{_hsname}") || {}).merge(sid => val)
+  end
+
+  def get_value(sid)
+    _model.send(_hsname).try :[], sid
+  end
+
+  def [](sid)
+    _props[sid.to_s]
+  end
+
+  def column_for_attribute(sid)
+    MetaTypeProperty[sid]
+  end
+
+  class << self
+    def validators_on(sid)
+      MetaTypeProperty[sid].required? ?
+        [ActiveModel::Validations::PresenceValidator.new(attributes: [:title])] :
+        []
+    end
+  end
+end

data/lib/meta_types/meta_property.rb

@@ -0,0 +1,27 @@
+class MetaTypes::MetaProperty
+  attr_accessor :meta_properties
+  attr_accessor :meta_type_property
+  attr_accessor :sid
+
+  def initialize(meta_properties, sid)
+    self.meta_properties = meta_properties
+    self.sid = sid
+    self.meta_type_property = MetaTypeProperty[sid]
+  end
+
+  def value
+    meta_type_property.cast(meta_properties.try(:get_value, sid) || meta_type_property.default_value)
+  end
+
+  def value=(val)
+    meta_properties.set_value(sid, meta_type_property.parse(val))
+  end
+
+  def choices()
+    ch = meta_type_property.choices.presence
+    ch && ch.split('||').map(&:strip)
+  end
+
+  delegate :sid, :label, :default_value, :unit, :meta_property_type, :required,
+    to: :meta_type_property
+end

data/lib/meta_types/meta_property_type.rb

@@ -0,0 +1,59 @@
+class MetaTypes::MetaPropertyType
+
+  attr_accessor :sid
+  attr_accessor :name
+
+  def initialize(sid, name)
+    self.sid = sid
+    self.name = name
+  end
+
+  Instances = {
+    integer: new('integer', 'Integer'),
+    string:  new('string',  'String'),
+    boolean: new('boolean', 'Boolean'),
+    float:   new('float',   'Float'),
+    text:    new('text',    'Text'),
+    date:    new('date',    'Date')
+  }
+
+  BoolTrueReps = %w{1 t true}
+
+  # cast is called to transform the string-value from the db
+  # into the desired ruby type
+  def cast(sval)
+    case sid
+    when 'integer' then sval.to_i
+    when 'string', 'text' then sval
+    when 'boolean' then BoolTrueReps.member?(sval.to_s)
+    when 'float'   then sval.to_f
+    when 'date'    then sval && Date.parse(sval)
+    else raise "Don't know how to handle MetaPropertyType with sid '#{sid}'."
+    end
+  end
+
+  # parse is called to transform the given ruby type into the
+  # db string format
+  def parse(sval)
+    case sid
+    when 'integer' then sval.to_s
+    when 'string', 'text' then sval.to_s
+    when 'boolean' then BoolTrueReps.member?(sval.to_s).to_s
+    when 'float'   then sval.to_s
+    when 'date'    then sval.presence && (sval.is_a?(String) ? Date.parse(sval) : sval).strftime("%Y-%m-%d")
+    else raise "Don't know how to handle MetaPropertyType with sid '#{sid}'."
+    end
+  end
+
+  class << self
+    def find(sid)
+      Instances[sid.to_sym] || raise("No MetaPropertyType with sid '#{sid}' found.")
+    end
+
+    alias_method :[], :find
+
+    def sids() %w{integer string boolean float text date} end
+  end
+
+end
+

data/lib/meta_types/version.rb

@@ -0,0 +1,3 @@
+module MetaTypes
+  VERSION = "0.0.1"
+end

data/lib/tasks/meta_types_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :meta_types do
+#   # Task goes here
+# end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.