RubyGems - collection-json-browser - Versions diffs - 0.0.1 - Mend

collection-json-browser 0.0.1

Files changed (110) hide show

data/app/controllers/collection_json_browser/application_controller.rb ADDED Viewed

@@ -0,0 +1,4 @@
+module CollectionJsonBrowser
+  class ApplicationController < ActionController::Base
+  end
+end

data/app/controllers/collection_json_browser/home_controller.rb ADDED Viewed

@@ -0,0 +1,7 @@
+module CollectionJsonBrowser
+  class HomeController < ApplicationController
+    def index
+    end
+  end
+end

data/app/helpers/collection_json_browser/application_helper.rb ADDED Viewed

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

data/app/views/collection_json_browser/home/index.html ADDED Viewed

@@ -0,0 +1,118 @@
+<body ng-controller="ApiController">
+  <div class="container-fluid">
+    <div class="row-fluid">
+      <div class="span6">
+        <h2>Path</h2>
+        <div class="location thumbnail">
+          <label for='href'>href: </label>
+          <input id='href' value="{{collection.href}}">
+        </div>
+        <div ng-show="collection.template">
+          <h2>Template</h2>
+          <div class="template thumbnail">
+            <form class="form-horizontal" ng-submit="post()">
+              <fieldset class="control-group" ng-repeat="field in collection.template.data">
+                <label class="control-label" for='{{field.name}}'>{{field.name}}</label>
+                <div class="controls">
+                  <input id='{{field.name}}' value="{{field.value}}" ng-model='field.value'>
+                </div>
+              </fieldset>
+              <div class="control-group">
+                <div class="controls">
+                  <button type="submit" class="btn">Submit</button>
+                </div>
+              </div>
+            </form>
+          </div>
+        </div>
+        <div ng-show="collection.links">
+          <h2>Links & Images</h2>
+          <div class="links thumbnail">
+            <table class="table table-hover table-striped">
+              <tr>
+                <th>rel</th>
+                <th>name</th>
+                <th>prompt</th>
+                <th>get</th>
+              </tr>
+              <tr ng-include src="'links.html'" ng-repeat="link in collection.links">
+              </tr>
+            </table>
+          </div>
+        </div>
+        <div ng-show="collection.items">
+          <h2>Items</h2>
+          <div class="items thumbnail">
+            <ol>
+              <li ng-repeat="item in collection.items" class="item">
+                <dl>
+                  <dt>
+                    rel
+                  </dt>
+                  <dd>
+                    {{item.rel}}
+                  </dd>
+                  <dt>
+                    prompt
+                  </dt>
+                  <dd>
+                    {{item.prompt}}
+                  </dd>
+                  <dt>
+                    get
+                  </dt>
+                  <dd>
+                    <a href="" ng-click="goTo(item.href)">{{item.href}}</a>
+                  </dd>
+                </dl>
+                <table class="table table-hover table-striped">
+                  <tr>
+                    <th>name</th>
+                    <th>prompt</th>
+                    <th>value</th>
+                  </tr>
+                  <tr class="data" ng-repeat="data in item.data">
+                    <td>{{data.name}}</td>
+                    <td>{{data.prompt}}</td>
+                    <td>{{data.value}}</td>
+                  </tr>
+                </table>
+                <div ng-show="item.links">
+                  <h3>Links & Images</h3>
+                  <div class="item-links thumbnail">
+                    <table class="table table-hover table-striped">
+                      <tr>
+                        <th>rel</th>
+                        <th>name</th>
+                        <th>prompt</th>
+                        <th>get</th>
+                      </tr>
+                      <tr ng-include src="'links.html'" ng-repeat="link in item.links">
+                      </tr>
+                    </table>
+                  </div>
+                </div>
+              </li>
+            </ol>
+          </div>
+        </div>
+      </div>
+      <div class="span6">
+        <h2>Status</h2>
+        <div class="status">
+          {{status}}
+        </div>
+        <h2>Response body</h2>
+        <pre class="raw">{{raw}}</pre>
+      </div>
+    </div>
+  </div>
+</body>

data/app/views/layouts/collection_json_browser/application.html.erb ADDED Viewed

@@ -0,0 +1,13 @@
+<!DOCTYPE html>
+<html ng-app>
+  <head>
+    <meta charset="utf-8">
+    <title>Collection+JSON Browser</title>
+    <%= javascript_include_tag "collection_json_browser/application" %>
+    <%= stylesheet_link_tag    "collection_json_browser/application", :media => "all" %>
+    <%= csrf_meta_tags %>
+  </head>
+  <%= yield %>
+</html>

data/config/routes.rb ADDED Viewed

@@ -0,0 +1,3 @@
+CollectionJsonBrowser::Engine.routes.draw do
+  get '/', to: "home#index", as: :root
+end

data/lib/collection-json-browser.rb ADDED Viewed

@@ -0,0 +1,4 @@
+require "collection-json-browser/engine"
+module CollectionJsonBrowser
+end

data/lib/collection-json-browser/engine.rb ADDED Viewed

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

data/lib/collection-json-browser/version.rb ADDED Viewed

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

data/lib/tasks/collection-json-browser_tasks.rake ADDED Viewed

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

data/test/collection-json-browser_test.rb ADDED Viewed

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

data/test/dummy/README.rdoc ADDED Viewed

@@ -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.