# -*- coding: utf-8 -*- # Configures your navigation SimpleNavigation::Configuration.run do |navigation| # Specify a custom renderer if needed. # The default renderer is SimpleNavigation::Renderer::List which renders HTML lists. # The renderer can also be specified as option in the render_navigation call. # navigation.renderer = Your::Custom::Renderer # Specify the class that will be applied to active navigation items. Defaults to 'selected' navigation.selected_class = 'current' # Specify the class that will be applied to the current leaf of # active navigation items. Defaults to 'simple-navigation-active-leaf' # navigation.active_leaf_class = 'your_active_leaf_class' # Item keys are normally added to list items as id. # This setting turns that off # navigation.autogenerate_item_ids = false # You can override the default logic that is used to autogenerate the item ids. # To do this, define a Proc which takes the key of the current item as argument. # The example below would add a prefix to each key. # navigation.id_generator = Proc.new {|key| "my-prefix-#{key}"} # If you need to add custom html around item names, you can define a proc that will be called with the name you pass in to the navigation. # The example below shows how to wrap items spans. # navigation.name_generator = Proc.new {|name| "#{name}"} # The auto highlight feature is turned on by default. # This turns it off globally (for the whole plugin) # navigation.auto_highlight = false # Define the primary navigation navigation.items do |primary| # Add an item to the primary navigation. The following params apply: # key - a symbol which uniquely defines your navigation item in the scope of the primary_navigation # name - will be displayed in the rendered navigation. This can also be a call to your I18n-framework. # url - the address that the generated item links to. You can also use url_helpers (named routes, restful routes helper, url_for etc.) # options - can be used to specify attributes that will be included in the rendered navigation item (e.g. id, class etc.) # some special options that can be set: # :if - Specifies a proc to call to determine if the item should # be rendered (e.g. :if => Proc.new { current_user.admin? }). The # proc should evaluate to a true or false value and is evaluated in the context of the view. # :unless - Specifies a proc to call to determine if the item should not # be rendered (e.g. :unless => Proc.new { current_user.admin? }). The # proc should evaluate to a true or false value and is evaluated in the context of the view. # :method - Specifies the http-method for the generated link - default is :get. # :highlights_on - if autohighlighting is turned off and/or you want to explicitly specify # when the item should be highlighted, you can set a regexp which is matched # against the current URI. You may also use a proc, or the symbol :subpath. # # primary.item :key_1, 'name', url, options # Add an item which has a sub navigation (same params, but with block) # primary.item :key_2, 'name', url, options do |sub_nav| # Add an item to the sub navigation (same params again) # sub_nav.item :key_2_1, 'name', url, options # end # You can also specify a condition-proc that needs to be fullfilled to display an item. # Conditions are part of the options. They are evaluated in the context of the views, # thus you can use all the methods and vars you have available in the views. # primary.item :key_3, 'Admin', url, :class => 'special', :if => Proc.new { current_user.admin? } # primary.item :key_4, 'Account', url, :unless => Proc.new { logged_in? } # you can also specify a css id or class to attach to this particular level # works for all levels of the menu primary.dom_id = 'tabs' primary.dom_class = 'header-item' # You can turn off auto highlighting for a specific level # primary.auto_highlight = false primary.item :insights, 'Insights', category_path(:id => 'youth-marketing-insights'), :highlights_on => :subpath, :class => 'has_nested' do |secondary| secondary.item :insights_articles, 'List Articles', category_articles_path(:category_id => 'youth-marketing-insights') secondary.item :new_insights_article, 'New Article', new_category_article_path(:category_id => 'youth-marketing-insights') secondary.item :insights_reports, 'List Reports', category_reports_path(:category_id => 'youth-marketing-insights') secondary.item :new_insights_report, 'New Report', new_category_report_path(:category_id => 'youth-marketing-insights') end primary.item :insights, 'News', category_path(:id => 'company-news'), :highlights_on => :subpath, :class => 'has_nested' do |secondary| secondary.item :news_news, 'List News', category_news_index_path(:category_id => 'company-news') secondary.item :new_news_news, 'New News', new_category_news_path(:category_id => 'company-news') end primary.item :channels, 'Channels', channels_path primary.item :tags, 'Tags', tags_path primary.item :logout, 'Logout', main_app.destroy_user_session_path, :method => :delete end end