scheduled_resource 0.0.1

data/lib/z_time_label_day.rb

@@ -0,0 +1,23 @@
+# -*- coding: utf-8 -*-
+# 
+class ZTimeLabelDay < ZTimeLabel
+
+  def self.get_timeblocks(id, t1, t2, inc)
+    (super).each do |b|
+      b.title = b.starttime.strftime "%a, %b %e"
+      b.css_classes = 'ZTimeHeaderDayRow '
+    end
+  end
+
+
+  def self.end_for_start( t )
+    (t.end_of_day + 1).beginning_of_day  # 0.00001 or whatever
+  end
+
+  # t is a TimeWithZone or similar
+  def self.floor(t)
+    t.beginning_of_day
+  end
+
+end
+

data/lib/z_time_label_hour.rb

@@ -0,0 +1,26 @@
+# -*- coding: utf-8 -*-
+# 
+class ZTimeLabelHour < ZTimeLabel
+
+  def self.get_timeblocks(id, t1, t2, inc)
+    (super).each do |b|
+      t = b.starttime
+      b.title = t.strftime('%I:%M').sub(/^0/, '')     # '%I'
+      b.css_classes = "ZTimeHeaderHourRow #{daylight_class(t)} "
+    end
+  end
+
+  def self.daylight_class(t)
+    (6...18).include?(t.hour) ? 'dayTimeblock' : 'niteTimeblock'
+  end
+
+  def self.end_for_start( t )
+    floor(t) + 15.minutes
+  end
+
+  # t is a TimeWithZone or similar
+  def self.floor(t)
+    t.change(min: (t.min / 15) * 15)
+  end
+
+end

data/scheduled_resource.gemspec

@@ -0,0 +1,25 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'scheduled_resource/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "scheduled_resource"
+  spec.version       = ScheduledResource::VERSION
+  spec.authors       = ["Mike Cannon"]
+  spec.email         = ["michael.j.cannon@gmail.com"]
+  spec.summary       = %q{Help display how something is used over time.}
+  spec.description   = %Q{== README.md:\n#{IO.read 'README.md'}}
+  spec.homepage      = ""
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0")
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_dependency "rails"
+  spec.add_dependency "coffee-rails"
+  spec.add_development_dependency "bundler", "~> 1.7"
+  spec.add_development_dependency "rake", "~> 10.0"
+end

metadata

@@ -0,0 +1,178 @@
+--- !ruby/object:Gem::Specification
+name: scheduled_resource
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Mike Cannon
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2015-02-18 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: coffee-rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.7'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.7'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+description: "== README.md:\n#ScheduledResource\n\nThis gem is for displaying how
+  things are used\nover time -- a schedule for a set of resources.  It\nprovides a
+  way to describe what is being displayed,\nalong with utilities and protocols to
+  connect them:\n\n - Configuration (specification and management),\n - Query interfaces
+  (a REST-like API and internal protocols to query the models), and\n - A basic Rails
+  controller implementation.\n\nSo we have a way to configure the schedule, internal\nmethods
+  to generate the data, and a way to retrieve\ndata from the client.  But the gem
+  is largely\nview-framework agnostic.  We could use a variety of\nclient-side packages
+  or even more traditional Rails\nview templates to generate HTML.\n\nIn any case,
+  to get a the most from a display like this\nwe need some client-side code.  The
+  gem includes\nclient-side modules to:\n\n - Manage <b>time and display geometries</b>
+  with \"infinite\" scroll along the time axis.\n - <b>Format display cells</b> in
+  ways specific to the resource models.\n - <b>Update text justification</b> as the
+  display is scrolled horizontally.\n\n\n## Configuration Management\n\nA **scheduled
+  resource** is something that can be\nused for one thing at a time.  Say \"Rocky
+  & Bullwinkle\"\nis on channel 3 from 10am to 11am on Saturday.  Then\n'channel 3'
+  is the <u>resource</u> and that showing of\nthe is a <u>resource-use block</u>.
+  \ Resources and \nuse-blocks are typically Rails models.  Each resource\nand its
+  use-blocks get one row in the display.  That\nrow has a label to the left with some
+  timespan visible\non the rest of the row.\n\nThe <b>ScheduledResource</b> class
+  manages resource and\nuse-block class names, id's and labels for a schedule.\nA
+  ScheduledResource instance ties together:\n\n 1. A resource class (eg TvStation),\n
+  2. An id (a channel number in this example), and\n 3. Strings and other assets that
+  will go into the DOM.\n\nThe id is used to\n  - select a resource <em>instance</em>
+  and\n  - select instances of the <em>resource use block</em> class (eg Program instances).\n\nThe
+  id <em>could</em> be a database id but more\noften is something a little more suited
+  to human use\nin the configuration.  In any case it is used by model\nclass method\n<tt>(resource_use_block_class).get_all_blocks()</tt>\nto
+  select the right use-blocks for the resource.\nA resource class name and id are
+  are joined with\na '_' to form a tag that also serves as an id for the DOM.\n\nSomething
+  else you would expect see in a schedule\nwould be headers and labels -- perhaps
+  one row with\nthe date and another row with the hour.  Headers and\nlabels also
+  fit the model of resources and use_blocks.\nBasic timezone-aware classes (ZTime*)
+  for those are\nincluded in this gem.\n\n\n### Configuration File\n\nThe schedule
+  configuration comes from\n<tt>config/resource_schedule.yml</tt> which has\nthree
+  top-level sections:\n\n- ResourceKinds:  A hash where the key is a Resource and
+  the value is a UseBlock. (Both are class names),\n- Resources:  A list where each
+  item is a Resource Class followed by one or more resource ids, and\n- visibleTime:
+  \ The visible timespan of the schedule in seconds.\n\nThe example file <tt>config/resource_schedule.yml</tt>\n(installed
+  when you run <tt>schedulize</tt>) should be\nenough to display a two-row schedule
+  with just the date\nabove and the hour below.  Of course you can monkey-patch\nor
+  subclass these classes for your own needs.\n\n\n### The schedule API\n\nThe endpoint
+  uses parameters <tt>t1</tt> and\n<tt>t2</tt> to specify a time interval for the
+  request.\nA third parameter <tt>inc</tt> allows an initial time\nwindow to be expanded
+  without repeating blocks that\nspan those boundaries.  The time parameters _plus
+  the\nconfigured resources_ define the data to be returned.\n\n\n### More About Configuration
+  Management\n\nOnce the configuration yaml is loaded that data is\nmaintained in
+  the session structure.  Of course having\na single configuration file limits the
+  application's\nusefulness.  A more general approach would be to\nhave a user model
+  with login and configuration would\nbe associated with the user.\n\n\n\n\n\n\n##
+  Installation\n\nAdd this line to your application's Gemfile:\n\n```ruby\ngem 'scheduled_resource'\n```\n\nAnd
+  then execute:\n\n    $ bundle\n\nOr install it yourself as:\n\n    $ gem install
+  scheduled_resource\n\n## Usage\n\nTo Do: Write usage instructions here\n\n## Contributing\n\n1.
+  Fork it ( https://github.com/emeyekayee/scheduled_resource/fork )\n2. Create your
+  feature branch (`git checkout -b my-new-feature`)\n3. Commit your changes (`git
+  commit -am 'Add some feature'`)\n4. Push to the branch (`git push origin my-new-feature`)\n5.
+  Create a new Pull Request\n"
+email:
+- michael.j.cannon@gmail.com
+executables:
+- schedulize
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- Gemfile
+- LICENSE
+- README.md
+- Rakefile
+- bin/schedulize
+- lib/assets/javascripts/blank.jpg
+- lib/assets/javascripts/justify_tweaks.js
+- lib/assets/javascripts/time_pix.js.coffee
+- lib/assets/javascripts/use_block.js.coffee
+- lib/assets/stylesheets/scheduled_resource.css.scss
+- lib/scheduled_resource.rb
+- lib/scheduled_resource/helper.rb
+- lib/scheduled_resource/resource_use_block.rb
+- lib/scheduled_resource/version.rb
+- lib/z_time_header.rb
+- lib/z_time_header_day.rb
+- lib/z_time_header_hour.rb
+- lib/z_time_label.rb
+- lib/z_time_label_day.rb
+- lib/z_time_label_hour.rb
+- scheduled_resource.gemspec
+homepage: ''
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.2.2
+signing_key: 
+specification_version: 4
+summary: Help display how something is used over time.
+test_files: []