Motivation

Simple DSL for use in classes to motivate a user towards a goal. An example goal might be "Complete Profile", or "Setup Project".

This was heavily inspired by progression.

I switched primarily because I wanted to use specific classes rather than inject into an existing model namespace, and extend the DSL some.

Add this line to your application's Gemfile:

gem 'motivation'

And then execute:

$ bundle

Or install it yourself as:

$ gem install motivation

Create a motivational class and include Motivation.

require "motivation"

Profile = Struct.new(:twitter_name, :age, :tweets) do
  attr_accessor :cached_tweets_count
end

class ProfileMotivation
  include Motivation

  # Aliases profile to subject for clarity in steps
  subject :profile

  # Provides an #applies? check.  use this block to
  # house logic if you want to selectively apply the
  # motivation.  Note this doesn't impact checks at
  # all, it's so you have a central place for checking
  # if you wish.  true by default
  applies { profile.age <= 14 }

  # Create a simple check.  This defines the predicate `#setup_twitter?`
  check(:setup_twitter) { profile.twitter_name.to_s.length > 0 }

  # Define a step by name then create a check
  step :enter_age
  check { profile.age.to_i > 0 }

  # Define a completetion block.  This is useful if you your
  # check is heavy and you want to use a cached result.  This
  # will define a method `#complete_tweets_added
  step :tweets_added
  check { profile.cached_tweets_count.to_i > 0 || profile.tweets.length > 0 }
  complete { profile.cached_tweets_count = profile.tweets.length.to_i }
end

profile = Profile.new(nil, 42, [1,2,3])
motivation = ProfileMotivation.new(profile)
motivation.setup_twitter? #=> false
profile.twitter_name = "JohnDoe"
motivation.setup_twitter? #=> true

motivation.complete_tweets_added

Note that the check and complete blocks will not tolerate early returns, you will get a LocalJumpError. If you want to simplify your DSL definitions, you can just call methods, including privates, in your ProfileMotivation class itself.

You can also iterate over checks for a motivation instance:

motivation.each_check do |check|
  puts check.name
  puts check.completed?
end

You can get the next incomplete check, this is useful if you want to render a message in a header, for instance.

motivation.next_check

Motivation checks are wrapped to provide a tranlation key suitable for use with i18n. Note it currently does not include i18n, you can pass the generated keys straight to your helper (such as t in Rails views).

motivation.next_check.translation_key #=> "motivations.profile.setup_twitter.default"

The key format is motivations.motivation_subject.step_name.[default|complete]. Note you can call default_translation_key as a shortcut to always grab the default translation key. This is useful if you want to always have the same messaging regardless of completion status. If you wish to provide alternate messaging based on completion, fill our your local data with both default and complete keys.

Here's an example locale that would match the motivation key structure:

en:
  motivations:
    project:
      name:
        default: "Add a project name"
        complete: "Your project is named!"
      support_email:
        default: "Setup a support email address"
        complete: "Your support email is ready to go"
      users_added:
        default: "Now go sign up some users"
        complete: "Awesome, you've got users!"

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request