RubyGems - wee - Versions diffs - 0.1.0 → 0.3.1 - Mend

wee 0.1.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (193) hide show

data/INSTALL +7 -0
data/README +268 -0
data/Rakefile +26 -0
data/TODO +116 -0
data/benchmark/Centrino1300/result.2000.counter.action +45 -0
data/benchmark/Centrino1300/result.2000.counter.render +43 -0
data/benchmark/Centrino1300/result.2000.filehandler +43 -0
data/benchmark/Centrino600/result.2000.counter.action +47 -0
data/benchmark/Centrino600/result.2000.counter.render +45 -0
data/benchmark/Centrino600/result.2000.filehandler +43 -0
data/benchmark/Makefile +48 -0
data/benchmark/bench.sh +24 -0
data/benchmark/counter.rb +96 -0
data/benchmark/filehandler.rb +6 -0
data/doc/rdoc/classes/Array.html +172 -0
data/doc/rdoc/classes/Cache.html +126 -0
data/doc/rdoc/classes/Cache/StorageCache.html +320 -0
data/doc/rdoc/classes/Cache/Strategy.html +128 -0
data/doc/rdoc/classes/Cache/Strategy/CapacityBounded.html +269 -0
data/doc/rdoc/classes/Cache/Strategy/LFU.html +238 -0
data/doc/rdoc/classes/Cache/Strategy/LFU/Item.html +111 -0
data/doc/rdoc/classes/Cache/Strategy/LRU.html +238 -0
data/doc/rdoc/classes/Cache/Strategy/LRU/Item.html +111 -0
data/doc/rdoc/classes/Cache/Strategy/Unbounded.html +225 -0
data/doc/rdoc/classes/Cache/Strategy/Unbounded/Item.html +111 -0
data/doc/rdoc/classes/Enumerable.html +146 -0
data/doc/rdoc/classes/LiteralMethod.html +196 -0
data/doc/rdoc/classes/Object.html +178 -0
data/doc/rdoc/classes/String.html +172 -0
data/doc/rdoc/classes/Struct.html +174 -0
data/doc/rdoc/classes/Wee.html +160 -0
data/doc/rdoc/classes/Wee/AnswerDecoration.html +182 -0
data/doc/rdoc/classes/Wee/Application.html +337 -0
data/doc/rdoc/classes/Wee/Brush.html +245 -0
data/doc/rdoc/classes/Wee/Brush/ActionCallbackMixin.html +149 -0
data/doc/rdoc/classes/Wee/Brush/ActionMixin.html +146 -0
data/doc/rdoc/classes/Wee/Brush/ActionURLCallbackMixin.html +157 -0
data/doc/rdoc/classes/Wee/Brush/AnchorTag.html +210 -0
data/doc/rdoc/classes/Wee/Brush/AssignMixin.html +141 -0
data/doc/rdoc/classes/Wee/Brush/CallbackMixin.html +141 -0
data/doc/rdoc/classes/Wee/Brush/FormTag.html +225 -0
data/doc/rdoc/classes/Wee/Brush/GenericEncodedTextBrush.html +176 -0
data/doc/rdoc/classes/Wee/Brush/GenericTagBrush.html +283 -0
data/doc/rdoc/classes/Wee/Brush/GenericTextBrush.html +176 -0
data/doc/rdoc/classes/Wee/Brush/ImageButtonTag.html +195 -0
data/doc/rdoc/classes/Wee/Brush/InputCallbackMixin.html +149 -0
data/doc/rdoc/classes/Wee/Brush/InputTag.html +172 -0
data/doc/rdoc/classes/Wee/Brush/Page.html +193 -0
data/doc/rdoc/classes/Wee/Brush/SelectListTag.html +267 -0
data/doc/rdoc/classes/Wee/Brush/SelectOptionTag.html +177 -0
data/doc/rdoc/classes/Wee/Brush/SubmitButtonTag.html +154 -0
data/doc/rdoc/classes/Wee/Brush/TableDataTag.html +173 -0
data/doc/rdoc/classes/Wee/Brush/TableHeaderTag.html +146 -0
data/doc/rdoc/classes/Wee/Brush/TableRowTag.html +277 -0
data/doc/rdoc/classes/Wee/Brush/TableTag.html +146 -0
data/doc/rdoc/classes/Wee/Brush/TextAreaTag.html +229 -0
data/doc/rdoc/classes/Wee/Brush/TextInputTag.html +154 -0
data/doc/rdoc/classes/Wee/Callback.html +231 -0
data/doc/rdoc/classes/Wee/CallbackRegistry.html +308 -0
data/doc/rdoc/classes/Wee/CallbackStream.html +227 -0
data/doc/rdoc/classes/Wee/Canvas.html +235 -0
data/doc/rdoc/classes/Wee/Component.html +933 -0
data/doc/rdoc/classes/Wee/Context.html +111 -0
data/doc/rdoc/classes/Wee/Decoration.html +338 -0
data/doc/rdoc/classes/Wee/Delegate.html +247 -0
data/doc/rdoc/classes/Wee/ErrorPage.html +175 -0
data/doc/rdoc/classes/Wee/ErrorResponse.html +180 -0
data/doc/rdoc/classes/Wee/GenericResponse.html +162 -0
data/doc/rdoc/classes/Wee/HtmlCanvas.html +751 -0
data/doc/rdoc/classes/Wee/HtmlWriter.html +351 -0
data/doc/rdoc/classes/Wee/LiteralMethodCallback.html +180 -0
data/doc/rdoc/classes/Wee/MethodCallback.html +193 -0
data/doc/rdoc/classes/Wee/Page.html +111 -0
data/doc/rdoc/classes/Wee/Presenter.html +521 -0
data/doc/rdoc/classes/Wee/RedirectResponse.html +150 -0
data/doc/rdoc/classes/Wee/RefreshResponse.html +157 -0
data/doc/rdoc/classes/Wee/RenderingContext.html +111 -0
data/doc/rdoc/classes/Wee/Request.html +268 -0
data/doc/rdoc/classes/Wee/RequestHandler.html +336 -0
data/doc/rdoc/classes/Wee/Response.html +260 -0
data/doc/rdoc/classes/Wee/Session.html +469 -0
data/doc/rdoc/classes/Wee/SimpleIdGenerator.html +198 -0
data/doc/rdoc/classes/Wee/Snapshot.html +211 -0
data/doc/rdoc/classes/Wee/StateHolder.html +149 -0
data/doc/rdoc/classes/Wee/StateRegistry.html +434 -0
data/doc/rdoc/classes/Wee/StateRegistry/Snapshot.html +320 -0
data/doc/rdoc/classes/Wee/StateRegistry/WithObject.html +153 -0
data/doc/rdoc/classes/Wee/Utils.html +111 -0
data/doc/rdoc/classes/Wee/Utils/LRUCache.html +148 -0
data/doc/rdoc/classes/Wee/ValueHolder.html +220 -0
data/doc/rdoc/classes/Wee/WEBrickAdaptor.html +330 -0
data/doc/rdoc/created.rid +1 -0
data/doc/rdoc/files/INSTALL.html +118 -0
data/doc/rdoc/files/README.html +466 -0
data/doc/rdoc/files/lib/cache/cache_rb.html +101 -0
data/doc/rdoc/files/lib/wee/adaptors/webrick_rb.html +108 -0
data/doc/rdoc/files/lib/wee/application_rb.html +112 -0
data/doc/rdoc/files/lib/wee/callback_rb.html +107 -0
data/doc/rdoc/files/lib/wee/component_ext_rb.html +101 -0
data/doc/rdoc/files/lib/wee/component_rb.html +109 -0
data/doc/rdoc/files/lib/wee/context_rb.html +101 -0
data/doc/rdoc/files/lib/wee/core/callback_rb.html +115 -0
data/doc/rdoc/files/lib/wee/core/component_rb.html +108 -0
data/doc/rdoc/files/lib/wee/core/decoration_rb.html +133 -0
data/doc/rdoc/files/lib/wee/core/presenter_rb.html +112 -0
data/doc/rdoc/files/lib/wee/core/snapshot_rb.html +113 -0
data/doc/rdoc/files/lib/wee/core/valueholder_rb.html +110 -0
data/doc/rdoc/files/lib/wee/core_rb.html +131 -0
data/doc/rdoc/files/lib/wee/decoration_rb.html +101 -0
data/doc/rdoc/files/lib/wee/holder_rb.html +101 -0
data/doc/rdoc/files/lib/wee/html_canvas_rb.html +108 -0
data/doc/rdoc/files/lib/wee/html_writer_rb.html +108 -0
data/doc/rdoc/files/lib/wee/idgen_rb.html +101 -0
data/doc/rdoc/files/lib/wee/page_rb.html +101 -0
data/doc/rdoc/files/lib/wee/presenter_rb.html +112 -0
data/doc/rdoc/files/lib/wee/renderer/html/brushes_rb.html +101 -0
data/doc/rdoc/files/lib/wee/renderer/html/canvas_rb.html +101 -0
data/doc/rdoc/files/lib/wee/renderer/html/writer_rb.html +108 -0
data/doc/rdoc/files/lib/wee/rendering/html/brushes_rb.html +101 -0
data/doc/rdoc/files/lib/wee/rendering/html/canvas_rb.html +101 -0
data/doc/rdoc/files/lib/wee/rendering/html/writer_rb.html +108 -0
data/doc/rdoc/files/lib/wee/request_rb.html +113 -0
data/doc/rdoc/files/lib/wee/requesthandler_rb.html +101 -0
data/doc/rdoc/files/lib/wee/response_rb.html +108 -0
data/doc/rdoc/files/lib/wee/session_rb.html +109 -0
data/doc/rdoc/files/lib/wee/snapshot_ext_rb.html +101 -0
data/doc/rdoc/files/lib/wee/snapshot_rb.html +107 -0
data/doc/rdoc/files/lib/wee/state_registry_rb.html +110 -0
data/doc/rdoc/files/lib/wee/stuff_rb.html +144 -0
data/doc/rdoc/files/lib/wee/utils/cache_rb.html +108 -0
data/doc/rdoc/files/lib/wee/webrick_rb.html +108 -0
data/doc/rdoc/files/lib/wee_rb.html +132 -0
data/doc/rdoc/fr_class_index.html +93 -0
data/doc/rdoc/fr_file_index.html +51 -0
data/doc/rdoc/fr_method_index.html +242 -0
data/doc/rdoc/index.html +24 -0
data/doc/rdoc/rdoc-style.css +208 -0
data/examples/ObjectSpaceBrowser.rb +199 -0
data/examples/calendar.rb +366 -0
data/examples/cc.rb +94 -0
data/examples/draw.rb +91 -0
data/examples/example.rb +223 -0
data/examples/test.rb +66 -0
data/examples/window.rb +53 -0
data/lib/cache/cache.rb +9 -0
data/lib/wee.rb +18 -8
data/lib/wee/adaptors/webrick.rb +73 -0
data/lib/wee/application.rb +69 -71
data/lib/wee/context.rb +2 -12
data/lib/wee/core.rb +15 -0
data/lib/wee/core/callback.rb +108 -0
data/lib/wee/core/component.rb +314 -0
data/lib/wee/core/decoration.rb +129 -0
data/lib/wee/core/presenter.rb +132 -0
data/lib/wee/core/snapshot.rb +21 -0
data/lib/wee/core/valueholder.rb +19 -0
data/lib/wee/idgen.rb +13 -0
data/lib/wee/page.rb +1 -1
data/lib/wee/renderer/html/brushes.rb +435 -0
data/lib/wee/renderer/html/canvas.rb +148 -0
data/lib/wee/{html_writer.rb → renderer/html/writer.rb} +31 -16
data/lib/wee/request.rb +57 -0
data/lib/wee/requesthandler.rb +77 -0
data/lib/wee/response.rb +77 -0
data/lib/wee/session.rb +70 -64
data/lib/wee/{snapshot.rb → snapshot_ext.rb} +4 -4
data/test/components/calltest.rb +16 -0
data/test/components/counter.rb +17 -0
data/test/components/messagebox.rb +15 -0
data/test/components/page.rb +14 -0
data/test/components/page_decoration.rb +7 -0
data/test/stress.rb +64 -0
data/test/test_component.rb +106 -0
data/test/test_html_canvas.rb +25 -0
data/test/test_html_writer.rb +27 -0
data/test/test_request.rb +13 -0
data/test/utils/cross.rb +65 -0
data/test/utils/generic_plotter.rb +28 -0
data/test/utils/gnuplot.rb +31 -0
data/test/utils/measure_memory.rb +9 -0
data/test/utils/memory_plotter.rb +10 -0
data/test/utils/object_plotter.rb +10 -0
data/test/utils/webrick_background.rb +31 -0
data/wee.gemspec +22 -0
metadata +222 -18
data/lib/wee/component.rb +0 -126
data/lib/wee/delegate_decoration.rb +0 -22
data/lib/wee/handler_registry.rb +0 -89
data/lib/wee/holder.rb +0 -14
data/lib/wee/html_canvas.rb +0 -379
data/lib/wee/state_registry.rb +0 -173
data/lib/wee/stuff.rb +0 -29
data/lib/wee/webrick.rb +0 -15

data/doc/rdoc/files/README.html ADDED Viewed

@@ -0,0 +1,466 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html
+     PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+  <title>File: README</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <meta http-equiv="Content-Script-Type" content="text/javascript" />
+  <link rel="stylesheet" href=".././rdoc-style.css" type="text/css" media="screen" />
+  <script type="text/javascript">
+  // <![CDATA[
+  function popupCode( url ) {
+    window.open(url, "Code", "resizable=yes,scrollbars=yes,toolbar=no,status=no,height=150,width=400")
+  }
+  function toggleCode( id ) {
+    if ( document.getElementById )
+      elem = document.getElementById( id );
+    else if ( document.all )
+      elem = eval( "document.all." + id );
+    else
+      return false;
+    elemStyle = elem.style;
+    if ( elemStyle.display != "block" ) {
+      elemStyle.display = "block"
+    } else {
+      elemStyle.display = "none"
+    }
+    return true;
+  }
+  // Make codeblocks hidden by default
+  document.writeln( "<style type=\"text/css\">div.method-source-code { display: none }</style>" )
+  // ]]>
+  </script>
+</head>
+<body>
+  <div id="fileHeader">
+    <h1>README</h1>
+    <table class="header-table">
+    <tr class="top-aligned-row">
+      <td><strong>Path:</strong></td>
+      <td>README
+      </td>
+    </tr>
+    <tr class="top-aligned-row">
+      <td><strong>Last Update:</strong></td>
+      <td>Wed Jan 05 14:36:24 CET 2005</td>
+    </tr>
+    </table>
+  </div>
+  <!-- banner header -->
+  <div id="bodyContent">
+  <div id="contextContent">
+    <div id="description">
+      <h1><a href="../classes/Wee.html">Wee</a> Web Framework</h1>
+<h2>Copyright and License</h2>
+<p>
+Copyright &#169; 2004, 2005 by Michael Neumann (mneumann@ntecs.de).
+</p>
+<p>
+Released under the same terms of license as Ruby. Some files under
+directory <tt>examples/</tt> might be copyrighted by third parties and
+licensed under different terms.
+</p>
+<h2>Status and Bugs</h2>
+<p>
+<a href="../classes/Wee.html">Wee</a> is not considered production ready!
+It should only be used for small things.
+</p>
+<p>
+Known Bugs:
+</p>
+<ul>
+<li>Continuations leak memory!
+</li>
+<li>Sessions get never reclaimed (easy to fix).
+</li>
+</ul>
+<h2>Introduction</h2>
+<p>
+<a href="../classes/Wee.html">Wee</a> is a light-weight, very high-level
+and modern web-framework that makes <b>W</b>eb <b>e</b>ngineering
+<b>e</b>asy. It mainly inherits many ideas and features from <a
+href="http://beta4.com/seaside2">Seaside2</a>, but was written from scratch
+without ever looking at the Seaside (or any other) sources. All code was
+developed from ideas and lots of discussions with Avi Bryant.
+</p>
+<h2>Features</h2>
+<h3>Reusable components</h3>
+<p>
+<a href="../classes/Wee.html">Wee</a> has <em>real</em> components, which
+are like widgets in a GUI. Once written, you can use them everywhere. They
+are completely independent and do not interfere with other components.
+Components encapsulate state, a view and actions. Of course you can use an
+external model or use templates for rendering.
+</p>
+<h3>Backtracking</h3>
+<p>
+See the <em>What is backtracking?</em> section below. In short,
+backtracking lets the browser&#8217;s back and forward-button play well
+together with your application.
+</p>
+<h3>Clean and concise</h3>
+<p>
+<a href="../classes/Wee.html">Wee</a> is well thought out, is written in
+<b>and</b> supports clean and concise code. Furthermore I think most parts
+are now very well documented.
+</p>
+<h3>Abstract core</h3>
+<p>
+The core of <a href="../classes/Wee.html">Wee</a> is completely independent
+of both HTTP and HTML. That means, with little effort, you should be able
+to render other formats than HTML and use other communication protocols
+like SOAP, XML-RPC, Email, GUI or Console.
+</p>
+<h3>Templating-independent</h3>
+<p>
+<a href="../classes/Wee.html">Wee</a> does not depend on a special
+templating-engine. You can use a different templating engine for each
+component if you want.
+</p>
+<h3>Powerful programmatic HTML generation</h3>
+<p>
+<a href="../classes/Wee.html">Wee</a> ships with an easy to use and very
+powerful programmatic html-generation library. For example you can create a
+select list easily with this piece of code:
+</p>
+<pre>
+   # select an object from these items
+   items = [1, 2, 3, 4]
+   # the labels shown to the user
+   labels = items.map {|i| i.to_s}
+   # render it
+   r.select_list(items).labels(labels).callback {|choosen| p choosen}
+   # render a multi-select list, with objects 2 and 4 selected
+   r.select_list(items).multi.labels(labels).selected([2,4])
+</pre>
+<p>
+The callback is called with the selected objects from the <em>items</em>
+array. Items can be any object, e.g. whole components:
+</p>
+<pre>
+   labels = [&quot;msg1&quot;, &quot;msg2&quot;]
+   items = labels.collect {|m| MessageBox.new(m)}
+   r.select_list(items).labels(labels).callback {|choosen| call choosen.first}
+</pre>
+<h3>Continuation based (Optional)</h3>
+<p>
+<b>IMPORTANT:</b> <em>The current implementation of continuations in Ruby
+might lead to memory leaks, if you use continuations. Furthermore, if you
+use continuations, it&#8217;s no longer possible to store the session state
+to disk.</em>
+</p>
+<p>
+Continuation-based frameworks are also known as <em>modal</em> frameworks.
+You can write code like the one shown below (taken from one of Avi&#8217;s
+emails) where each method displays a new page:
+</p>
+<pre>
+  def checkout
+    billing = getAddress(&quot;Billing Address&quot;)
+    if useSeparateShippingAddress()
+      shipping = getAddress(&quot;Shipping Address&quot;)
+    else
+      shipping = billing
+    end
+    payment = getPaymentInfo()
+    showConfirmation(billing, shipping, payment)
+  end
+</pre>
+<p>
+Try to implement the same in a non-continuation based framework and show me
+your code&#8230; ;-)
+</p>
+<h3>Fully Marshallable (drops Continuation support)</h3>
+<p>
+If you don&#8217;t need continuations, <a
+href="../classes/Wee.html">Wee</a> can be made fully marshallable. It is
+not yet fully marshallable (it was in the past), but it can be made, if
+required.
+</p>
+<h2>Observations and Limitations</h2>
+<ul>
+<li>Using continuations (might) lead to memory leaks!
+</li>
+<li>When using continuations for cross-component calls, it&#8217;s impossible
+to store a session to disk (at least in Ruby). This problem is partly
+addressed by checkpointing provided by operating systems like <a
+href="http://www.dragonflybsd.org">DragonFly</a>. But with this approach
+it&#8217;s still impossible to store sessions <em>selectively</em> to disk.
+</li>
+<li>Each session runs in it&#8217;s own (light-weigth) thread (this is a
+neccessity when using continuations).
+</li>
+<li>Only one action callback can be invoked per request (a former version of <a
+href="../classes/Wee.html">Wee</a> was able to invoke multiple callback,
+and answer even from multiple components at the same time, but this was
+removed, due to the unreliability of continuations in Ruby).
+</li>
+<li>Components are thread-safe, as a fresh components-tree is created for each
+session and requests inside a session are serialized.
+</li>
+</ul>
+<h2>What is backtracking?</h2>
+<p>
+If you want, you can make the back-button of your browser work correctly
+together with your web-application. Imagine you have a simple counter
+application, which shows the current count and two links <em>inc</em> and
+<em>dec</em> with which you can increase or decrease the current count.
+Starting with an inital count of 0, you increase the counter up to 8, then
+click three times the back button of your browser (now displays 5) and
+finally decrease by one, then the counter really shows the expected 4,
+instead of 7 (as clicking the back button does usually not send a HTTP
+request, and the last state of your application was 8).
+</p>
+<p>
+Only individual objects are backtracked, those of which you explicitly take
+a snapshot, not the whole component. That&#8217;s the easiest (from an
+application programmers perspective) and most flexible way. And its fast
+and uses less memory.
+</p>
+<p>
+You can decide yourself whether you want infinite backtracking or only
+backtracking up to n pages, with whatever replacement strategy you want,
+least recently used (LRU), least frequently used (LFU) etc.
+</p>
+<h2>Decorations</h2>
+<p>
+Decorations are used to modify the look and behaviour of a component,
+without modifying the components tree. A component can have more than one
+decoration. This is implemented as a linked list of decorations
+(Wee::Decoration#owner points to the next decoration). <a
+href="../classes/Wee/Component.html#M000170">Wee::Component#decoration</a>
+points to the first decoration in the chain or to the component itself, if
+no decorations were specified. We actually use a <a
+href="../classes/Wee/ValueHolder.html">Wee::ValueHolder</a> for the
+<tt>@decoration</tt> instance variable of class <a
+href="../classes/Wee/Component.html">Wee::Component</a> to be able to
+easily backtrack it (required if you want to &quot;undo&quot; component
+calls).
+</p>
+<h2>The anatomy of a request/response cycle</h2>
+<p>
+The request/response cycle in <a href="../classes/Wee.html">Wee</a> is
+actually split into two separate phases or steps. Depending on the
+point-of-view (given that a page is rendered and the user clicks on a link
+or button), the first phase is to invoke an action (a
+&quot;callback&quot;). Then in the second phase, a new page is rendered and
+sent back to the user. So the two steps are:
+</p>
+<ol>
+<li>invoke callbacks (action phase)
+</li>
+<li>render new page and display (render phase)
+</li>
+</ol>
+<p>
+These two phases repeat permanently. Which tasks are performed in each of
+them, is briefly listed below:
+</p>
+<p>
+<b>Action:</b>
+</p>
+<ol>
+<li>restore snapshot (if not up-to-date)
+</li>
+<li>invoke actions
+</li>
+<li>backtrack state
+</li>
+<li>update url -&gt; redirect to render phase (not yet)
+</li>
+</ol>
+<p>
+<b>Render:</b>
+</p>
+<ol>
+<li>restore snapshot (if not up-to-date)
+</li>
+<li>render
+</li>
+</ol>
+<p>
+For each session there is at most one request handled at the same time.
+That means, that there is either one action request or one render request
+handled. Why? Because we have only one components tree, which we update on
+action requests. As <a href="../classes/Wee.html">Wee</a> allows to go back
+in time, we have to restore this components tree to a certain point in time
+before we can handle an action or render request. This disallows to handle
+e.g. two render requests simultaneous.
+</p>
+<h3>Action Phase (Invoking Callbacks)</h3>
+<p>
+Possible sources for callbacks are links (anchors) and all kinds of
+form-elements like submit buttons, input-fields etc. There are two
+different kinds of callbacks:
+</p>
+<ul>
+<li>Input callbacks (input-fields)
+</li>
+<li>Action callbacks (anchor, submit-button)
+</li>
+</ul>
+<p>
+The distinction between input and action callbacks is important, as action
+callbacks might depend on values of input-fields being assigned to instance
+variables of the controlling component. Hence, <a
+href="../classes/Wee.html">Wee</a> first invokes all input callbacks before
+any action callback is triggered.
+</p>
+<p>
+There are two methods related to callback processing:
+</p>
+<ul>
+<li><a
+href="../classes/Wee/Component.html#M000165">Wee::Component#process_callbacks_chain</a>
+</li>
+<li><a
+href="../classes/Wee/Presenter.html#M000187">Wee::Presenter#process_callbacks</a>
+</li>
+</ul>
+<p>
+Note that each <a href="../classes/Wee/Component.html">Wee::Component</a>
+is also a <a href="../classes/Wee/Presenter.html">Wee::Presenter</a>,
+whereas a <a href="../classes/Wee/Decoration.html">Wee::Decoration</a> is
+not a Component (but a Presenter)!
+</p>
+<p>
+Method <em>process_callbacks_chain</em> invokes <em>process_callbacks</em>
+for it&#8217;s first decoration, or if the component has no decorations,
+the method is called for the component itself. As such,
+<em>process_callbacks_chain</em> is important to avoid entering an infinite
+loop (a method calling itself). What decorations are, is discussed
+elsewhere.
+</p>
+<p>
+Method <em>process_callbacks</em> of class Component first invokes all
+input callbacks specified for this component, then calls
+<em>process_callbacks_chain</em> for all of it&#8217;s child components.
+This ensures, that all input callbacks are triggered before the first
+action callback is run. Finally, it invokes all of it&#8217;s action
+callbacks.
+</p>
+<h3>Rendering Phase</h3>
+<p>
+The rendering phase is assumed to be side-effect free! So, you as a
+programmer should take care to meet this assumption.
+</p>
+<p>
+Similar as in the callback-step, there are two methods related to rendering
+a page:
+</p>
+<ul>
+<li><a
+href="../classes/Wee/Component.html#M000163">Wee::Component#do_render_chain</a>
+</li>
+<li><a
+href="../classes/Wee/Presenter.html#M000182">Wee::Presenter#do_render</a>
+</li>
+</ul>
+<p>
+Method <em>Component#do_render_chain</em> starts rendering the decoration
+chain by calling <em>Presenter#do_render</em> for the first decoration of
+the component or for the component itself if no decorations were specified.
+Method <em>Presenter#do_render</em> then generates the desired output which
+gets sent to the user. Note that method <em>do_render</em> might call other
+components&#8217; <em>do_render_chain</em> methods to display those
+components &quot;inside&quot; itself (usually a component does this for
+it&#8217;s child components, but this has to be implemented by the
+programmer).
+</p>
+<h3>Further Reads</h3>
+<p>
+In this order:
+</p>
+<ul>
+<li><a href="../classes/Wee/Presenter.html">Wee::Presenter</a>
+</li>
+<li><a href="../classes/Wee/Component.html">Wee::Component</a>
+</li>
+<li><a href="../classes/Wee/Decoration.html">Wee::Decoration</a>
+</li>
+<li><a href="../classes/Wee/Delegate.html">Wee::Delegate</a>
+</li>
+<li><a href="../classes/Wee/AnswerDecoration.html">Wee::AnswerDecoration</a>
+</li>
+</ul>
+    </div>
+   </div>
+  </div>
+    <!-- if includes -->
+    <div id="section">
+    <!-- if method_list -->
+  </div>
+<div id="validator-badges">
+  <p><small><a href="http://validator.w3.org/check/referer">[Validate]</a></small></p>
+</div>
+</body>
+</html>