role-haml 1.2.1

data/.gitignore

@@ -0,0 +1,6 @@
+*.gem
+*.log
+.bundle
+Gemfile.lock
+tmp/
+pkg/*

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "role"]
+	path = role
+	url = git://github.com/kossnocorp/role.git

data/Gemfile

@@ -0,0 +1,6 @@
+source 'http://rubygems.org'
+
+# Specify your gem's dependencies in role-rails.gemspec
+gemspec
+
+gem 'haml'

data/README.md

@@ -0,0 +1,140 @@
+## This is gem for Haml support for jQuery plugin [role](https://github.com/kossnocorp/role) by [@kossnocorp](https://github.com/kossnocorp)
+
+Sponsored by [Evil Martians](http://evilmartians.com/).
+
+## Usage
+
+`app/views/home/index.html`
+
+```haml
+%a@some-role@another-role...
+```
+
+Will produce:
+
+```html
+<a role='some-role another-role'...
+```
+
+## Install
+
+In your `Gemfile`:
+
+`gem 'role-haml'`
+
+## Contributors
+
+* [@kossnocorp](http://github.com/kossnocorp)
+* @gazay
+
+## License
+
+MIT (look into repo LICENSE)
+
+# jQuery plagin role readme
+
+This project uses [Semantic Versioning](http://semver.org/) for release numbering.
+
+## Downloads
+
+* [jquery.role.min.js](https://raw.github.com/kossnocorp/role/master/lib/jquery.role.min.js)
+* [role.min.js](https://raw.github.com/kossnocorp/role/master/lib/jquery.role.min.js)
+* [jquery.role.js](https://raw.github.com/kossnocorp/role/master/lib/jquery.role.js)
+* [role.js](https://raw.github.com/kossnocorp/role/master/lib/role.js)
+
+Also you can add jquery.role.js and role.js by bundle `role-rails` gem. For futher details see *installation* section below.
+
+## Use `role` attribute FTW
+
+```
+Use cases for a role attribute for HTML5, include:
+
+* accessibility,
+* device adaptation,
+* server-side processing, and
+* complex data description.
+```
+
+This is a quote from [W3C Specification on Role attribute](http://www.w3.org/wiki/PF/XTech/HTML5/RoleAttribute#A_Role_Attribute_for_HTML5).
+
+In [Evil Martians](http://evilmartians.com/) we came up with a way to use this attribute for our own purposes.
+
+Say you have to update your website page design. HTML markup is done and you have to apply it to the existing site. Of course this marvelous page is crammed with Javascript code tied to an existing structure.
+
+``` javascript
+$('.list .item img')
+    .mouseenter(function () {
+        $(this).rotateTo(30, 300)
+    })
+    .mouseleave(function () {
+        $(this).rotateTo(0, 300)
+    });
+```
+
+Obviously, you'll have to rewrite all the selectors for the new layout. And it would be nice if you had to fix only one (or even ten) of these selectors. In reality, most likely, there will be several dozen of them.
+
+Another issue is that refactoring process requires you to change the names or a number of classes. You'll have to muddle through every JS file to find all classes you are going to change.
+
+And, of course, in both cases the end result is absolutely unpredictable, because layout alone is not enougn to figure out if a class is actualy used in JS.
+
+The `.js-class_name` prefix use may seem like a good idea, except that someone will surely add styles to this class in a future... Let alone the difficulty to spot, among a large of number of classes, one with a prefix.
+
+In order to avoid this problems, we can "attach" JS to DOM elements by a `role` attribute.
+
+It's a lot safer then prefixes, beacause it's much harder to attach styles to `role` and it feals morally difficult to break the `role` use convention.
+
+With the use of `role`, layout update becomes very straightforward: you just have to add roles to a new element, and if you are not tied to the "magic numbers" -- it will work with no further hassle.
+
+To make life easier (shoutout to [@alex_chrome](https://twitter.com/#!/alex_chrome) for the great idea) we also extended jQuery selector syntax:
+
+``` javascript
+$('@list @item @image')
+    .mouseenter(function () {
+        $(this).rotateTo(30, 300)
+    })
+    .mouseleave(function () {
+        $(this).rotateTo(0, 300)
+    });
+```
+
+`$('@list @item @image')` is the same as `$('[role="list"] [role="item] [role="image"]')` and you can use "multirole": `$('@list@coupons')`.
+
+In addition to the jQuery plug-in, I also wrote a version that extends `querySelectorAll` of [Zepto.js](http://zeptojs.com/) with a Role functionality.
+
+Using of 'role' in a query may work a bit slower compared to usual selectors, but it's neglectable even in a large number of queries.
+
+In addition to `role`, I sometimes use `id`, but only in very extraodinary cases — because if there is only single element on a page today, it may happen that there will be a few tomorrow, even if that wasn't planned.
+
+## Usage
+
+### Using selectors
+
+You can use shortcut `@` in jQuery selectors to find elements with roles.
+
+Will select all elements in document with `role="ajax-link"`:
+
+``` js
+$('@ajax-link')
+```
+
+Also you can combinate roles:
+
+`<form role="form login_form"></form>`:
+
+``` js
+$('@form@login_form')
+```
+
+Will select all forms with "form" as role `<form role="form login_form"></form><form role="form registration_form"></form>`:
+
+``` js
+$('@form')
+```
+
+You can combine role with other selectors, but that is not recommended:
+
+`<form class="dark" role="login_form" method="post"></form>`:
+
+``` js
+$('form.dark@login_form[method=post]')
+```

data/Rakefile

@@ -0,0 +1,34 @@
+#!/usr/bin/env rake
+require 'bundler/gem_tasks'
+require 'rake/testtask'
+require 'rdoc/task'
+require 'fileutils'
+
+Rake::TestTask.new(:test) do |test|
+  test.libs << 'lib' << 'test'
+  test.pattern = 'test/**/*_test.rb'
+  test.verbose = true
+end
+
+task :default => :test
+Rake::RDocTask.new do |rdoc|
+  version = RoleHaml::VERSION
+
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = "role-haml #{version}"
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+namespace :role do
+
+  desc 'Pull role/master subtree.'
+  task :pull do
+    system "cd role ; git checkout v#{RoleHaml::VERSION}"
+  end
+
+  desc 'Update role assets.'
+  task :update => 'role:pull' do
+    FileUtils.cp_r('role/lib/.', 'vendor/assets/javascripts')
+  end
+end

data/lib/role-haml.rb

@@ -0,0 +1,2 @@
+require 'role-haml/version'
+require 'role-haml/engine'

data/lib/role-haml/engine.rb

@@ -0,0 +1,85 @@
+module RoleHaml
+  class Engine < ::Rails::Engine
+    initializer "role-haml.register" do |app|
+      if defined?(Haml::Parser)
+        module Haml::Parser
+          DIV_ROLE = ?@
+
+          private
+
+          original_process_line_method = instance_method :process_line
+          define_method :process_line do |text, index|
+            if text[0] === DIV_ROLE
+              push div(text)
+            else
+              original_process_line_method.bind(self).call(text, index)
+            end
+          end
+
+          def self.parse_class_and_id(list)
+            attributes = {}
+            list.scan(/([#.@])([-:_a-zA-Z0-9]+)/) do |type, property|
+              case type
+              when '.'
+                if attributes['class']
+                  attributes['class'] += " "
+                else
+                  attributes['class'] = ""
+                end
+                attributes['class'] += property
+              when '#'; attributes['id'] = property
+              when '@'
+                if attributes['role']
+                  attributes['role'] += " "
+                else
+                  attributes['role'] = ""
+                end
+                attributes['role'] += property
+              end
+            end
+            attributes
+          end
+
+          def parse_tag(line)
+            raise SyntaxError.new("Invalid tag: \"#{line}\".") unless match = line.scan(/%([-:\w]+)([-:\w\.\#\@]*)(.*)/)[0]
+
+            tag_name, attributes, rest = match
+            raise SyntaxError.new("Illegal element: classes and ids must have values.") if attributes =~ /[\.#](\.|#|\z)/
+
+            new_attributes_hash = old_attributes_hash = last_line = nil
+            object_ref = "nil"
+            attributes_hashes = {}
+            while rest
+              case rest[0]
+              when ?{
+                break if old_attributes_hash
+                old_attributes_hash, rest, last_line = parse_old_attributes(rest)
+                attributes_hashes[:old] = old_attributes_hash
+              when ?(
+                break if new_attributes_hash
+                new_attributes_hash, rest, last_line = parse_new_attributes(rest)
+                attributes_hashes[:new] = new_attributes_hash
+              when ?[
+                break unless object_ref == "nil"
+                object_ref, rest = balance(rest, ?[, ?])
+              else; break
+              end
+            end
+
+            if rest
+              nuke_whitespace, action, value = rest.scan(/(<>|><|[><])?([=\/\~&!])?(.*)?/)[0]
+              nuke_whitespace ||= ''
+              nuke_outer_whitespace = nuke_whitespace.include? '>'
+              nuke_inner_whitespace = nuke_whitespace.include? '<'
+            end
+
+            value = value.to_s.strip
+            [tag_name, attributes, attributes_hashes, object_ref, nuke_outer_whitespace,
+            nuke_inner_whitespace, action, value, last_line || @index]
+          end
+
+        end
+      end
+    end
+  end
+end

data/lib/role-haml/version.rb

@@ -0,0 +1,3 @@
+module RoleHaml
+  VERSION = '1.2.1'
+end

data/role-haml.gemspec

@@ -0,0 +1,36 @@
+# -*- encoding: utf-8 -*-
+
+require File.expand_path('../lib/role-haml/version', __FILE__)
+
+Gem::Specification.new do |gem|
+  gem.name              = "role-haml"
+  gem.rubyforge_project = "role-haml"
+  gem.version           = RoleHaml::VERSION
+
+  gem.authors           = ["kossnocorp, gazay"]
+  gem.email             = "koss@nocorp.me"
+  gem.date              = "2012-03-23"
+
+  gem.description       = "Gem for jQuery plugin to provide easy way to handle DOM elements by role attribute"
+  gem.summary           = "Gem for jQuery plugin to provide easy way to handle DOM elements by role attribute"
+  gem.homepage          = "https://github.com/gazay/role-haml"
+
+  gem.executables       = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  gem.files             = `git ls-files`.split("\n")
+  gem.test_files        = `git ls-files -- {test,spec,features}/*`.split("\n")
+
+  gem.files.reject! { |fn| fn.include? "vendor/role" }
+
+  gem.licenses          = ["MIT"]
+
+  gem.require_paths     = ["lib"]
+
+  gem.rubygems_version  = "1.8.15"
+
+  gem.add_dependency "rails", ">= 3.1.0"
+
+  gem.add_development_dependency "haml", ">= 3.0.0"
+  gem.add_development_dependency "sqlite3"
+  gem.add_development_dependency "shoulda"
+  gem.add_development_dependency "bundler", ">= 1.0.0"
+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.