tagz 0.0.1

data/lib/tagz/rails.rb

@@ -0,0 +1,198 @@
+module Tagz::Rails
+  class Renderer
+    class Erbout
+      def self.for *a, &b
+        new *a, &b
+      end
+      def initialize context
+        @context = context
+      end
+      def nil?
+        true
+      end
+      def method_missing m, *a, &b
+        @context.send m, *a, &b
+      end
+    end
+
+    class Context
+      include Tagz
+
+      attr_accessor "__view__"
+      attr_accessor "__erbout__"
+      attr_accessor "__eol__"
+
+      def self.create view, local_assigns 
+        context = new
+        context.__view__ = view
+
+        view.assigns.merge(local_assigns).each do |k,v|
+          context.instance_variable_set "@#{ k }", v
+        end
+
+        local_assigns.each do |k,v|
+          context.singleton_class{ define_method(k.to_s){ v } }
+        end
+
+        context.instance_variable_set "@content_for_layout", view.instance_variable_get("@content_for_layout")
+        context
+      end
+
+      def self.render view, local_assigns, *argv
+        context = create view, local_assigns
+
+        pushing context do
+          source = argv.first
+          filename = argv.last
+
+          content_for_lookup = lambda do |*names|
+            name = names.shift || :layout
+            context.instance_variable_get "@content_for_#{ name }"
+          end
+
+          before_ivars = context.instance_variables
+
+            content_for_layout = context.__render__ source, filename, &content_for_lookup
+
+          after_ivars = context.instance_variables
+
+          #new_ivars = ( after_ivars - before_ivars ).delete_if{|ivar| ivar =~ %r/^@(__|content_for_)/o}
+          new_ivars = ( after_ivars - before_ivars ).delete_if{|ivar| ivar =~ %r/^@(__)/o}
+
+          new_ivars.each do |ivar|
+            key = ivar[1..-1]
+            value = context.instance_variable_get ivar
+            view.assigns[key] = value
+          end
+
+          content_for_layout
+        end
+      end
+
+      def self.stack
+        @stack ||= []
+      end
+
+      def self.pushing context
+        stack.push context
+        begin
+          yield
+        ensure
+          stack.pop
+        end
+      end
+
+      def self.depth
+        stack.size
+      end
+
+      def __render__ source, filename
+        tagz {
+          content_for_layout = eval source.to_s, binding, filename
+        }
+      end
+
+      def singleton_class &b
+        sc = 
+          class << self 
+            self 
+          end  
+        b ? sc.module_eval(&b) : sc
+      end
+
+      def method_missing m, *a, &b
+        case m.to_s
+          when %r/^(.*[^_])_(!)?$/o
+            m, bang = $1, $2
+            unless bang
+              __tag_start__ m, *a, &b
+            else
+              __tag_start__(m, *a){}
+            end
+          when %r/^_([^_].*)$/o
+            m = $1 
+            __tag_stop__ m, *a, &b
+          else
+            __view__.send m, *a, &b
+        end
+      end
+
+      def flash *a, &b
+        __view__.controller.send :flash, *a, &b
+      end
+
+      def _erbout
+        self.__erbout__ ||= Erbout.for(self)
+        #Erbout.for self
+      end
+
+      def << s
+        __ s; nil 
+      end
+
+      def puts *a
+        a.each{|elem| self << "#{ elem.to_s.chomp }#{ eol }"}
+      end
+
+      def p *a
+        a.each{|elem| self << "#{ CGI.escapeHTML elem.inspect }#{ eol }"}
+      end
+
+      def print *a
+        a.each{|elem| self << elem}
+      end
+
+      def eol
+        if  __view__.controller.response.content_type =~ %r|text/plain|io
+          "\n"
+        else
+          "<br />"
+        end
+      end
+
+      def capture *a, &b
+        b.call *a
+      end
+
+      def content_for(name, &block)
+        name, ivar = "content_for_#{ name }", "@content_for_#{ name }"
+        value = instance_variable_get(ivar).to_s
+        value << capture(&block).to_s
+        instance_variable_set ivar, value
+        __view__.assigns[name] = value
+        nil
+      end
+
+    end
+
+    def initialize view
+      @view = view
+    end
+
+    def render template, local_assigns, path
+      (( Context.render @view, local_assigns, template, path )).to_s
+    end
+  end
+
+  def self.new *a, &b
+    Renderer.new *a, &b
+  end
+
+  #if defined? ::ActionView and defined? ::ActionView::Base
+### TODO - see if this hack can be pulled out
+    module ::ActionView # thanks _why !
+      class Base
+        def render_template(template_extension, template, file_path = nil, local_assigns = {})
+          if handler = @@template_handlers[template_extension]
+            template ||= read_template_file(file_path, template_extension)
+            handler.new(self).render(template, local_assigns, file_path)
+          else
+            compile_and_render_template(template_extension, template, file_path, local_assigns)
+          end
+        end
+      end
+    end
+    ::ActionView::Base.register_template_handler 'rb', Tagz::Rails
+    ::ActionView::Base.register_template_handler 'tagz', Tagz::Rails
+  #end
+end

data/rails/README

@@ -0,0 +1,182 @@
+== Welcome to Rails
+
+Rails is a web-application and persistence framework that includes everything
+needed to create database-backed web-applications according to the
+Model-View-Control pattern of separation. This pattern splits the view (also
+called the presentation) into "dumb" templates that are primarily responsible
+for inserting pre-built data in between HTML tags. The model contains the
+"smart" domain objects (such as Account, Product, Person, Post) that holds all
+the business logic and knows how to persist themselves to a database. The
+controller handles the incoming requests (such as Save New Account, Update
+Product, Show Post) by manipulating the model and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails.  You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting started
+
+1. At the command prompt, start a new rails application using the rails command
+   and your application name. Ex: rails myapp
+   (If you've downloaded rails in a complete tgz or zip, this step is already done)
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You’re riding the Rails!"
+4. Follow the guidelines to start developing your application
+
+
+== Web Servers
+
+By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
+Rails will use the WEBrick, the webserver that ships with Ruby. When you run script/server,
+Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
+that you can always get up and running quickly.
+
+Mongrel is a Ruby-based webserver with a C-component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+
+If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
+Mongrel and WEBrick and also suited for production use, but requires additional
+installation and currently only works well on OS X/Unix (Windows users are encouraged
+to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
+http://www.lighttpd.net.
+
+And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
+web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
+for production.
+
+But of course its also possible to run Rails on any platform that supports FCGI.
+Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
+please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
+
+
+== Debugging Rails
+
+Have "tail -f" commands running on the server.log and development.log. Rails will
+automatically display debugging and runtime information to these files. Debugging
+info will also be shown in the browser on requests from 127.0.0.1.
+
+
+== Breakpoints
+
+Breakpoint support is available through the script/breakpointer client. This
+means that you can break out of execution at any point in the code, investigate
+and change the model, AND then resume execution! Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      breakpoint "Breaking out from the list"
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the breakpointer window. Here you can do things like:
+
+Executing breakpoint "Breaking out from the list" at .../webrick_server.rb:16 in 'breakpoint'
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a breakpoint"
+  => "hello from a breakpoint"
+
+...and even better is that you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you press CTRL-D
+
+
+== Console
+
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+Here you'll have all parts of the application configured, just like it is when the
+application is running. You can inspect domain models, change values, and save to the
+database. Starting the script without arguments will launch it in the development environment.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+
+
+== Description of contents
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from ApplicationController
+  which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.rhtml for the WeblogsController#index action. All views use eRuby
+  syntax.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the common
+  header/footer method of wrapping views. In your views, define a layout using the
+  <tt>layout :default</tt> and create a file named default.rhtml. Inside default.rhtml,
+  call <% yield %> to render the view using this layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are generated
+  for you automatically when using script/generate for controllers. Helpers can be used to
+  wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+
+components
+  Self-contained mini-applications that can bundle together controllers, models, and views.
+
+db
+  Contains the database schema in schema.rb.  db/migrate contains all
+  the sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when generated
+  using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that doesn't
+  belong under controllers, models, or helpers. This directory is in the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files. This should be
+  set as the DOCUMENT_ROOT of your web server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the script/generate scripts, template
+  test files will be generated for you and placed in this directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  This directory is in the load path.

data/rails/Rakefile

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'

data/rails/app/controllers/application.rb

@@ -0,0 +1,7 @@
+# Filters added to this controller apply to all controllers in the application.
+# Likewise, all the methods added will be available for all controllers.
+
+class ApplicationController < ActionController::Base
+  # Pick a unique cookie name to distinguish our session data from others'
+  session :session_key => '_rails_session_id'
+end

data/rails/app/controllers/tagz_controller.rb

@@ -0,0 +1,51 @@
+class TagzController < ApplicationController
+  include Tagz
+  helper{ include Tagz }
+
+  ### menu
+  def index
+    menu = %w( a b c d e ).map{|action| "<br><a href='#{ action }'>#{ action }</a>"}
+    render :text => "<html> <body> #{ menu } </body> </html>"
+  end
+
+  ### setup a little data
+  def initialize
+    @title = 'tagz!'
+    @list = %w( a b c )
+  end
+
+  ### just using tagz inline
+  def a 
+    text = tagz {
+      html_{
+        head_{ title_{ @title } }
+
+        body_{
+          ul_{ @list.each{|elem| li_{ elem } } }
+        }
+      }
+    }
+
+    render :text => text
+  end
+
+  ### using a simple template : app/views/tagz/b.rb
+  def b
+    render
+  end
+
+  ### using content_for : app/views/layouts/layout.rb app/views/tagz/c.rb
+  def c
+    render :layout => 'layout' 
+  end
+
+  ### mixing erb and tagz
+  def d
+    render
+  end
+
+  ### rendering fubar content see app/views/tagz/e.rb
+  def e
+    render
+  end
+end