realtime-validations 0.0.1

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2011 YOURNAME
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,3 @@
+= RealtimeValidations
+
+This project rocks and uses MIT-LICENSE.

data/Rakefile

@@ -0,0 +1,38 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'RealtimeValidations'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+
+task :default => :test

data/app/assets/javascripts/realtime_validations/core.js

@@ -0,0 +1,80 @@
+$(document).ready(rt_validations_bind_fields);
+
+function rt_validations_bind_fields()
+{
+  $('form[validation="true"] :input').each(function(i, field) {
+    rt_validations_bind_field(field);
+  });
+}
+
+function rt_validations_bind_field(field)
+{
+  var field_to_validate = $('#' + field.id);
+  field_to_validate.blur(rt_validations_bind_field_on_blur);
+}
+
+function rt_validations_bind_field_on_blur()
+{
+  var field = $(this);
+  var form_to_validate = $('form[validation="true"]');
+  var validation_path = rt_validations_path(form_to_validate);
+  var model = form_to_validate.attr('model');
+  var field_name = field.attr('name');
+  var matched = field_name.match(/(\w+)\[(\w+)_confirmation\]/);
+  var data_to_send = null;
+  var current_value = field.val();
+
+  if (matched) {
+    var field_canonical_namespace = matched[1];
+    var field_canonical_name = matched[2];
+    var validation_value = $('#' + field_canonical_namespace + '_' + field_canonical_name).val();
+    data_to_send = { field: field_name.replace("_confirmation", ""), value: current_value,
+                     validates: validation_value, model: model };
+  } else {
+    data_to_send = { field: field_name, value: current_value, model: model };
+  }
+
+  var custom_data_to_send = rt_validations_custom_fields();
+  $.extend(data_to_send, custom_data_to_send);
+
+  $.post(validation_path, data_to_send, function(data) {
+    if ($.isEmptyObject(data.errors)) {
+      rt_validations_hide_warning_message(field);
+    } else {
+      rt_validations_show_warning_message(field, data.errors);
+    }
+  });
+}
+
+function rt_validations_path(form)
+{
+  return '/validations' + form.attr('action');
+}
+
+function rt_validations_show_warning_message(field, errors)
+{
+  var validation_errors = field.attr('validation-errors');
+  if (!$.isEmptyObject(validation_errors) && (validation_errors.toString() == errors.toString())) {
+    return;
+  }
+  field.attr('valid', false);
+  field.attr('validation-errors', errors);
+  if ($('#' + field.attr('id') + '_error').length) {
+    $('#' + field.attr('id') + '_error').remove();
+  }
+  field.parent().append('<div style="display: none;" id="' + field.attr('id') + '_error" class="field-error">'
+                          + errors.join(', ') +
+                          '<div class="field-error-arrow-border"></div> \
+                           <div class="field-error-arrow"></div>        \
+                         </div>');
+  $('#' + field.attr('id') + '_error').fadeIn('slow');
+}
+
+function rt_validations_hide_warning_message(field)
+{
+  field.attr('valid', true);
+  field.attr('validation-errors', null);
+  $('#' + field.attr('id') + '_error').fadeOut('slow', function() {
+    $(this).remove();
+  });
+}

data/app/assets/stylesheets/realtime_validations/core.css

@@ -0,0 +1,40 @@
+div.field-error {
+  display: inline-block;
+  position: relative;
+  border: 2px solid #666666;
+  line-height: 1.3em;
+  margin-left: 10px;
+  margin-top:-53px;
+  margin-bottom: 11px;
+  width: 200px;
+  padding: 10px;
+  text-align:center;
+  -moz-border-radius: 10px;
+  -webkit-border-radius: 10px;
+  -moz-box-shadow:0 0 5px #888888;
+  -webkit-box-shadow:0 0 5px #888888;
+  background: -webkit-gradient(linear, left -200%, left 200%, from(#FFFFFF), to(#FF0000));
+  background: -moz-linear-gradient(#FFFFFF -200%, #FF0000 200%);
+}
+
+div.field-error-arrow-border {
+  border-color: transparent #666666 transparent transparent;
+  border-style: solid;
+  border-width: 10px;
+  height: 0;
+  width: 0;
+  position: absolute;
+  top: 10px;
+  left: -20px;
+}
+
+div.field-error-arrow {
+  border-color: transparent transparent transparent transparent;
+  border-style: solid;
+  border-width: 10px;
+  height: 0;
+  width: 0;
+  position: absolute;
+  top: 10px;
+  left: -17px;
+}

data/app/controllers/realtime_validations/validations_controller.rb

@@ -0,0 +1,50 @@
+module RealtimeValidations
+
+  class ValidationsController < ApplicationController
+
+    include Controller
+
+    def validate
+      model_name = params[:model]
+      request.path =~ /^\/validations(.+)$/
+      request_path = $1
+      args = remove_unused_args Rails.application.routes.recognize_path(request_path)
+      field = params[:field]
+      field =~ /^[^\[]+\[(\w+)\]$/
+      field = $1
+      value = params[:value]
+      validates = params[:validates]
+      if args.has_key? :id
+        model = Object.const_get("#{model_name}".camelize.to_sym).find args[:id]
+        args.delete :id
+      else
+        model = Object.const_get("#{model_name}".camelize.to_sym).new
+      end
+      args.each do |key, value|
+        full_key = key.to_s.singularize
+        model.send "#{full_key}=", value if model.respond_to? full_key.to_sym
+      end
+      model.send "#{field}=", value
+      model.send "#{field}_confirmation=", validates if validates
+      before_model_validation model if respond_to? :before_model_validation
+      begin
+        model.valid?
+      rescue
+      end
+      errors = model.errors[field.to_sym].uniq
+      respond_to do |format|
+        format.json { render :json => { :field => params[:field],
+                                        :errors => errors } }
+      end
+    end
+
+    private
+
+    def remove_unused_args(args)
+      [:action, :controller].each { |key| args.delete key }
+      args
+    end
+
+  end
+
+end

data/config/initializers/form_validated_for.rb

@@ -0,0 +1,25 @@
+module ActionView
+  module Helpers
+    module FormHelper
+
+      def form_validated_for(record, options = {}, &proc)
+        options[:html] ||= {}
+        options[:html][:validation] = true
+
+        case record
+        when String, Symbol
+          object_name = record
+          object      = nil
+        else
+          object      = record.is_a?(Array) ? record.last : record
+          object_name = options[:as] || ActiveModel::Naming.param_key(object)
+        end
+
+        options[:html][:model] = object_name
+
+        form_for record, options, &proc
+      end
+
+    end
+  end
+end

data/config/routes.rb

@@ -0,0 +1,7 @@
+Rails.application.routes.draw do
+
+  scope :module => :realtime_validations do
+    match '/validations/*args(.:format)', :to => 'validations#validate', :via => :post
+  end
+
+end

data/lib/generators/realtime_validations/realtime_validations_generator.rb

@@ -0,0 +1,12 @@
+require 'rails/generators'
+
+class RealtimeValidationsGenerator < Rails::Generators::NamedBase
+
+  source_root File.join(File.dirname(__FILE__), 'templates')
+
+  def copy_initializer_file
+    copy_file 'initializer.rb', 'config/initializers/realtime_validations_initializer.rb'
+    copy_file 'realtime_validations.js', 'app/assets/javascripts/realtime_validations.js'
+  end
+
+end

data/lib/generators/realtime_validations/templates/initializer.rb

@@ -0,0 +1,13 @@
+module RealtimeValidations
+
+  module Controller
+
+    def self.included(base)
+    end
+
+    def before_model_validation(model)
+    end
+
+  end
+
+end

data/lib/generators/realtime_validations/templates/realtime_validations.js

@@ -0,0 +1,3 @@
+function rt_validations_custom_fields() {
+  return {};
+}

data/lib/realtime-validations/version.rb

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

data/lib/realtime-validations.rb

@@ -0,0 +1,6 @@
+module RealtimeValidations
+
+  class RealtimeValidations < Rails::Engine
+  end
+
+end

data/lib/tasks/realtime-validations_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :realtime-validations 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.