midas-guilded 0.2.7 → 0.2.8

data/History.txt

@@ -1,3 +1,9 @@
+= 0.2.8 2009-06-12
+
+* Removed some code from the InactiveRecord:Base extension for human attrbiute hint that returns unless 
+  table_exists? as this does not make any sense for InactiveRecord.
+
+
 = 0.2.7 2009-06-10
 
 * Changed the BrowserDetector to need to be instantiated to use.  No longer just static methods.

data/README.rdoc

@@ -66,6 +66,12 @@ The Guilded gem contains the framework to build Guilded components.
   these is found, it includes it, otherwise, it includes the version specified by the author in the view helper.  This is usually 
   an unpacked version of the file.
 
+=== Additional common utilities
+* Determine the browser making a request with the BrowserDetector class and related view helpers.
+* Extends ActiveRecord to have a attr_human_hint method.  This method works similar to the attr_human_name method except a hint
+  to use on forms, etc is being set.
+* Extends InactiveRecord (http://github.com/midas/inactive_record/tree/master) to include the attr_human_hint method.
+
 
 == GUILDED COMPONENT PROJECTS
 

data/guilded.gemspec

@@ -2,11 +2,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{guilded}
-  s.version = "0.2.7"
+  s.version = "0.2.8"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["C. Jason Harrelson (midas)"]
-  s.date = %q{2009-06-10}
+  s.date = %q{2009-06-12}
   s.description = %q{Guilded is a framework for building web based components centered around current web standards and best practices. The current  framework is written in ruby, but could be ported to other languages.  Guilded intends to provide a toolset for creating and consuming reusable web components.  Currently, this problem domain is filled with JavaScript frameworks.  These frameworks are wonderful and work very well.   However, they do not degrade gracefully and  are not accessible.  Guilded seeks to provide the same level of "componentization" and ease of use without sacrificing degradability  and accessibility.  Guilded will achieve these goals by applying each technology at our disposal to do what it was intended.    XHTML will be employed for content.  CSS used for layout and styling.  Behavior will be added to a component with JavaScript  through progressive enhancement.  The user will have the best experience with a Guilded component when CSS and JavaScript are  enabled in their browser, but will still be able to use the component when CSS and JavaScript are disabled.   Guilded will use jQuery as it's base JavaScript framework.  jQuery was chosen because it lends itself to progressive enhancement due to the way it was authored.  In addition, the tight integration of jQuery's selectors with CSS selectors is also highly  desirable.  When authoring a Guilded component, it is encouraged to write the behavior code as a jQuery plugin.  This will  allow the jQuery plugin to be used outside of the Guilded project, if desired.  Guilded also seeks to provide a standardized CSS framework for creating layouts that are reusable and predictable.  Guilded will utilize the currently existing RubyGems system to package its components.  A new Guilded component will be packaged  in a Gem and have a dependency on the Guilded gem.  The Guilded gem contains the framework to build Guilded components.}
   s.email = ["jason@lookforwardenterprises.com"]
   s.extra_rdoc_files = ["History.txt", "Manifest.txt", "PostInstall.txt", "README.rdoc"]

data/lib/guilded.rb

@@ -73,7 +73,7 @@ require 'guilded/rails/inactive_record/human_attribute_hint'
 #   <%= g_load_alerter :skin => 'blueish', :id => 'load_alerter' %>
 #
 module Guilded
-  VERSION = '0.2.7'
+  VERSION = '0.2.8'
 end
 
 ActionView::Base.send( :include, Guilded::Rails::ViewHelpers ) if defined?( ActionView )

data/lib/guilded/rails/inactive_record/human_attribute_hint.rb

@@ -5,7 +5,7 @@ module InactiveRecord
       # converted to 'Num employees' normally using <tt>human_attribute_name</tt>.  More descriptive text can be set. Example:
       #   attr_human_name 'num_employees' => 'Number of employees'
       def attr_human_hint(attributes) # :nodoc:
-        return unless table_exists?
+        #return unless table_exists?
 
         attributes.stringify_keys!
         write_inheritable_hash("attr_human_hint", attributes || {})

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: midas-guilded
 version: !ruby/object:Gem::Version 
-  version: 0.2.7
+  version: 0.2.8
 platform: ruby
 authors: 
 - C. Jason Harrelson (midas)
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-06-10 00:00:00 -07:00
+date: 2009-06-12 00:00:00 -07:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency