refinerycms-settings 0.9.9.3 → 0.9.9.4

Sign up to get free protection for your applications and to get access to all the features.
data/license.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # MIT License
2
2
 
3
- Copyright (c) 2005-2010 [Resolve Digital](http://www.resolvedigital.com)
3
+ Copyright (c) 2005-2011 [Resolve Digital](http://www.resolvedigital.com)
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining a copy
6
6
  of this software and associated documentation files (the "Software"), to deal
@@ -2,10 +2,10 @@
2
2
 
3
3
  Gem::Specification.new do |s|
4
4
  s.name = %q{refinerycms-settings}
5
- s.version = %q{0.9.9.3}
5
+ s.version = %q{0.9.9.4}
6
6
  s.summary = %q{Settings engine for Refinery CMS}
7
7
  s.description = %q{The default settings engine that is required by Refinery CMS core. Adds programmer creatable, user editable settings for each engine.}
8
- s.date = %q{2011-02-17}
8
+ s.date = %q{2011-02-24}
9
9
  s.email = %q{info@refinerycms.com}
10
10
  s.homepage = %q{http://refinerycms.com}
11
11
  s.rubyforge_project = %q{refinerycms}
@@ -73,12 +73,11 @@ Gem::Specification.new do |s|
73
73
  'lib/generators/refinerycms_settings_generator.rb',
74
74
  'lib/refinerycms-settings.rb',
75
75
  'license.md',
76
- 'readme.md',
77
76
  'refinerycms-settings.gemspec',
78
77
  'spec',
79
78
  'spec/models',
80
79
  'spec/models/refinery_setting_spec.rb'
81
80
  ]
82
81
 
83
- s.add_dependency 'refinerycms-base', '~> 0.9.9.3'
82
+ s.add_dependency 'refinerycms-base', '~> 0.9.9.4'
84
83
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: refinerycms-settings
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.9.9.3
5
+ version: 0.9.9.4
6
6
  platform: ruby
7
7
  authors:
8
8
  - Resolve Digital
@@ -13,7 +13,7 @@ autorequire:
13
13
  bindir: bin
14
14
  cert_chain: []
15
15
 
16
- date: 2011-02-17 00:00:00 +13:00
16
+ date: 2011-02-24 00:00:00 +13:00
17
17
  default_executable:
18
18
  dependencies:
19
19
  - !ruby/object:Gem::Dependency
@@ -24,7 +24,7 @@ dependencies:
24
24
  requirements:
25
25
  - - ~>
26
26
  - !ruby/object:Gem::Version
27
- version: 0.9.9.3
27
+ version: 0.9.9.4
28
28
  type: :runtime
29
29
  version_requirements: *id001
30
30
  description: The default settings engine that is required by Refinery CMS core. Adds programmer creatable, user editable settings for each engine.
@@ -77,7 +77,6 @@ files:
77
77
  - lib/generators/refinerycms_settings_generator.rb
78
78
  - lib/refinerycms-settings.rb
79
79
  - license.md
80
- - readme.md
81
80
  - refinerycms-settings.gemspec
82
81
  - spec/models/refinery_setting_spec.rb
83
82
  has_rdoc: true
data/readme.md DELETED
@@ -1,55 +0,0 @@
1
- # Settings
2
-
3
- ![Refinery Settings](http://refinerycms.com/system/images/0000/0666/settings.png)
4
-
5
- ## About
6
-
7
- Refinery comes out of the box with a full settings area that is populated with smart defaults to avoid configuration.
8
-
9
- ## Settings of Interest
10
-
11
- Here's an overview of what comes out of the box
12
-
13
- ### Google Analytics
14
-
15
- Just edit the setting called "Analytics Page Code" and enter just your account number. It will look something like this
16
-
17
- UA-XXXXXX-X
18
-
19
- Save this and Refinery will automatically note you have set the page code up and start rendering it on the front end so tracking can begin.
20
-
21
- ### Firebug Lite Support
22
-
23
- [Firebug lite](http://getfirebug.com/lite) is fantastic for debugging your site in Internet Explorer.
24
-
25
- Set the 'Show Firebug Lite' setting to ``true`` and you'll be able to debug your views in Internet Explorer in no time.
26
-
27
- _Note: you'll want to turn this off once your site is live_
28
-
29
- ### Use Google Ajax Libraries
30
-
31
- This setting will automatically change your AJAX libraries to use the ones delivered by Google's CDN (Content Delivery Network) which means your Javascript will be cached and delivery as quickly as possible.
32
-
33
- ## How do I Make my Own Settings?
34
-
35
- Settings can be really useful, especially when you have custom display logic or new plugins that need to behave in different ways.
36
-
37
- To best explain how settings work let's use an example. Say you have a client who has a display in a local trade show every year and 2 months before the trade show they want to display a little banner in the header of all pages.
38
-
39
- But once the trade show is finished, the client needs to be able to hide it again until next year. This is what my ``application.html.erb`` file might look like:
40
-
41
- ...
42
- <div id='header'>
43
- <h1>My Company</h1>
44
-
45
- <% if RefinerySetting.find_or_set(:show_trade_show_banner, false) %>
46
- <%= image_tag ('trade-show-banner.jpg') %>
47
- <% end %>
48
- </div>
49
- ...
50
-
51
- The following will automatically create a new Refinery setting called "show_trade_show_banner" and default it to ``false``. If that setting already exists, it just reads in what the current value is.
52
-
53
- So as you can see this is quite clever because you can quickly define new settings and their defaults right from the view as you need them.
54
-
55
- This setting would then show up in the backend in the 'Settings' area where the client could change the value as their trade show approaches. Easy as pie!