hookercookerman-amee 0.0.2

data/History.txt

@@ -0,0 +1 @@
+There is none

data/LICENSE.txt

@@ -0,0 +1,20 @@
+Copyright (c) 2009 Richard Hooker
+
+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/Manifest.txt

@@ -0,0 +1,79 @@
+History.txt
+LICENSE.txt
+Manifest.txt
+README.rdoc
+Rakefile
+features/config.feature
+features/data/data_category.feature
+features/data/data_item.feature
+features/data/data_item_value.feature
+features/data/drill_down.feature
+features/development.feature
+features/profile/create.profile.feature
+features/profile/create.profile_item.feature
+features/profile/delete.profile.feature
+features/profile/delete.profile_item.feature
+features/profile/get.profile.feature
+features/profile/profile_category.feature
+features/profile/profile_item.feature
+features/profile/profiles.feature
+features/profile/update.profile_item.feature
+features/session/reauthenticate.feature
+features/step_definitions/amee_steps.rb
+features/step_definitions/common_steps.rb
+features/step_definitions/config_steps.rb
+features/step_definitions/data_steps.rb
+features/step_definitions/profile_category_steps.rb
+features/step_definitions/profile_item_steps.rb
+features/step_definitions/profile_steps.rb
+features/support/amee/auth/response.json
+features/support/amee/data.json
+features/support/amee/data/transport/car/generic.json
+features/support/amee/data/transport/car/generic/drill.json
+features/support/amee/data/transport/car/generic/drill?fuel=diesel&size=large.json
+features/support/amee/data/transport/car/generic/drill?fuel=diesel.json
+features/support/amee/data/transport/plane/generic.json
+features/support/amee/data/transport/plane/generic/FFC7A05D54AD.json
+features/support/amee/data/transport/plane/generic/FFC7A05D54AD/kgCO2PerPassengerJourney.json
+features/support/amee/data_category.json
+features/support/amee/data_category_with_data_items.json
+features/support/amee/profiles.json
+features/support/amee/profiles/155DD3C63646/transport/motorcycle/generic/D47C465B8157.json
+features/support/amee/profiles/155DD3C63646/transport/motorcycle/generic/D47C465B8157?distance=400&representation=true.json
+features/support/amee/profiles/48B97680BCCF/home/energy/quantity/response.json
+features/support/amee/profiles/7C7D68C2A7CD/home.json
+features/support/amee/profiles/BB1BDB4FDD77/home/energy/quantity/920B54ED665B.json
+features/support/amee/profiles/E0BCB3704D15.json
+features/support/amee/profiles/E0BCB3704D15/Business.json
+features/support/amee/profiles/profile.json
+features/support/env.rb
+init.rb
+lib/amee.rb
+lib/amee/config.rb
+lib/amee/data_api/data_category.rb
+lib/amee/data_api/data_item.rb
+lib/amee/data_api/data_item_value.rb
+lib/amee/data_api/drill_down.rb
+lib/amee/data_api/item_definition.rb
+lib/amee/data_api/item_value_definition.rb
+lib/amee/data_api/value_definition.rb
+lib/amee/logging.rb
+lib/amee/model.rb
+lib/amee/parser.rb
+lib/amee/profile_api/profile.rb
+lib/amee/profile_api/profile_category.rb
+lib/amee/profile_api/profile_item.rb
+lib/amee/service.rb
+lib/amee/session.rb
+lib/amee/utils/string.rb
+script/console
+script/destroy
+script/generate
+script/txt2html
+spec/amee_spec.rb
+spec/service_spec.rb
+spec/session_spec.rb
+spec/spec.opts
+spec/spec_helper.rb
+tasks/rspec.rake
+tasks/yard.rake

data/README.rdoc

@@ -0,0 +1,33 @@
+= Amee (Lets Cut Co2) By D50 
+
+= Docs 
+  
+  These are on the way; this is very early release; However have a look at the cucumber features
+  you should be able so see that most bases have been covered; Basically the more we use this 
+  the more docs there will be
+  
+= Usage (More to come; If you are lucky and example rails app)
+  
+  There is a config where login, cache and logging settings can be applied have a look at the config
+  model to see how one should use that.
+  
+  Create a session ie @session = Amee::Session.create("blar", "blar")
+  And then use the session to get, put, post and delete on what you required from amee; 
+  there are a set number of operations that are available to you currently but more will 
+  be added
+  
+  Some objects say like data_categories can be lazy loaded so you can do method calls like
+  
+  data_category = @session.get_data_category("/data/home/appliances")
+  fridge = data_category.data_categories.first
+  
+  if you wanted to know the data_categories for fridge just call data_categories on fridge it
+  will populated the fridge category automagically;
+  
+  Cache - Simple to Start (using Moneta)
+  Therefore if u wish you can choose your cache store even memcache via leveraging Moneta 
+
+= TODOS
+
+  Pagination (should be simple enough just hook into will_paginate collections)
+  Other stuff when start to use amee api fully 

data/Rakefile

@@ -0,0 +1,29 @@
+%w[rubygems rake rake/clean fileutils newgem rubigen].each { |f| require f }
+require File.dirname(__FILE__) + '/lib/amee'
+
+# Generate all the Rake tasks
+# Run 'rake -T' to see list of generated tasks (from gem root directory)
+$hoe = Hoe.new('amee', Amee::VERSION) do |p|
+  p.developer('Richard Hooker', 'richard.hooker@dynamic50.com')
+  p.changes              = p.paragraphs_of("History.txt", 0..1).join("\n\n")
+  p.rubyforge_name       = p.name # TODO this is default value
+  # p.extra_deps         = [
+  #   ['activesupport','>= 2.0.2'],
+  # ]
+  p.extra_dev_deps = [
+    ['newgem', ">= #{::Newgem::VERSION}"]
+  ]
+  
+  p.clean_globs |= %w[**/.DS_Store tmp *.log]
+  path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}"
+  p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc')
+  p.rsync_args = '-av --delete --ignore-errors'
+end
+
+require 'newgem/tasks' # load /tasks/*.rake
+Dir['tasks/**/*.rake'].each { |t| load t }
+
+
+
+# TODO - want other tests/tasks run by default? Add them to the list
+task :default => [:spec, :features]

data/features/config.feature

@@ -0,0 +1,22 @@
+Feature: Amee can be configured
+
+  As a ruby developer
+  I want to set an Amee config 
+  So that so Amee can run under a certain configurations
+  
+  Scenario: defaults should be available if no config has been set
+    When I do not create a config
+    
+    Then the amee config: "server" should be: "stage.amee.com"
+    And the amee config: "cache_store" should be: "Moneta::Memory"
+    And the amee config: "cache" should be: "true"
+    
+  Scenario: server should be changed if I set a config with new server
+    When I set the: "server" on the amee config with: "prod.amee.com"
+
+    Then the amee config: "server" should be: "prod.amee.com"
+    And the amee config: "cache_store" should be: "Moneta::Memory"
+    And the amee config: "cache" should be: "true"
+  
+  
+  

data/features/data/data_category.feature

@@ -0,0 +1,26 @@
+Feature: Get Amee Category
+  In order to gain access to data information
+  As a amee developer
+  I want to be able to get amee categories
+  
+  Scenario: Get Amee category with path /data
+    Given I have a valid amee session
+    When I ask the session for: get_data_category with path: "/data"
+    
+    Then the data category should have: "path" with: ""
+    And the data category should have: "name" with: "Root"
+    And the data category should have: "uid" with: "CD310BEBAC52"
+    And the data category's data_items should be nil
+    And the data category's data_categories should not be nil
+    
+  Scenario: Get Amee category with path /data/transport/plane/generic
+    Given I have a valid amee session
+    When I ask the session for: get_data_category with path: "/data/transport/plane/generic"
+
+    Then the data category should have: "path" with: "generic"
+    And the data category should have: "resource_path" with: "/transport/plane/generic"
+    And the data category should have: "name" with: "Generic"
+    And the data category should have: "uid" with: "FBA97B70DBDF"
+    
+    And the data category's data_items should not be empty
+    And the data category's data_categories should not be empty

data/features/data/data_item.feature

@@ -0,0 +1,19 @@
+Feature: Get Amee DataItem
+  In order to gain access to data_item information so I can make loads of money from making
+  In order carbon calculators
+  As a amee developer
+  I want to be able to get amee data items
+  
+  
+  Scenario: Get Amee Date Item with path /data/transport/plane/generic/FFC7A05D54AD
+    Given I have a valid amee session
+    When I ask the session for: get_data_item with path: "/data/transport/plane/generic/FFC7A05D54AD"
+    
+    Then the data item should have: "path" with: ""
+    And the data item should have: "name" with: "FFC7A05D54AD"
+    And the data item should have: "uid" with: "FFC7A05D54AD"
+    And the data item's item_values should not be nil
+    And the data item's choices should not be nil
+    
+    And the data item's item_definition: drill_down should be "type,size"
+    And the data item's item_definition: name should be "Plane Generic"

data/features/data/data_item_value.feature

@@ -0,0 +1,17 @@
+Feature: Get Amee DataItemValue
+  In order to gain access to data_item_value information so I can make loads of money from making
+  In order carbon calculators
+  As a amee developer
+  I want to be able to get amee data item value
+  
+  
+  Scenario: Get Amee Date Item with path /data/transport/plane/generic/FFC7A05D54AD/kgCO2PerPassengerJourney
+    Given I have a valid amee session
+    When I ask the session for: get_data_item_value with path: "/data/transport/plane/generic/FFC7A05D54AD/kgCO2PerPassengerJourney"
+    
+    Then the data item value should have: "path" with: "kgCO2PerPassengerJourney"
+    And the data item value should have: "name" with: "kgCO2 Per Passenger Journey"
+    And the data item value should have: "uid" with: "C32B6E2EDCB0"
+    
+    And the data item value's item_value_definition: uid should be "653828811D42" 
+    And the data item value's item_value_definition: name should be "kgCO2 Per Passenger Journey"

data/features/data/drill_down.feature

@@ -0,0 +1,48 @@
+Feature: Get Amee Drill Down
+  In order to gain the correct access to a data item
+  As a amee developer
+  I want to be able to get amee drill down
+  
+  Scenario: get a drill down for data_category with path /data/transport/car/generic
+    Given I have a valid amee session
+    
+    When I ask the session for: get_data_category with path: "/data/transport/car/generic"
+    And I drill down with params: ""
+    
+    Then the drill down should have: "choice_name" with: "fuel"
+    And the drill down's choices should not be empty
+    And the drill down's selections should be empty
+    And the drill down data category's should have: "uid" with: "87E55DA88017"
+    And the drill down data category's should have: "name" with: "Generic"
+    And the drill down data category's should have: "path" with: "generic"
+    
+  Scenario: get a drill down for data_category with path /data/transport/car/generic
+    Given I have a valid amee session
+
+    When I ask the session for: get_data_category with path: "/data/transport/car/generic"
+    And I drill down with params: "?fuel=diesel"
+
+    Then the drill down should have: "choice_name" with: "size"
+    And the drill down's choices should not be empty
+    And the drill down's selections should not be empty
+    And the drill down data category's should have: "uid" with: "87E55DA88017"
+    And the drill down data category's should have: "name" with: "Generic"
+    And the drill down data category's should have: "path" with: "generic"
+
+  Scenario: get a drill down for data_category with path /data/transport/car/generic
+    Given I have a valid amee session
+
+    When I ask the session for: get_data_category with path: "/data/transport/car/generic"
+    And I drill down with params: "?fuel=diesel&size=large"
+
+    Then the drill down should have: "choice_name" with: "uid"
+    And the drill down should have: "data_item_uid" with: "4F6CBCEE95F7"
+    And the drill down should be uid_found
+    And the drill down's choices should not be empty
+    And the drill down's selections should not be empty
+    And the drill down data category's should have: "uid" with: "87E55DA88017"
+    And the drill down data category's should have: "name" with: "Generic"
+    And the drill down data category's should have: "path" with: "generic"
+
+    
+    

data/features/development.feature

@@ -0,0 +1,13 @@
+Feature: Development processes of newgem itself (rake tasks)
+
+  As a Newgem maintainer or contributor
+  I want rake tasks to maintain and release the gem
+  So that I can spend time on the tests and code, and not excessive time on maintenance processes
+    
+  Scenario: Generate RubyGem
+    Given this project is active project folder
+    And 'pkg' folder is deleted
+    When task 'rake gem' is invoked
+    Then folder 'pkg' is created
+    And file with name matching 'pkg/*.gem' is created else you should run "rake manifest" to fix this
+    And gem spec key 'rdoc_options' contains /--mainREADME.rdoc/

data/features/profile/create.profile.feature

@@ -0,0 +1,15 @@
+Feature: Creating a Profile
+  In order to keep a container for an object | user for calculating co2 emissions
+  As a amee developer
+  I want to be alble to create a profile
+  
+  
+  Scenario: Create a amee profile
+    Given I have a valid amee session
+    When I create an amee profile
+    Then I should have a valid amee profile
+  
+  
+  
+
+  

data/features/profile/create.profile_item.feature

@@ -0,0 +1,12 @@
+Feature: Create Amee Profile Item
+  In order to add co2 data that then can be used to calculate cos2 emission
+  As a amee developer
+  I want to be able to be albe to create profile data items
+  
+  Scenario: Create Amee profile item with path /profiles/48B97680BCCF/home/energy/quantity
+    Given I have a valid amee session
+    
+    # representation=full&energyConsumption=10&energyConsumptionUnit=kWh&dataItemUid=66056991EE23&energyConsumptionPerUnit=month&name=representation
+    When I create a profile item with uid: "48B97680BEGG" the path: "/profiles/48B97680BCCF/home/energy/quantity"
+    
+    Then the location of the new should be: "whatever"

data/features/profile/delete.profile.feature

@@ -0,0 +1,12 @@
+Feature: Deleting a Profile
+  In order to make sure we can delete stale data
+  As a amee developer
+  I want to be able to delete a profile
+  
+  Scenario: Delete an amee profile
+    Given I have a valid amee session
+    When I create an amee profile
+    When I delete that amme profile
+    
+    Then the profile should no longer exist
+  

data/features/profile/delete.profile_item.feature

@@ -0,0 +1,13 @@
+Feature: Deleting a Profile Item
+  In order to make sure we can delete stale profile items
+  As a amee developer
+  I want to be able to delete a profile item
+  
+  Scenario: Delete an amee profile
+    Given I have a valid amee session
+    And I profile exists with path "/profiles/155DD3C63646/transport/motorcycle/generic/D47C465B8157"
+    
+    When I delete the profile item
+    
+    Then the profile item should no longer exist
+  

data/features/profile/get.profile.feature

@@ -0,0 +1,13 @@
+Feature: Get Amee Profiles
+  In order to gain access to profile information
+  As a amee developer
+  I want to be able to get an amee profile
+  
+  Scenario: Get Amee profile
+    Given I have a valid amee session
+    When I ask the session for: profile with: "E0BCB3704D15"
+    
+    Then the amee profile should have: "uid" with: "E0BCB3704D15"
+    And the amee profile should have: "name" with: "E0BCB3704D15"
+    And the amee profile should have: "path" with: "E0BCB3704D15"
+    And the amee profile profile_categories should not be empty

data/features/profile/profile_category.feature

@@ -0,0 +1,14 @@
+Feature: Get Amee Profile Category
+  In order to gain access to profile data category information
+  As a amee developer
+  I want to be able to get profile data categories
+  
+  Scenario: Get Amee profile category with path /profiles/E0BCB3704D15/Business
+    Given I have a valid amee session
+    When I ask the session for: get_profile_category with path: "/profiles/E0BCB3704D15/business"
+    
+    Then the profile category should have: "total_amount_per_month" with: "0"
+    And the profile category should have: "resource_path" with: "/business"
+    And the profile category's profile_items should not be nil
+    And the profile category's profile_categories should not be nil
+    And the profile category's data_category should not be nil

data/features/profile/profile_item.feature

@@ -0,0 +1,15 @@
+Feature: Getting Amee Profile Item
+  In order to gain access to profile item information which means we can keep
+  In order co2 histroy and calcuations and profit big time
+  As a amee developer
+  I want to be able to get profile items
+  
+  Scenario: Get Amee profile item with path /profiles/BB1BDB4FDD77/home/energy/quantity/920B54ED665B
+    Given I have a valid amee session
+    When I ask the session for: get_profile_item with path: "/profiles/BB1BDB4FDD77/home/energy/quantity/920B54ED665B"
+    
+    Then the profile item should have: "amount_per_month" with: "2.055"
+    And the profile item should have: "resource_path" with: "/home/energy/quantity/920B54ED665B"
+    And the profile item should have: "valid_from" with: "20090301"
+    And the profile item should have: "end" with: "false"
+    And the profile item's item_values should not be nil

data/features/profile/profiles.feature

@@ -0,0 +1,15 @@
+Feature: Get Amee Profiles
+  In order to gain access to profile information
+  As a amee developer
+  I want to be able to get amee profiles
+  
+  Scenario: Get Amee profiles
+    Given I have a valid amee session
+    When I ask the session for: profiles
+    Then there should be an amee profile with the uid of "B28A58B0E243"
+    And each amee profile should have a path, name, created, modified and uid
+  
+  
+  
+
+