RubyGems - devmate - Versions diffs - 0.0.1 → 0.1.0 - Mend

devmate 0.0.1 → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (70) hide show

checksums.yaml +8 -8
data/{LICENSE.txt → MIT-LICENSE} +1 -3
data/README.rdoc +7 -0
data/Rakefile +39 -1
data/app/assets/javascripts/devmate/application.js +35 -0
data/app/assets/javascripts/devmate/noty-2.2.4/LICENSE.txt +20 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/jquery.noty.js +488 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/bottom.js +34 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/bottomCenter.js +41 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/bottomLeft.js +43 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/bottomRight.js +43 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/center.js +56 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/centerLeft.js +61 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/centerRight.js +61 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/inline.js +31 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/top.js +34 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/topCenter.js +41 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/topLeft.js +43 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/layouts/topRight.js +43 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/packaged/jquery.noty.packaged.js +1180 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/packaged/jquery.noty.packaged.min.js +1 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/promise.js +432 -0
data/app/assets/javascripts/devmate/noty-2.2.4/js/noty/themes/default.js +157 -0
data/app/assets/stylesheets/devmate/application.css +13 -0
data/app/controllers/devmate/application_controller.rb +26 -0
data/app/helpers/devmate/application_helper.rb +4 -0
data/app/views/layouts/devmate/application.html.erb +14 -0
data/config/data/quotes.json +36 -0
data/config/routes.rb +3 -0
data/lib/devmate.rb +14 -4
data/lib/devmate/engine.rb +5 -0
data/lib/devmate/version.rb +1 -1
data/lib/generators/devmate_generator.rb +27 -0
data/test/devmate_test.rb +7 -0
data/test/dummy/README.rdoc +261 -0
data/test/dummy/Rakefile +7 -0
data/test/dummy/app/assets/javascripts/application.js +15 -0
data/test/dummy/app/assets/stylesheets/application.css +13 -0
data/test/dummy/app/controllers/application_controller.rb +3 -0
data/test/dummy/app/helpers/application_helper.rb +2 -0
data/test/dummy/app/views/layouts/application.html.erb +14 -0
data/test/dummy/config.ru +4 -0
data/test/dummy/config/application.rb +59 -0
data/test/dummy/config/boot.rb +10 -0
data/test/dummy/config/database.yml +25 -0
data/test/dummy/config/environment.rb +5 -0
data/test/dummy/config/environments/development.rb +37 -0
data/test/dummy/config/environments/production.rb +67 -0
data/test/dummy/config/environments/test.rb +37 -0
data/test/dummy/config/initializers/backtrace_silencers.rb +7 -0
data/test/dummy/config/initializers/inflections.rb +15 -0
data/test/dummy/config/initializers/mime_types.rb +5 -0
data/test/dummy/config/initializers/secret_token.rb +7 -0
data/test/dummy/config/initializers/session_store.rb +8 -0
data/test/dummy/config/initializers/wrap_parameters.rb +14 -0
data/test/dummy/config/locales/en.yml +5 -0
data/test/dummy/config/routes.rb +4 -0
data/test/dummy/public/404.html +26 -0
data/test/dummy/public/422.html +26 -0
data/test/dummy/public/500.html +25 -0
data/test/dummy/public/favicon.ico +0 -0
data/test/dummy/script/rails +6 -0
data/test/functional/devmate/prompts_controller_test.rb +9 -0
data/test/integration/navigation_test.rb +10 -0
data/test/test_helper.rb +15 -0
metadata +117 -30
data/.gitignore +0 -22
data/Gemfile +0 -4
data/README.md +0 -29
data/devmate.gemspec +0 -24

data/app/assets/stylesheets/devmate/application.css ADDED

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */

data/app/controllers/devmate/application_controller.rb ADDED

@@ -0,0 +1,26 @@
+module Devmate
+  class ApplicationController < ActionController::Base
+    def fetchData
+      path = File.join(Devmate::Engine.root, 'config', 'data', 'quotes.json')
+      if File.exists?(path)
+        quotes_file = File.read(path)
+        quotes_hash = JSON.parse(quotes_file)
+        test_data = Hash[
+          :position => Devmate.position,
+          :timeout => Devmate.timeout,
+          :call_timeout => Devmate.call_timeout,
+          :maxVisible => Devmate.maxVisible,
+          :close_with => Devmate.close_with,
+          :data_count => quotes_hash.length.to_s,
+          :data => quotes_hash
+        ]
+        respond_to do |format|
+          format.json {
+            render json: test_data.to_json
+          }
+        end
+      end
+    end
+  end
+end

data/app/helpers/devmate/application_helper.rb ADDED

@@ -0,0 +1,4 @@
+module Devmate
+  module ApplicationHelper
+  end
+end

data/app/views/layouts/devmate/application.html.erb ADDED

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Devmate</title>
+  <%= stylesheet_link_tag    "devmate/application", :media => "all" %>
+  <%= javascript_include_tag "devmate/application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+<%= yield %>
+</body>
+</html>

data/config/data/quotes.json ADDED

@@ -0,0 +1,36 @@
+{
+  "1": "Just because something doesn’t do what you planned it to do doesn’t mean it’s useless ~ Thomas Edison",
+  "2": "We are stuck with technology when what we really want is just stuff that works ~ Douglas Adams!",
+  "3": "It’s supposed to be automatic, but actually you have to push this button ~ John Brunner",
+  "4": "Computers make it easier to do a lot of things, but most of the things they make it easier to do don’t need to be done ~ Andy Rooney",
+  "5": "May the source be with you",
+  "6": "Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live ~ Martin Golding",
+  "7": "When debugging, novices insert corrective code; experts remove defective code ~ Richard Pattis",
+  "8": "Any fool can write code that a computer can understand. Good programmers write code that humans can understand ~ Martin Fowler",
+  "9": "You've baked a really lovely cake, but then you've used dog shit for frosting ~ Steve Jobs",
+  "10": "Programs must be written for people to read, and only incidentally for machines to execute ~ Hal Abelson",
+  "11": "Walking on water and developing software from a specification are easy if both are frozen ~ Edward Berard",
+  "12": "Deleted code is debugged code ~ Jeff Sickel",
+  "13": "First, solve the problem. Then, write the code ~ John Johnson",
+  "14": "Computers are good at following instructions, but not at reading your mind ~ Donald Knuth",
+  "15": "The computing scientist’s main challenge is not to get confused by the complexities of his own making ~ E. W. Dijkstra",
+  "16": "Controlling complexity is the essence of computer programming ~ Brian Kernighan",
+  "17": "Beauty is more important in computing than anywhere else in technology because software is so complicated. Beauty is the ultimate defence against complexity ~ David Gelernter",
+  "18": "Life is too short to run proprietary software ~ Bdale Garbee",
+  "19": "Measuring programming progress by lines of code is like measuring aircraft building progress by weight ~ Bill Gates",
+  "20": "A language that doesn’t have everything is actually easier to program in than some that do ~ Dennis M. Ritchie",
+  "21": "Compatibility means deliberately repeating other people’s mistakes ~ David Wheeler",
+  "22": "Code never lies, comments sometimes do ~ Ron Jeffries",
+  "23": "I am rarely happier than when spending an entire day programming my computer to perform automatically a task that would otherwise take me a good ten seconds to do by hand ~ Douglas Adams, Last Chance to See",
+  "24": "When I am working on a problem I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong ~ R. Buckminster Fuller",
+  "25": "Theory is when you know something, but it doesn’t work. Practice is when something works, but you don’t know why. Programmers combine theory and practice: Nothing works and they don’t know why ~ Stewart Brand",
+  "26": "Good code is short, simple, and symmetrical – the challenge is figuring out how to get there ~ Sean Parent",
+  "27": "The only sin is to make a choice without knowing you are making one ~ Jonathan Shewchuk",
+  "28": "It is a painful thing to look at your own trouble and know that you yourself and no one else has made it ~ Sophocles, Ajax",
+  "29": "I object to doing things that computers can do ~ Olin Shivers",
+  "30": "If it doesn’t work, it doesn’t matter how fast it doesn’t work ~ Mich Ravera",
+  "31": "No code is faster than no code ~ Merb Motto",
+  "32": "So much complexity in software comes from trying to make one thing do two things ~ Ryan Singer",
+  "33": "Normal people believe that if it ain’t broke, don’t fix it. Engineers believe that if it ain’t broke, it doesn’t have enough features yet ~ Scott Adams",
+  "34": "If you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime ~ David Leinweber"
+}

data/config/routes.rb ADDED

@@ -0,0 +1,3 @@
+Devmate::Engine.routes.draw do
+  get 'fetchData' => 'application#fetchData'
+end

data/lib/devmate.rb CHANGED

@@ -1,9 +1,19 @@
-require "devmate/version"
+require "devmate/engine"
 module Devmate
-  def self.prompt
-    p 'Hello'
+  class << self
+    mattr_accessor :position, :timeout, :maxVisible, :close_with, :call_timeout
+    self.position = 'topRight'
+    self.timeout = '60000'
+    self.maxVisible = '1'
+    self.close_with = 'click'
+    self.call_timeout = '1200000'
+  end
+  # this function maps the vars from your app into your engine
+  def self.setup(&block)
+    yield self
   end
 end

data/lib/devmate/engine.rb ADDED

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

data/lib/devmate/version.rb CHANGED

@@ -1,3 +1,3 @@
 module Devmate
-  VERSION = "0.0.1"
+  VERSION = "0.1.0"
 end

data/lib/generators/devmate_generator.rb ADDED

@@ -0,0 +1,27 @@
+class DevmateGenerator < Rails::Generators::Base
+  desc 'This generator creates an initializer file at config/initializers for devmate'
+  def create_initializer_file
+    create_file 'config/initializers/devmate.rb',
+"Devmate.setup do |config|
+    # Where would ypu like the notification to appear?
+    # [top, topLeft, topCenter, topRight, centerLeft, center, centerRight, bottomleft, bottomCenter, bottomRight, bottom]
+    config.position = 'topRight'
+    # How long before its dismissed
+    config.timeout = 5000
+    # Max Visible
+    config.maxVisible = 1
+    # Call every n seconds
+    config.call_timeout = 8000
+    # close with
+    config.close_with = 'click'
+  end
+end "
+  end
+end

data/test/devmate_test.rb ADDED

@@ -0,0 +1,7 @@
+require 'test_helper'
+class DevmateTest < ActiveSupport::TestCase
+  test "truth" do
+    assert_kind_of Module, Devmate
+  end
+end

data/test/dummy/README.rdoc ADDED

@@ -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
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- 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.

data/test/dummy/Rakefile ADDED

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+require File.expand_path('../config/application', __FILE__)
+Dummy::Application.load_tasks