RubyGems - masterview - Versions diffs - 0.1.5 → 0.2.0 - Mend

masterview 0.1.5 → 0.2.0

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 (105) hide show

data/CHANGELOG +17 -0
data/README +36 -504
data/RELEASE_NOTES +126 -45
data/Rakefile +215 -86
data/TODO +8 -3
data/doc/configuration.html +485 -0
data/doc/directives.html +1085 -0
data/doc/guide.html +243 -0
data/doc/index.html +287 -0
data/doc/installation.html +376 -0
data/doc/stylesheets/masterview.css +206 -0
data/doc/stylesheets/mv-config.css +23 -0
data/doc/stylesheets/mv-directives.css +18 -0
data/doc/stylesheets/mv-installation.css +10 -0
data/doc/troubleshooting.html +18 -0
data/examples/product.html +256 -0
data/examples/product.html.old +107 -0
data/examples/rails_app_config/masterview/environment/development.rb +22 -0
data/examples/rails_app_config/masterview/environment/production.rb +9 -0
data/examples/rails_app_config/masterview/settings.rb +59 -0
data/examples/test.import +80 -0
data/init.rb +26 -12
data/lib/masterview/analyzer.rb +25 -15
data/lib/masterview/directive_base.rb +4 -0
data/lib/masterview/directive_helpers.rb +7 -5
data/lib/masterview/directives/import_render.rb +6 -0
data/lib/masterview/directives/insert_generated_comment.rb +8 -8
data/lib/masterview/extras/app/controllers/masterview_controller.rb +154 -2
data/lib/masterview/extras/app/views/masterview/admin/create.rhtml +4 -4
data/lib/masterview/extras/app/views/masterview/admin/empty.rhtml +1 -1
data/lib/masterview/extras/app/views/masterview/admin/list.rhtml +14 -9
data/lib/masterview/extras/app/views/masterview/admin/view_rhtml.rhtml +70 -0
data/lib/masterview/extras/init_logger.rb +102 -0
data/lib/masterview/extras/init_rails_erb_mv_direct.rb +117 -0
data/lib/masterview/extras/init_rails_reparse_checking.rb +59 -0
data/lib/masterview/extras/watcher.rb +17 -23
data/lib/masterview/filter_helpers.rb +26 -0
data/lib/masterview/initializer.rb +912 -0
data/lib/masterview/io.rb +352 -0
data/lib/masterview/keyword_expander.rb +116 -0
data/lib/masterview/masterview_version.rb +2 -2
data/lib/masterview/mtime_tracking_hash.rb +44 -0
data/lib/masterview/parser.rb +64 -92
data/lib/masterview/pathname_extensions.rb +33 -0
data/lib/masterview/template_spec.rb +49 -56
data/lib/masterview.rb +40 -85
data/test/fixtures/configs/fake_rails_app_with_config/config/masterview/environments/development.rb +12 -0
data/test/fixtures/configs/fake_rails_app_with_config/config/masterview/environments/production.rb +11 -0
data/test/fixtures/configs/fake_rails_app_with_config/config/masterview/settings.rb +23 -0
data/test/fixtures/templates/product.html +256 -0
data/test/fixtures/templates/test.import +80 -0
data/test/test_helper.rb +5 -3
data/test/tmp/template/foo.txt +1 -0
data/test/tmp/templates_src/product.html +256 -0
data/test/tmp/views/layouts/product.rhtml +35 -0
data/test/tmp/views/product/_form.rhtml +30 -0
data/test/tmp/views/product/_product.rhtml +14 -0
data/test/tmp/views/product/_show.rhtml +27 -0
data/test/tmp/views/product/destroy.rhtml +27 -0
data/test/tmp/views/product/edit.rhtml +26 -0
data/test/tmp/views/product/list.rhtml +31 -0
data/test/tmp/views/product/new.rhtml +29 -0
data/test/tmp/views/product/show.rhtml +16 -0
data/test/unit/config_settings_test.rb +172 -0
data/test/{attr_test.rb → unit/directive_attr_test.rb} +2 -2
data/test/{block_test.rb → unit/directive_block_test.rb} +2 -2
data/test/{content_test.rb → unit/directive_content_test.rb} +2 -2
data/test/{else_test.rb → unit/directive_else_test.rb} +2 -2
data/test/{elsif_test.rb → unit/directive_elsif_test.rb} +2 -2
data/test/{form_test.rb → unit/directive_form_test.rb} +2 -2
data/test/{global_inline_erb_test.rb → unit/directive_global_inline_erb_test.rb} +2 -2
data/test/{hidden_field_test.rb → unit/directive_hidden_field_test.rb} +2 -2
data/test/{if_test.rb → unit/directive_if_test.rb} +2 -2
data/test/unit/directive_import_render_test.rb +62 -0
data/test/{import_test.rb → unit/directive_import_test.rb} +2 -2
data/test/{javascript_include_test.rb → unit/directive_javascript_include_test.rb} +2 -2
data/test/{link_to_if_test.rb → unit/directive_link_to_if_test.rb} +2 -2
data/test/{link_to_test.rb → unit/directive_link_to_test.rb} +2 -2
data/test/{omit_tag_test.rb → unit/directive_omit_tag_test.rb} +2 -2
data/test/{password_field_test.rb → unit/directive_password_field_test.rb} +2 -2
data/test/{replace_test.rb → unit/directive_replace_test.rb} +2 -2
data/test/{stylesheet_link_test.rb → unit/directive_stylesheet_link_test.rb} +2 -2
data/test/{submit_test.rb → unit/directive_submit_test.rb} +2 -2
data/test/{text_area_test.rb → unit/directive_text_area_test.rb} +2 -2
data/test/{text_field_test.rb → unit/directive_text_field_test.rb} +2 -2
data/test/{example_test.rb → unit/example_test.rb} +1 -1
data/test/unit/file_mio_test.rb +368 -0
data/test/{filter_helpers_test.rb → unit/filter_helpers_test.rb} +1 -1
data/test/unit/keyword_expander_test.rb +95 -0
data/test/unit/mio_test.rb +110 -0
data/test/unit/mtime_string_hash_mio_tree_test.rb +289 -0
data/test/unit/mtime_tracking_hash_test.rb +38 -0
data/test/{parser_test.rb → unit/parser_test.rb} +19 -1
data/test/unit/pathname_extensions_test.rb +46 -0
data/test/{run_parser_test.rb → unit/run_parser_test.rb} +7 -3
data/test/unit/string_hash_mio_test.rb +320 -0
data/test/unit/template_file_watcher_test.rb +107 -0
data/test/{template_spec_test.rb → unit/template_spec_test.rb} +57 -21
data/test/{template_test.rb → unit/template_test.rb} +123 -22
data/test/xtras/config-mv-logger_config.rb +109 -0
data/test/xtras/config_initialize_standalone.rb +53 -0
metadata +111 -38
data/lib/masterview/extras/rails_init.rb +0 -72
data/test/import_render_test.rb +0 -30
data/test/template_file_watcher_test.rb +0 -50

data/doc/guide.html ADDED Viewed

@@ -0,0 +1,243 @@
+<?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>MasterView - User's Guide</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <meta http-equiv="Content-Script-Type" content="text/javascript" />
+  <link href="./stylesheets/masterview.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+<div id="pageHeader">
+<div>MasterView Template Engine</div>
+<div class="description">Rails-optimized (x)html friendly template engine</div>
+</div>
+<div id="pageBody">
+<div id="bodyContent" mv:generate="{template_path}" mv:omit_tag="">
+<h1>MasterView - User's Guide</h1>
+<p>
+MasterView is designed to be easy
+for a developer and designer to work together. By keeping the template in
+an html friendly format, designers can apply style, layout changes, wording
+changes, without causing havoc on the rails view code. The designer can be
+involved at anytime during the development cycle including being able to
+change style and layout after the system is built. This is great for
+allowing design or wording changes without reinvolving the developers. One
+can even start from a designer created prototype and add MasterView tags to make it become
+real. Whichever way you prefer to work, MasterView accomodates you.
+</p>
+<h2>Creating MasterView Templates</h2>
+<p>
+You may add MasterView attributes
+to existing (x)html or you may use the masterview generator to create a
+complete working application.
+</p>
+<h3>Writing MasterView Template Attribute Markup</h3>
+<p>MasterView template processing directives are encoded in an (x)html template
+using attribute markup.  A MasterView directive is an element attribute
+in the <span class="directiveName">mv:</span> namespace.
+By convention, Masterview directive attribute names use lower-case letters with
+underscore as a separator, e.g., <span class="directiveName">mv:generate</span>, <span class="directiveName">mv:link_to</span>.
+</p>
+<p class="explanation">
+<b>Note:</b> use of the <span class="directiveName">mv:</span> namespace
+used for MasterView directives in an (x)html template can be modified
+by a configuration setting.  See the <a href="configuration.html">MasterView Configuration Guide</a> for details.  However, we recommend that you do not change this namespace convention unless truly necessary - it's easier to understand your templates when they follow the standard markup convention.
+</p>
+<p>MasterView provides a number of built-in directives for general use.
+See the <a href="directives.html">MasterView Directives Reference</a>
+for details on the standard set of masterview directives that are available.
+You can also create your own custom directives to extend the power of the
+MasterView template processing with markup notation and processing directives
+that support standard uses for your particular application.
+<!--TODO: add link the Directive Developer's Guide-->
+</p>
+<h3>Using the MasterView Generator</h3>
+<p>
+ The masterview generator can create controllers, models,
+and MasterView template files in your Rails <code>app</code> directory,
+similar to how the built-in Rails generator works.
+</p>
+<p>
+To use the masterview generator, open a command shell and
+change directory to your rails application.
+Then run the masterview generator using a command of the form:
+</p>
+<pre class="code">
+script/generate masterview YourModelName [YourControllerName] [&#8212;style
+[cssStylesheet]] [&#8212;single-file] [&#8212;show-all | &#8212;show-only
+list]
+</pre>
+<p class="explanation">(Note for Windows users: you will need to explicitly specify the Ruby interpreter to run the masterview generator, i.e., the expression above becomes <code><b>ruby</b> script/generate masterview ...</code>) in a DOS command window.</p>
+<p>
+The generator by default will generate five masterview template files, one
+for each distinct page, list, new, edit, show, and destroy. They exist in
+the app/views/masterview directory with the filename
+controller_action.html. The layout and message partial are defined in the
+list template file and imported into the others. Similarly the new template
+defines the form partial which is imported into edit, and finally the show
+file defines a _show partial which is imported into destroy. Thus there is
+one definition of each part (layout and partial) and they are imported into
+the other files where needed to provide accurate WYSIWYG design time
+editing. By generating separate files, teams can work on a project easier,
+however MasterView also supports
+generating all parts to a single file for the ultimate in DRY.
+</p>
+<p>
+By adding the &#8212;single-file switch MasterView will create a single file
+and to make it easier to use this template at design time, some design time
+css stylesheets are included in the file to hide all sections except one.
+By default the NEW section is the only one shown. Other options are
+&#8212;show-all which makes all sections visible or [&#8212;show-only list]
+which shows only the LIST section. When you are editing the masterview file
+you may comment/uncomment one of the other css files to show a different
+section. The &#8212;style param allows you to suppress default style
+generation and specify an existing stylesheet to use, if you exlude the
+stylesheet none will be used, if you include this option multiple times
+with different stylesheets each will be used.
+</p>
+<p>
+Once it is done generating, the generated MasterView template file will be
+created in app/views/masterview/controller.html. This file is html and can
+be edited with any standard html editor. The rails specific logic is
+contained in simple attributes which are ignored by html editors. The
+syntax for these attributes is heavily derived from the rails helper tags
+themselves so it should feel natural to the rails developer.
+</p>
+<p>
+Another interesting thing to know is that while all of the pages for this
+Model have been bundled up into a few html file for ease of editing, at
+runtime these templates gets rendered into the exact same layouts and
+partials that you would use if you were building from scratch. Its jsut
+that now you can see what your pages will render like in your wysiwyg html
+editor and change and layout accordingly. Additionally MasterView supplies some javascript
+to show only one action view at time (list, new, show, edit, destroy) so
+you can view in your browser without running in Rails. Dummy html can be
+included to improve the accuracy of the page which can be easily removed at
+runtime. To make it easier to work with in an editor, design time
+stylesheets are included in the file to allow you to hide all sections
+except the one you are working on, simply uncomment the appropriate
+stylesheet for the section you would like to work with.
+</p>
+<h2>Using the MasterView Admin Controller</h2>
+<p>
+The MasterView admin controller/view is used by a MasterView developer
+to obtain a birds-eye view of all your
+masterview templates, the status of those templates (OK, Invalid xhtml,
+Conflicts, Imports outdated), the details regarding the status, and the
+ultimate erb files generated from each template.
+The admin controller also displays a summary of your current configuration.
+</p>
+<p>The MasterView admin controller is enabled or disabled in your application
+by the Master <code>enable_admin_pages</code> configuration setting.
+By default, the admin controller is enabled.
+See the <a href="configuration.html">MasterView Configuration Guide</a> for details.
+</p>
+<p>
+When enabled, the MasterView admin controller is available in your application
+at <a href="http://yourserver/masterview">http://yourserver/masterview</a>.
+The Admin home page displays an overview of your application's templates
+and links to admin information and operations.
+</p>
+<p>
+Since it can be difficult to import a layout by hand into a new file, the
+MasterView admin controller has a
+link where you can copy the layout into a new file by providing the new
+files Action. It will take the layout from the template chosen and create a
+new file <code><i>controller</i>_<i>action</i>.html</code> with the layout imported
+and a shell for the new Action code.
+</p>
+<p>
+As described in the following section, youcan also do this from command line using rake:
+</p>
+<pre class="code">
+rake mv:copy_layout TEMPLATE=foo_list.html ACTION=newaction
+</pre>
+<h3>Using Rake for MasterView Admin Operations</h3>
+<p>All of the power of the MasterView admin controller is
+also available via a set of rake commands.
+MasterView includes a <code>masterview.rake</code> file in your
+<code>vendor/plugins/masterview/tasks</code> directory which is automatically included
+by the top level Rails Rakefile, so the masterview <b>mv:</b> admin tasks
+are automatically available in your application's rake tasks
+when the MasterView plugin is installed.
+</p>
+<p>
+In a command shell, cd to your Rails application directory and use rake commands of the form:
+</p>
+<pre class="code">
+rake mv:list
+rake mv:list_all
+rake mv:rebuild
+rake mv:rebuild_all
+rake mv:copy_layout
+</pre>
+<p>To obtain further information about the supported commands,
+run the standard rake tasks report using the <code>--tasks</code> (<code>-T</code>) option:</p>
+<pre class="code">
+rake -T
+</pre>
+</div>  <!-- bodyContent -->
+</div>
+<div id="pageFooter">
+<div>
+&middot;&nbsp;
+<a href="./index.html">Doc Home</a>
+&nbsp;|&nbsp;
+<a href="./installation.html">Installation</a>
+&nbsp;|&nbsp;
+<a href="./configuration.html">Configuration</a>
+&nbsp;|&nbsp;
+<a href="./guide.html">Usage</a>
+&nbsp;|&nbsp;
+<a href="./directives.html">Directives</a>
+&nbsp;&middot;
+</div>
+<table summary="layout area">
+<tbody>
+<tr>
+<td class="copyright">&copy;&nbsp;Copyright MasterView 2006</td>
+<td class="validators">
+  <a href="http://validator.w3.org/check/referer">[Valid XHTML]</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</body>
+</html>

data/doc/index.html ADDED Viewed

@@ -0,0 +1,287 @@
+<?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>MasterView - Rails-optimized (x)html friendly template engine</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+  <meta http-equiv="Content-Script-Type" content="text/javascript" />
+  <link href="./stylesheets/masterview.css" rel="stylesheet" type="text/css" />
+</head>
+<body>
+<div id="pageHeader">
+<div>MasterView Template Engine</div>
+<div class="description">Rails-optimized (x)html friendly template engine</div>
+</div>
+<div id="pageBody">
+<div id="bodyContent" mv:generate="{template_path}" mv:omit_tag="">
+<h1>MasterView - Rails-optimized (x)html friendly template engine</h1>
+<p>
+MasterView is a ruby/rails
+optimized HTML/XHTML friendly template engine. It is designed to use the
+full power and productivity of rails including layouts, partials, and rails
+html helpers while still being editable/styleable in a WYSIWYG HTML editor.
+</p>
+<p>
+MasterView is distributed as a gem
+or a plugin. You may install it as a gem and then generate a lightweight
+plugin which mainly refers to the gem <b>or</b> you can simply install as a
+plugin which is self contained. I personally prefer installing as a gem for
+ease of management, however if you are running at a shared hosting
+environment you might not have authority to install this gem so you may
+install as a self contained plugin.
+</p>
+<p>
+If you are interested in the background story behind all this, it is at the
+end of this page.
+</p>
+<table summary="project location and author information">
+<tr>
+  <td>Author:</td>
+  <td>Jeff Barczewski (jeff.barczewski <span class="class"> @ </span> gmail.com)</td>
+</tr>
+<tr><td>Primary developers:</td><td>Jeff Barczewski, Deb Lewis</td></tr>
+<tr>
+  <td>Website:</td>
+  <td><a href="http://masterview.org">masterview.org</a></td>
+</tr>
+<tr>
+  <td>Rubyforge project:</td>
+  <td><a href="http://rubyforge.org/projects/masterview/">masterview</a></td>
+</tr>
+<tr><td>License:</td><td>MIT open source license (like Rails)
+</td></tr>
+<tr>
+<td>Mailing lists:</td>
+<td>Join mailing lists at <a href="http://rubyforge.org/mail/?group_id=1290">rubyforge.org</a></td>
+</tr>
+<tr>
+<td>&nbsp;</td>
+<td>masterview-announce - MasterView release announcements</td>
+</tr>
+<tr>
+<td>&nbsp;</td>
+<td>masterview-users - Discussion, problems, ideas, suggestions for MasterView</td>
+</tr>
+<tr>
+<td>&nbsp;</td>
+<td>masterview-devel - MasterView project developer list</td>
+</tr>
+<tr><td>Videos:</td><td><a href="http://masterview.org/videos/masterview_quick_start.html">MasterView Quick Start Video</a> - demonstrating basic usage of MasterView (no audio)</td></tr>
+</table>
+<h2>Goals</h2>
+<ul>
+<li>Create/extend a template engine for rails that would be XHTML friendly and
+thus could be edited/styled with a WYSIWYG HTML editor even late in
+development without breaking template.
+</li>
+<li>Keep it simple. DRY. No extra config files, simple syntax with ruby flavor.
+</li>
+<li>Design it specifically for ruby and rails. Use the full power and not be
+limited in its capabilities over what can be done with ERb
+</li>
+<li>Work nicely with layouts, partials, and rails html helpers.
+</li>
+<li>Reduce complexity, work with existing rails code, no extra view logic or
+hashes than what is used by ERb. Scaffold generate initial templates or
+work from existing html prototype.
+</li>
+<li>Reduce the numbers of files, simplifying editing. Define partials and
+layouts naturallyl right in the template, no need to go to another file.
+</li>
+<li>Preview in browser without running an app. Allow for dummy data in the
+template so that the page can be viewed and styled independently of the
+application.
+</li>
+<li>Performance equal to ERb
+</li>
+</ul>
+<h2>Prerequisites</h2>
+<table summary="prerequisites summary">
+<tr><td valign="top">Requires:</td><td>No external dependencies
+</td></tr>
+<tr><td valign="top">Optional:</td><td>tidy, log4r</td></tr>
+</table>
+<p>See the <a href="installation.html">MasterView Installation Guide</a> for details.</p>
+<h2>Installation and Configuration</h2>
+<p>See the <a href="installation.html">MasterView Installation Guide</a> for complete installation instructions.</p>
+<p>See the <a href="configuration.html">MasterView Configuration Guide</a> for informatino about customizing the MasterView configuration settings for your application.</p>
+<h2>Usage</h2>
+<p>See the <a href="guide.html">MasterView User's Guide</a> for information on using MasterView templates and supporting services.</p>
+<h2>MasterView attribute directive syntax</h2>
+<p>See the <a href="directives.html">MasterView Directives Reference</a> for complete descriptions of all the standard built-in MasterView directives.</p>
+<h2>Background story</h2>
+<p>
+I came from a Java Struts environment when I was introduced to Ruby. I was
+just in the process of evaluating Tapestry and JSF when I learned about
+Rails. Ruby and Rails changed my world forever. I had to however drop many
+of my bad habits aquired from years of Java and C++ work. I had to embrace
+the new ideas and approach things now with a different mindset. (If you
+ever have a chance to hear Dave Thomas speak, you will know what I mean. He
+has a wonderfully entertaining yet enlightening way of illustrating this.)
+</p>
+<p>
+After learning the Ruby and Rails way, (Thank you Matz and DHH for such
+wonderful gifts to the world) I was amazed at how productive this
+environment is. Programming was fun once again, and everything you do in
+Ruby or Rails is easier than any other language or framework I have ever
+seen. Even taking into account having to learn something new, I was still
+far more productive than ever before. The only thing that I felt that could
+be done better, was to have a nice html friendly templating engine so that
+designers and developers could work collaboratively together on a project.
+The designers could style and layout the pages with their WYSIWYG HTML
+editors and developers would have the full power of Ruby and Rails without
+having to jump through extra hoops to use them. I looked at the available
+html template engines to see if anything fit with my style. I was
+disappointed with each of them, mainly because they all made it harder than
+straigt ERb (rhtml) and were not able to use layouts and partials easily.
+</p>
+<p>
+After all the hard work so many people have put into Ruby and Rails, I
+wanted to see if there was anyway I could contribute as well, maybe
+extending one of the existing template projects to have the ideal
+functionality I was striving for. I wanted something to make my own web
+development even more productive. However after reviewing each of them and
+even getting into the source code, the closest ones seemed to be Amrita2,
+Liquid, and Kwartz. Unfortunately it was not going to be easy to add the
+functionality and usability I desired.
+</p>
+<p>
+During my research I learned that many of the rails gurus were putting down
+html template engines because they felt that they handicapped the developer
+severely, namely by not taking advantage of rails layouts, partials, and
+html helpers. After doing some projects with ERb (rhtml) I realized that
+they were right. I too did not want to give up any of that power either. I
+also didn&#8217;t want to create a bunch of extra code or config to use the
+templates (extra view code, or data structures to pass to the templates) as
+so many of the other engines relied on.
+</p>
+<p>
+I expanded my search outside of Ruby for the best html template technology
+I could find. After reviewing all the front runners I still didn&#8217;t
+find anything that quite met with my goals for developing with ruby and
+rails. I also didn&#8217;t find any technology that was close enough that I
+could adapt it. However I did come across features in a variety of systems
+that inspired me, and helped me shape the ideas that are presented here. A few
+of those systems were Tapestry, Zope/PHP TAL, Kwartz, Amrita 2, Liquid,
+and Web Objects.
+</p>
+<p>
+After putting much thought into all the possible options I could not see
+extending an existing template engine to meet my needs. And since I wanted
+this engine to have all the power of ruby and rails, it seemed that I would
+be best served by developing a html template syntax that was a thin layer
+above ERb. That way it would be intuitive to use (not having to learn yet
+another syntax) yet very powerful. Once I was able to come up with the
+desired syntax and approach it became apparent that this would also be
+fairly straightforward to build.
+</p>
+<p>
+I ran the concept by the guys at the St. Louis Ruby Group <a
+href="http://stlruby.org">stlruby.org</a> and they were excited about the
+project. With their help I was able to simply some of the confusing or
+complicated areas before beginning development. They also sparked some
+ideas about how to make this infinitely extensible such that developers
+could easily add their own attribute directives. This would give them the
+power to create custom extensions that would encapsulate some of their
+development work. This would serve a couple needs, it would not only make
+this engine extensible, it would also allow this engine to grow easily
+being composed of small pluggable attribute directives. Many thanks to the
+members of this group, I continue to enjoy discussing the power of Ruby and
+learning from each of them on a monthly basis.
+</p>
+<p>
+While I am on the subject of thanks, I would like to thank my wife and
+daughter for their support as I took time away from them to work on this
+project and I want to thank God for bringing the right people into my life
+just when I needed them and for bringing me on this wonderful journey, I am
+so very blessed. May I be able to give back some of what has been given to
+me.
+</p>
+<p>
+And one more mention of tremendous thanks to Deb Lewis, the other core developer on the
+team, she has spent countless hours reviewing, revising, and improving the codebase,
+configuration, and documentation. The project wouldn't be half of what it is today
+without all her help, inspiration, and hard work. I thoroughly enjoy working and
+debating the finer points of the project with her each step of the way.
+</p>
+<p>
+So that&#8217;s the story, I hope that many of you will find MasterView to be a useful tool for
+your development. I am continuing to refine MasterView by using it daily for
+Genesis Ministry sites and all my web projects. I know that there is much
+more work needed in documentation, examples, test cases, additional
+directives, etc., so I would appreciate any feedback and ideas that you
+have. Thanks for taking the time to review MasterView!
+</p>
+<p>
+Jeff Barczewski
+(jeff.barczewski
+<span class="class"> @ </span>
+gmail.com)
+</p>
+</div>  <!-- bodyContent -->
+</div>
+<div id="pageFooter">
+<div>
+&middot;&nbsp;
+<a href="./index.html">Doc Home</a>
+&nbsp;|&nbsp;
+<a href="./installation.html">Installation</a>
+&nbsp;|&nbsp;
+<a href="./configuration.html">Configuration</a>
+&nbsp;|&nbsp;
+<a href="./guide.html">Usage</a>
+&nbsp;|&nbsp;
+<a href="./directives.html">Directives</a>
+&nbsp;&middot;
+</div>
+<table summary="layout area">
+<tbody>
+<tr>
+<td class="copyright">&copy;&nbsp;Copyright MasterView 2006</td>
+<td class="validators">
+  <a href="http://validator.w3.org/check/referer">[Valid XHTML]</a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</body>
+</html>