Project

loquacious

0.01
No commit activity in last 3 years
No release in over 3 years
Descriptive configuration files for Ruby written in Ruby. Loquacious provides a very open configuration system written in ruby and descriptions for each configuration attribute. The attributes and descriptions can be iterated over allowing for helpful information about those attributes to be displayed to the user. In the simple case we have a file something like Loquacious.configuration_for('app') { name 'value', :desc => "Defines the name" foo 'bar', :desc => "FooBar" id 42, :desc => "Ara T. Howard" } Which can be loaded via the standard Ruby loading mechanisms Kernel.load 'config/app.rb' The attributes and their descriptions can be printed by using a Help object help = Loquacious.help_for('app') help.show :values => true # show the values for the attributes, too Descriptions are optional, and configurations can be nested arbitrarily deep. Loquacious.configuration_for('nested') { desc "The outermost level" a { desc "One more level in" b { desc "Finally, a real value" c 'value' } } } config = Loquacious.configuration_for('nested') p config.a.b.c #=> "value" And as you can see, descriptions can either be given inline after the value or they can appear above the attribute and value on their own line.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.6
 Project Readme

Loquacious¶ ↑

by Tim Pease
http://rubygems.org/gems/loquacious

DESCRIPTION:¶ ↑

Descriptive configuration files for Ruby written in Ruby.

Loquacious provides a very open configuration system written in ruby and descriptions for each configuration attribute. The attributes and descriptions can be iterated over allowing for helpful information about those attributes to be displayed to the user.

In the simple case we have a file something like

Loquacious.configuration_for('app') {
  name 'value', :desc => "Defines the name"
  foo  'bar',   :desc => "FooBar"
  id   42,      :desc => "Ara T. Howard"
}

Which can be loaded via the standard Ruby loading mechanisms

Kernel.load 'config/app.rb'

The attributes and their descriptions can be printed by using a Help object

help = Loquacious.help_for('app')
help.show :values => true        # show the values for the attributes, too

Descriptions are optional, and configurations can be nested arbitrarily deep.

Loquacious.configuration_for('nested') {
  desc "The outermost level"
  a {
    desc "One more level in"
    b {
      desc "Finally, a real value"
      c 'value'
    }
  }
}

config = Loquacious.configuration_for('nested')

p config.a.b.c  #=> "value"

And as you can see, descriptions can either be given inline after the value or they can appear above the attribute and value on their own line.

INSTALL:¶ ↑

  • sudo gem install loquacious

EXAMPLES:¶ ↑

example/simple.rb¶ ↑

# A simple example that configures three options (a b c) along with
# descriptions for each option. The descriptions along with the
# values for the configuration options are printed to the terminal.

require 'loquacious'
include Loquacious

Configuration.for(:simple) {
  desc 'Your first configuration option'
  a "value for 'a'"

  desc 'To be or not to be'
  b "William Shakespeare"

  desc 'The underpinings of Ruby'
  c 42
}

help = Configuration.help_for :simple
help.show :values => true

====== output ======
 Your first configuration option
  - a => "value for 'a'"

 To be or not to be
  - b => "William Shakespeare"

 The underpinings of Ruby
  - c => 42

examples/nested.rb¶ ↑

# Here we show how to used nested configuration options by taking a subset
# of some common Rails configuration options. Also, descriptions can be give
# before the option or they can be given inline using Ruby hash notation. If
# both are present, then the inline description takes precedence.
#
# Multiline descriptions are provided using Ruby heredocs. Leading
# whitespace is stripped and line breaks are preserved when descriptions
# are printed using the help object.

require 'loquacious'
include Loquacious

Configuration.for(:nested) {
  root_path '.', :desc => "The application's base directory."

  desc "Configuration options for ActiveRecord::Base."
  active_record {
    colorize_logging true, :desc => <<-__
      Determines whether to use ANSI codes to colorize the logging statements committed
      by the connection adapter. These colors make it much easier to overview things
      during debugging (when used through a reader like +tail+ and on a black background),
      but may complicate matters if you use software like syslog. This is true, by default.
    __

    default_timezone :local, :desc => <<-__
      Determines whether to use Time.local (using :local) or Time.utc (using :utc)
      when pulling dates and times from the database. This is set to :local by default.
    __
  }

  log_level :info, :desc => <<-__
    The log level to use for the default Rails logger. In production mode,
    this defaults to :info. In development mode, it defaults to :debug.
  __

  log_path 'log/development.log', :desc => <<-__
    The path to the log file to use. Defaults to log/\#{environment}.log
    (e.g. log/development.log or log/production.log).
  __
}

help = Configuration.help_for :nested
help.show :values => true

====== output ======
 Configuration options for ActiveRecord::Base.
  - active_record

 Determines whether to use ANSI codes to colorize the logging statements committed
 by the connection adapter. These colors make it much easier to overview things
 during debugging (when used through a reader like +tail+ and on a black background),
 but may complicate matters if you use software like syslog. This is true, by default.
  - active_record.colorize_logging => true

 Determines whether to use Time.local (using :local) or Time.utc (using :utc)
 when pulling dates and times from the database. This is set to :local by default.
  - active_record.default_timezone => :local

 The log level to use for the default Rails logger. In production mode,
 this defaults to :info. In development mode, it defaults to :debug.
  - log_level                      => :info

 The path to the log file to use. Defaults to log/#{environment}.log
 (e.g. log/development.log or log/production.log).
  - log_path                       => "log/development.log"

 The application's base directory.
  - root_path                      => "."

examples/gutters.rb¶ ↑

# Using Ruby heredocs for descriptions, the Loquacious configuration will
# strip out leading whitespace but preserve line breaks. Gutter lines can be
# used to mark where leading whitespace should be preserved. This is useful
# is you need to provide example code in your descriptions.

require 'loquacious'
include Loquacious

Configuration.for(:gutters) {
  log_path "log/development.log", :desc => <<-__
    The path to the log file to use. Defaults to log/\#{environment}.log
    (e.g. log/development.log or log/production.log).
    |
    |  config.log_path = File.join(ROOT, "log", "\#{environment}.log
    |
  __

  log_level :warn, :desc => <<-__
    |The log level to use for the default Rails logger. In production mode,
    |this defaults to :info. In development mode, it defaults to :debug.
    |
    |  config.log_level = 'debug'
    |  config.log_level = :warn
    |
  __
}

help = Configuration.help_for :gutters
help.show :values => true

====== output ======
 The log level to use for the default Rails logger. In production mode,
 this defaults to :info. In development mode, it defaults to :debug.

   config.log_level = 'debug'
   config.log_level = :warn

  - log_level => :warn

 The path to the log file to use. Defaults to log/#{environment}.log
 (e.g. log/development.log or log/production.log).

   config.log_path = File.join(ROOT, "log", "#{environment}.log

  - log_path  => "log/development.log"

LICENSE:¶ ↑

(The MIT License)

Copyright © 2009-2011

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.