masterview_plugin_generator 0.3.2 → 0.3.3

data/masterview_plugin_generator.rb

@@ -1,4 +1,4 @@
-# Generator to generate small init.rb plugin which is used in 
+# Generator to generate small init.rb plugin which is used in
 # conjunction with the masterview gem
 class MasterviewPluginGenerator < Rails::Generator::Base
   def initialize(runtime_args, runtime_options = {})
@@ -9,6 +9,8 @@ class MasterviewPluginGenerator < Rails::Generator::Base
     record do |m|
       m.directory 'vendor/plugins/masterview'
       m.directory 'vendor/plugins/masterview/directives'
+      m.directory 'vendor/plugins/masterview/examples'
+      m.directory 'vendor/plugins/masterview/examples/rails_app_admin_auth'
       m.directory 'vendor/plugins/masterview/lib'
       m.directory 'vendor/plugins/masterview/lib/masterview'
       m.directory 'vendor/plugins/masterview/lib/masterview/extras'
@@ -26,6 +28,7 @@ class MasterviewPluginGenerator < Rails::Generator::Base
       m.file 'settings.rb', 'config/masterview/settings.rb'
       m.file 'development.rb', 'config/masterview/environments/development.rb'
       m.file 'production.rb', 'config/masterview/environments/production.rb'
+      m.file 'admin_auth_mixin.rb', 'vendor/plugins/masterview/examples/rails_app_admin_auth/admin_auth_mixin.rb'
     end
   end
 

data/templates/admin_auth_mixin.rb

@@ -0,0 +1,47 @@
+
+# Example of a MasterView admin custom authorization mixin.
+#
+# This module is included into the MasterviewController, so it has access
+# to all the the standard rails controller facilities as well as
+# any application-specific features in your own ApplicationController.
+#
+# To install a custom authorization handler in your application,
+# copy this file to the app/masterview directory in your rails application
+# and modify the implementation of the allow_access? predicate to
+# perform checking suitable in your application for determining
+# whether to grant access to the MasterView admininstration pages.
+#
+# To change the mixin module name or to load your admin_auth module
+# from a different directory or file name, set the MasterView 
+# admin_auth_mixin configuration setting in your config/masterview/settings.rb 
+# or an appropriate config/masterview/environments specification.
+# 
+# For example, to load an alternate mixin from your app/masterview directory:
+#
+# config.admin_auth_mixin = {
+#   :file => 'alt_admin_auth_mixin',
+#   :module => :MasterViewAltAdminAuthMixin, # default is MasterViewAdminAuthMixin
+# }
+#
+# To load an auth_check mixin from your rails lib directory:
+#
+# config.admin_auth_mixin = {
+#   :file => 'lib/custom_admin_auth_mixin',
+#   :file_loc => :RAILS_ROOT,
+# }
+#
+module MasterViewAdminAuthMixin
+
+  MasterView::Log.debug { 'Using customized admin_auth mixin for MasterView admin (local requests only)' }
+
+  protected
+
+  # Check that the current user has authorization to access admin operations.
+  def allow_access?
+    # default allows only for developer testing on local machine
+    local_request?
+  end
+
+end
+
+

data/templates/masterview.rake

@@ -113,4 +113,19 @@ namespace :mv do
     puts f.read
   end
 
+  desc 'Cleanup/remove MasterView generated rhtml files - useful when generating erb to file system'
+  task :clean_mv_rhtml do
+    if MasterView::ConfigSettings.generate_rhtml_files
+      removed = []
+      MasterView::TemplateSpec.scan do |template_spec, content_hash|
+        removed << template_spec.remove_rhtml
+      end
+      removed.flatten.each { |f| puts "#{f} removed" }
+    else
+      puts "\nNote: config.generate_rhtml_files was false, so rails reads erb/rhtml directly from MasterView, and thus there is nothing to remove from the file system. If config.generate_rhtml_files = true (in config/masterview/settings.rb) and then this command would clean up the generated rhtml files from the file system"
+    end
+  end
+
+
+
 end

data/templates/settings.rb

@@ -26,6 +26,10 @@
 #config.template_src_dir_path = 'app/views'  # relative path from config.root_path
 #config.template_src_dir_abs_path( '/path/to/masterview/templates' )
 #config.template_filename_pattern = '*.html'
+#config.auto_copy_file_entries << { :source => 'path_to_my_images', :destination => 'public/images' }
+#config.auto_copy_file_entries << { :source => 'path_to_my_scripts', :destination => 'public/javascripts', :extensions => [:js, :JS] } # only copy js files
+#config.auto_copy_file_entries << { :source => 'path_to_my_css', :destination => 'public/stylesheets' }
+
 
 # Template Generation Options
 #config.template_dst_dir_path = 'app/views'  # relative path from config.root_path
@@ -50,6 +54,7 @@
 #config.inline_erb_start = '{{{'
 #config.inline_erb_end = '}}}'
 #config.inline_erb_substitution_regex = /\{\{\{(([^}]|\}[^}]|\}\}[^}])*)\}\}\}/
+#config.use_original_rexml_sax2parser = false
 
 # Rails application options
 #config.parse_masterview_templates_at_startup = true

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.0
 specification_version: 1
 name: masterview_plugin_generator
 version: !ruby/object:Gem::Version 
-  version: 0.3.2
-date: 2007-02-21 00:00:00 -06:00
+  version: 0.3.3
+date: 2007-05-28 00:00:00 -05:00
 summary: A (x)html friendly template engine for rails with the power of layouts, and partials. MasterView Plugin Generator for GEM
 require_paths: 
 - .
@@ -34,6 +34,7 @@ files:
 - templates/settings.rb
 - templates/empty.rhtml
 - templates/init.rb
+- templates/admin_auth_mixin.rb
 - templates/masterview.rake
 - templates/production.rb
 - Rakefile