hubspot 0.0.2 → 1.0.0

data/app/models/hubspot/keyword.rb

@@ -1,49 +0,0 @@
-module Hubspot
-  
-  # Finds and updates leads
-  #
-  # Finds:
-  # Hubspot::Keyword.find :all
-  # Hubspot::Keyword.find <GUID>  
-  #
-  # Creates:
-  # Hubspot::Keyword.create({ :keyword => { :keyword => 'sleutel' }})
-  # Note that you should pass in the root element 'keyword', as activeresource removes the root element name when it matches the object name
-  class Keyword < Hubspot::Base
-    self.site = 'https://api.hubapi.com/keywords/v1'
-    
-    schema do
-      string 'keyword'
-    end
-    
-    alias_attribute :id, :keyword_guid
-    
-    class << self
-      def instantiate_collection(collection, prefix_options = {})
-        collection = collection['keywords'] if collection.is_a?(Hash)
-        collection.collect! { |record| instantiate_record(record, prefix_options) }
-      end
-              
-      def collection_path(prefix_options = {}, query_options = nil)
-        prefix_options, query_options = split_options(prefix_options) if query_options.nil?
-        "#{prefix(prefix_options)}#{collection_name}#{query_string(query_options)}"
-      end        
-    end
-    
-    protected
-    
-    # Override to support the object returned after create
-    def load_attributes_from_response(response)
-      if (response_code_allows_body?(response.code) &&
-          (response['Content-Length'].nil? || response['Content-Length'] != "0") &&
-          !response.body.nil? && response.body.strip.size > 0)
-          
-        response_data = self.class.format.decode(response.body)
-        load(response_data.is_a?(Array) ? response_data.first : response_data, true)
-        @persisted = true
-      end
-    end    
-  
-  end
-  
-end

data/app/models/hubspot/lead.rb

@@ -1,26 +0,0 @@
-module Hubspot
-  
-  # Finds and updates leads
-  #
-  # Finds:
-  # Hubspot::Lead.find :all, :params => { :search => 'test' }
-  # Hubspot::Lead.find <GUID>  
-  #
-  # Updates:
-  # lead.firstName = 'Reinier'; lead.save!
-  # lead.update_attributes(:firstName => 'Reinier')
-  class Lead < Hubspot::Base
-    self.site = 'https://api.hubapi.com/leads/v1'
-    
-    schema do
-      string 'guid', 'salutation', 'firstName', 'lastName', 'email', 'website', 'company'
-      string 'address', 'state', 'city', 'zip', 'country'
-      string 'phone', 'fax', 'userToken', 'industry', 'jobTitle', 'twitterHandle', 'ipAddress'
-      float  'score'
-    end
-    
-    alias_attribute :id, :guid
-  
-  end
-  
-end

data/app/models/hubspot/performable/event.rb

@@ -1,67 +0,0 @@
-require 'uri'  
-require 'net/http'
-    
-module Hubspot
-  module Performable
-  
-    # The Event class can be used to record events using the Performable API.
-    # Example: Hubspot::Event.new('event_32145').record!
-    # The response will always be a 1X1 transparent GIF, this is because the HTTP API can be used via an HTML image tag as well :)
-    class Event < Struct.new(:event_id, :performed_at, :completed_at, :url, :ip, :value, :order_id, :custom_parameters)
-      include ActiveModel::Validations
-    
-      validates :event_id, :presence => true
-      
-      # _a - Your Performable API key. (Your API Key can be found in Account Settings within your Performable account.)
-      # _n - The EVENT_ID of the event you want to record. You can get an event id in two ways:
-      # Log into your Performable account, click Setup, and then click on the event that you wish to record. Finally, click the configuration link to bring up a dialog which shows you the event id.
-      # Use your own unique label as the id, and Performable will automatically generate the corresponding event in your account. You can rename it from within the app later if you'd like.
-      # There are also optional parameters:
-      # 
-      # _t - The timestamp of the event (in seconds as a UTC Unix epoch). By default this is ignored - it is used only to help make requests unique and the time that our servers receive the event is used for the timestamp of the event.
-      # _d - If equal to the string true, implies that the timestamp sent with this event should be used as the time of completion for this event. The timestamp will be ignored if it represents a future date (within some reason), or is more than a few years old. Servers generating timestamps should use some mechanism (like NTP) for syncing clocks to a reasonable standard. The API expects timestamps are in seconds, but may detect timestamps in milliseconds and attempt to resolve them to seconds.
-      # _l (that's a lowercase L) - The URL that triggered this event.
-      # _ip - The IP address of the user who completed this event. This is useful if you want Performable to assign location data to a user based on their IP address.
-      #
-      # If you are recording an e-commerce transaction you may use any of the following parameters:
-      # 
-      # value - A monetary value associated with this event, such as the purchase amount or expected conversion value. This value should be a number with no formatting other than a period representing the decimal point (if necessary.)
-      # order_id - A unique identifier associated with the order or transaction. This is used to make sure this transaction is not counted more than once.    
-      PARAMETER_MAPPING = { :event_id => '_n', :performed_at => '_t', :completed_at => '_d', :url => '_l', :ip => '_ip', :value => 'value', :order_id => 'order_id'}
-
-      def record!
-        return false unless valid?
-     
-        uri.query = to_param      
-        http = Net::HTTP.new(uri.host, uri.port)
-        http.set_debug_output(Hubspot.config.debug_http_output) if Hubspot.config.debug_http_output
-            
-        return http.request_get(uri.request_uri).code.to_i
-      end
-    
-      # Records, but doesn't raise an error when the record fails and returns flase instead.
-      def record
-        record! rescue false
-      end    
-    
-      # Sets the Performable API URI
-      def uri
-        @uri ||= URI('http://analytics.performable.com/v1/event')            
-      end
-    
-      # Converts the event to encoded form data.
-      def to_param
-        parameters = PARAMETER_MAPPING.keys.inject({}) do |hash, parameter| 
-          parameter_value = send(parameter)
-          hash[PARAMETER_MAPPING[parameter]] = parameter_value if parameter_value.present?
-          hash
-        end
-
-        parameters.merge!(custom_parameters) if custom_parameters
-        parameters.merge!('_a' => Hubspot.config.hubspot_key)        
-        parameters.to_param      
-      end
-
-    end
-  end
-end

data/lib/hubspot/action_controller_extensions.rb

@@ -1,15 +0,0 @@
-module Hubspot
-  module ActionControllerExtensions
-    extend ActiveSupport::Concern
-    
-    included do
-      helper_method :hubspot_user_token
-    end
-    
-    # Returns the user token (GUID). This can be used to check whether the current user has been recorded as a Lead.
-    def hubspot_user_token
-      @hubspot_user_token ||= cookies[:hubspotutk]
-    end
-    
-  end
-end

data/lib/hubspot/engine.rb

@@ -1,30 +0,0 @@
-module Hubspot
-  
-  class Engine < Rails::Engine
-    
-    # The domain of your Hubspot site, which is used in the javascript tracker code
-    config.hubspot_site         = 'demo.app11.hubspot.com'
-    
-    # The access token for authenticating to several Hubspot services, e.g. 'demooooo-oooo-oooo-oooo-oooooooooooo'
-    config.hubspot_access_token = nil
-    
-    # Your API key
-    config.hubspot_key          = 'demo'
-    
-    # Your Portal ID
-    config.hubspot_portal_id    = '62515'
-    
-    # Enables/disables logging of HTTP requests and response.
-    # false - Disables debugging
-    # STDOUT - logs to STDOUT. Of course you can specify any IO object you want.
-    config.debug_http_output    = false # STDOUT
-    
-    ActiveSupport.on_load(:action_controller) do
-      include Hubspot::ActionControllerExtensions
-    end
-    
-  end
-
-  def self.config; Hubspot::Engine.config; end    
-  
-end

data/lib/tasks/hubspot_tasks.rake

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

data/test/dummy/README.rdoc

@@ -1,261 +0,0 @@
-== 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.