BigW Consortium Gitlab

Commit 15d54b29 by Christian Höltje

design pages now uses the COLOR_SCHEMES

This unifies the code color-scheme code and makes adding new schemes a little easier.
parent 336750c9
.black .highlight {
.dark .highlight {
background-color: #333;
......
......@@ -4,12 +4,23 @@ require 'uri'
module ApplicationHelper
COLOR_SCHEMES = {
1 => 'white',
2 => 'black',
2 => 'dark',
3 => 'solarized-dark',
4 => 'monokai',
}
COLOR_SCHEMES.default = 'white'
# Helper method to access the COLOR_SCHEMES
#
# The keys are the `color_scheme_ids`
# The values are the `name` of the scheme.
#
# The preview images are `name-scheme-preview.png`
# The stylesheets should use the css class `.name`
def color_schemes
COLOR_SCHEMES.freeze
end
# Check if a particular controller is the current one
#
# args - One or more controller names to check
......
......@@ -40,23 +40,9 @@
%i.icon-ok
Saved
.code_highlight_opts
- color_schemes.each do |color_scheme_id, color_scheme|
= label_tag do
.prev
= image_tag "white.png"
= f.radio_button :color_scheme_id, 1
White
= label_tag do
.prev
= image_tag "dark.png"
= f.radio_button :color_scheme_id, 2
Dark
= label_tag do
.prev
= image_tag "solarized_dark.png"
= f.radio_button :color_scheme_id, 3
Solarized Dark
= label_tag do
.prev
= image_tag "monokai.png"
= f.radio_button :color_scheme_id, 4
Monokai
= image_tag "#{color_scheme}-scheme-preview.png"
= f.radio_button :color_scheme_id, color_scheme_id
= color_scheme.gsub(/[-_]+/, ' ').humanize
......@@ -74,7 +74,7 @@ class Profile < Spinach::FeatureSteps
When "I change my code preview theme" do
within '.code-preview-theme' do
choose "Solarized Dark"
choose "Solarized dark"
end
end
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment