masterview 0.2.5 → 0.3.0

data/TODO

@@ -1,31 +1,28 @@
-- put image, stylesheets, javascript relative path regex in initializer
+TODO LIST
 - create install.rb for rails 1.1 plugin installs, it will create config/masterview and some sample configs
 - create namespace for mv and publish, update generated files
 - more videos
-- allow multiple namespace prefixes for directives (allow custom directives to declare their own namespace)
-- publish .xsd namespace definition for builtin directives to enable xhmtl docs using mv markup to validate
+- publish .xsd namespace definition for builtin directives to enable xhtml docs using mv markup to validate
 - wiki for site
 - render from db
 - app for syntax
 - include additional stylesheets
 - ajax examples
 - ajax table component
-- fix admin controller config page so it fits into admin layout
+- improve directives info page in admin controller
+    - add link to directives rdoc from Loaded Directives page
 - documentation
     - update the plugin generator descr in installation.html: also installs config file templates in config
     - add tips in installation.doc about running gems rdoc server to view installed gems' rdoc
     - update admin controller description to point out that it installs public/stylesheets/masterview
     - run spelling checker on our html and release docs; retrofit to rdoc comments
-- directive developer documentation and examples
+    - build utility to auto-generate directives reference doc from directive metadata and std. rdoc markup
+    - add doc on directive impl unit test helper and techniques/examples
 - more tests
 - build improvements
     - add release tasks to automate archiving trunk to tags/masterview-N.N.N, resetting tags/masterview
 - investigate mirror sites for obtaining gems (supplement primary rubyforge host)
 - improve RubyForge project site: include online docs; post release msgs in news
-- internal code cleanup 
-    - DirectiveHelpers ERB_xx constants to differentiate ' %>' and ' -%>'
-    - replace MasterView::NamespacePrefix+'<gen/import directivename>' concats in parser/analyzer with directive attr name constants
-    - run spell checker on doc/*.html, ripple typo fixes back in rdoc comment
 - reverse engineer legacy rhtml into masterview templates
 
 --####################
@@ -36,29 +33,16 @@
 
 - make tidy installation easier
 
-DSL for creating directives
-maybe something like
 
-event :stag do |e|
-  # these read args consecutively out of parse(attr_value)
-  e.attr_arg :object, :quote_if => true
-  e.attr_arg :foo { |t| t.upcase } # modifying case of foo
-  e.attr_arg :link_name { self.content } #overriding with different value
-  e.attr_arg :options, :optional => {} # specify that is optional but provide default if it is needed 
-  e.attr_arg :html_options, :merge_common => true, :merge => [:size, :rows] # merge in common and specified attributes
-  
-  a = a+1 # do some other logic
+- clean up rhtml files when switching from write rhtml files to filesystem to direct erb, otherwise written files will take precedence over MV internals.
 
-  old_content = e.content # retrieving content of tag
-  e.content = 'foo' # resetting content of tag
-  yield_contents = e.yield()
+- build patch to send to rails core team improving hooks for template engines, removing file system dependency
 
-  e.erb_code_render 'a = a + 1' # render <% a = a + 1 %>
-  e.erb_content_render 'text_area' args(:object, :foo, :link_name, :options, :html_options) # render <%= %>, args handles joining the args with comma, and also takes into account if last args are not empty that other args are either provided also or defaulted.
+- make admin pages localhost lockdown configurable rather than simple only available from localhost
 
-  e.render 'direct render' # direct render as is
-end
+- create DirectiveHelpers.parse_string_into_hash
+- create DirectiveHelpers.serialize_hash_to_attributes # refactor attr directive code into here
 
-- default generate to *.rhtml if nothing is specified
+- liquid directives or other non-evaling safe mode which allows user created templates or parts
 
-  
+- handle all xml syntax including processing_instruction, attlistdecl, elementdecl, entitydecl, notationdecl

data/doc/about.html

@@ -0,0 +1,246 @@
+<?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">
+<a href="index.html"><img id="logo" src="images/masterview_logo.png" alt="MasterView Rails-optimized (x)html friendly template engine"/></a>
+</div>
+
+<div id="headerNav">
+<div>
+&middot;&nbsp;
+<a href="./index.html">Doc Home</a>
+&nbsp;|&nbsp;
+<a href="./about.html">About</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;|&nbsp;
+<a href="./developer.html">Developers</a>
+&nbsp;|&nbsp;
+<a href="./media_list.html">Screencasts</a>
+&nbsp;&middot;
+</div>
+</div>
+
+<div id="pageBody">
+<div id="bodyContent">
+
+<h1>About MasterView</h1>
+
+<h2>Why another templating engine?</h2>
+<p>In short, I needed a way to be able to use a WYSIWYG editor to design/layout my rails pages and didn't want to give up the power and productivity of layouts, partials, and rails helpers. I needed to be able to create html templates quickly that could be handed off to a graphic designer for complex styling, and then use those html templates directly in the project. I also needed to be able to take existing html prototypes and easily make them real. I wanted to be able to give these html templates back to the designer at anytime throughout the project if the style or layout needs to be updated. The existing templating solutions did not meet all my goals or desired operation. For more information, read the background story below.
+</p>
+
+<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>Utilize 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>Production ready generated templates - Make generated scaffolding templates
+useable for production. Build in proper structure and style hooks. Provide simple
+CSS for style and color usage. Fully generate labels and fields so that
+it will be simple to reorder or remove things from views there by eliminating much
+of the re-work necessary to build out real-world views.
+
+</li>
+<li>Reduce the numbers of files, simplifying editing. Define partials and
+layouts naturally 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>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
+straight 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"> (at) </span>
+gmail (dot) com)
+</p>
+
+
+</div>  <!-- bodyContent -->
+</div>
+
+<div id="pageFooter">
+<div>
+&middot;&nbsp;
+<a href="./index.html">Doc Home</a>
+&nbsp;|&nbsp;
+<a href="./about.html">About</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;|&nbsp;
+<a href="./developer.html">Developers</a>
+&nbsp;|&nbsp;
+<a href="./media_list.html">Screencasts</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"><img
+          src="http://www.w3.org/Icons/valid-xhtml10" class="w3c_validator"
+          title="Valid XHTML 1.0!" alt="Valid XHTML 1.0!" /></a>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+
+</body>
+</html>

data/doc/configuration.html

@@ -1,8 +1,8 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html 
+<!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>
 
@@ -25,6 +25,8 @@
 &middot;&nbsp;
 <a href="./index.html">Doc Home</a>
 &nbsp;|&nbsp;
+<a href="./about.html">About</a>
+&nbsp;|&nbsp;
 <a href="./installation.html">Installation</a>
 &nbsp;|&nbsp;
 <a href="./configuration.html">Configuration</a>
@@ -32,8 +34,10 @@
 <a href="./guide.html">Usage</a>
 &nbsp;|&nbsp;
 <a href="./directives.html">Directives</a>
-&nbsp;&nbsp;
-<a href="./media_list.html">Media (Videos/Illustrations)</a>
+&nbsp;|&nbsp;
+<a href="./developer.html">Developers</a>
+&nbsp;|&nbsp;
+<a href="./media_list.html">Screencasts</a>
 &nbsp;&middot;
 </div>
 </div>
@@ -41,7 +45,7 @@
 <div id="pageBody">
 <div id="bodyContent">
 
-<h1>MasterView - Configuration Guide</h1>
+<h1>MasterView Configuration Guide</h1>
 
 <p><span class="productName">MasterView</span> supports a number of options for configuring its operation.</p>
 
@@ -61,7 +65,7 @@
 that are suitable for a typical Rails application.
 The goal is to allow Rails application developers to use
 the <span class="productName">MasterView</span> plugin "out of the box",
-with little or no initial setup effort: simply install the 
+with little or no initial setup effort: simply install the
 <span class="productName">MasterView</span> plugin in a rails application
 and start using the template engine facilities in its views.
 </p>
@@ -69,11 +73,11 @@ and start using the template engine facilities in its views.
 <h2>Using MasterView in a Rails Application</h2>
 
 <p>The standard configuration of <span class="productName">MasterView</span> in
-a Rails application is to search for MasterView templates (*.html) in the normal 
+a Rails application is to search for MasterView templates (*.html) in the normal
 <code>RAILS_ROOT/app/views</code> directory and for rails to load the generated
 rhtml directly from <span class="productName">MasterView</span> internally. If config.generate_rhtml is set to true
-(default is false) then <span class="productName">MasterView</span> will generate its intermediate rhtml to the standard 
-<code>RAILS_ROOT/app/views</code> directory and Rails will pick it up from there 
+(default is false) then <span class="productName">MasterView</span> will generate its intermediate rhtml to the standard
+<code>RAILS_ROOT/app/views</code> directory and Rails will pick it up from there
 as normal.
 
 The <code>mv:</code> attribute markup in the masterview templates determines
@@ -83,11 +87,11 @@ the content of the generated rhtml view templates, which are then used by the Ra
 By default, all masterview templates are parsed during rails application startup to ensure
 that generated rhtml views are up-to-date for the application.
 In a development environment, when Rails is reloading changed classes to dynamically
-update the application code as you make changes, 
+update the application code as you make changes,
 <span class="productName">MasterView</span> will automatically
 detect changes you make to your masterview templates and regenerate the rails rhtml views.
 This ability to dynamically modify your rails application during development
-is a key factor for the productivity of Rails developers, so 
+is a key factor for the productivity of Rails developers, so
 the <span class="productName">MasterView</span> designers have ensured
 that you continue to have this capability when using masterview templates.
 </p>
@@ -112,10 +116,10 @@ to configure settings specifically for your development environment).
 
 <h3>Sample <code>config/masterview/settings.rb</code> in a Rails Application</h3>
 
-<pre><code>
+<pre class="code">
     # Application configuration settings for the MasterView template engine.
-    # Run at plugin load time during Rails startup (after the base rails 
-    # framework is loaded and before the application's own startup logic 
+    # Run at plugin load time during Rails startup (after the base rails
+    # framework is loaded and before the application's own startup logic
     # in its config/environment.rb is run).
     #
     # Set standard application
@@ -126,24 +130,23 @@ to configure settings specifically for your development environment).
 
     # Only use the MasterView admin pages for development
     config.enable_admin_pages = false
-    
+
     # modify the default logging level from WARN to ERROR (only want to see serious errors)
     config.logger = 'log4r'
     config.log_level = 'ERROR'
-    config.after_initialize { 
+    config.after_initialize {
       # we shouldn't see any of these in the log
-      MasterView.Log.debug "LOG CONFIG TEST: debug log entries suppressed at ERROR level" 
-      MasterView.Log.info "LOG CONFIG TEST: info log entries suppressed at ERROR level" 
-      MasterView.Log.warn "LOG CONFIG TEST: warning log entries suppressed at ERROR level" 
+      MasterView.Log.debug "LOG CONFIG TEST: debug log entries suppressed at ERROR level"
+      MasterView.Log.info "LOG CONFIG TEST: info log entries suppressed at ERROR level"
+      MasterView.Log.warn "LOG CONFIG TEST: warning log entries suppressed at ERROR level"
       # so this is the only log message that should get through
       #MasterView.Log.error "LOG CONFIG TEST: only serious messages are reported at ERROR level"
     }
-
-</code></pre>
+</pre>
 
 <h3>Sample <code>config/masterview/environments/development.rb</code> in a Rails Application</h3>
 
-<pre><code>
+<pre class="code">
     # Application configuration settings for the MasterView template engine.
     #
     # Set development-mode config settings here
@@ -153,8 +156,7 @@ to configure settings specifically for your development environment).
 
     # include debug and all info/warning/error log messages during development
     config.log_level = 'DEBUG'
-    
-</code></pre>
+</pre>
 
 <h2>Using MasterView outside Rails</h2>
 
@@ -163,14 +165,14 @@ used independently of the Rails application context.
 Outside Rails, you need to explicitly run the <code>MasterView::Initializer</code>
 in your application startup code.
 While the Rails framework handles masterview loading automatically through its
-framework startup and plugin loading facilities, 
+framework startup and plugin loading facilities,
 with configuration settings files obtained from standard locations within the
 overall structure of a rails application,
 a non-rails application using the MasterView template engine needs to initiate
 loading the template engine and providing it with configuration information.
 </p>
 
-<pre><code>
+<pre class="code">
     require 'masterview/initializer'
     config = MasterView::Configuration( :app_root_path = '/path/to/my/app' )
     # This app has simple config, so it won't use the config files scheme used in Rails.
@@ -178,7 +180,7 @@ loading the template engine and providing it with configuration information.
     config.template_src_dir_path = 'masterview/templates'  # rel path from app's root_path
     config.template_dst_dir_path = 'masterview/output'
     Masterview::Initializer(:process, config)
-</code></pre>
+</pre>
 
 <hr />
 <a name="mv_options_ref" />
@@ -311,7 +313,7 @@ Use <code>config.template_src_dir_abs_path(abs_path)</code> to specify the templ
 <br />{root_path}/masterview/output<br />(non-rails app)</td>
 <td class="description">Path to the directory where Masterview template output (rhtml) will be generated.
 <div class="explanation">
-Specify the location of your template output directory as a relative path from 
+Specify the location of your template output directory as a relative path from
 the application's <code>root_path</code>.
 Use <code>config.template_dst_dir_abs_path(abs_path)</code> to specify the template output directory as an absolute path.
 </div>
@@ -389,7 +391,7 @@ with the pathname of the source template file.
 <tr>
 <td>&nbsp;</td>
 <td class="default"><b>:default_generate</b> => true</td>
-<td class="description">Ensure that a mv:generate or mv:gen_partial is present in a template, 
+<td class="description">Ensure that a mv:generate or mv:gen_partial is present in a template,
 otherwise add a mv:generate="{template_path}" to the body tag if one is present or the root
 element. If a body tag is present and mv:generate is being added then also add mv:omit_tag="".</td>
 </tr>
@@ -401,7 +403,12 @@ element. If a body tag is present and mv:generate is being added then also add m
 <tr>
 <td class="setting">namespace_prefix</td>
 <td class="default">mv:</td>
-<td class="description">XML name space prefix for MasterView directive attributes in template html.</td>
+<td class="description">XML name space prefix for built-in MasterView directive attributes in template html.</td>
+</tr>
+<tr>
+<td class="setting">namespace_prefix_extensions</td>
+<td class="default">mvx:</td>
+<td class="description">XML name space prefix for addon MasterView directive attributes in template html.</td>
 </tr>
 <tr>
 <td class="setting">inline_erb_start</td>
@@ -447,13 +454,13 @@ element. If a body tag is present and mv:generate is being added then also add m
 <tr>
 <td class="setting">reparse_changed_masterview_templates</td>
 <td class="default">true if both template parsing at startup and ActionController class reloading are enabled</td>
-<td class="description">Boolean which determines whether masterview templates are automatically reparsed if the template changes after initial application loading.
+<td class="description">Boolean which determines whether masterview templates are automatically reparsed if the template changes after initial application loading. Note: If ActionController::Base.perform_caching is true (default true in production), compiled rhtml is cached and MasterView will not check for modified templates.
 </td>
 </tr>
 <tr>
 <td class="setting">enable_admin_pages</td>
 <td class="default">true for development, otherwise false</td>
-<td class="description">Enable MasterView admin pages in the rails application. 
+<td class="description">Enable MasterView admin pages in the rails application.
 <!--Too clever, just set the default and be done with it:
 If config/masterview/environments/development.rb was created during installation then the default is true in development mode (false by default in production unless changed in settings.rb).
 -->
@@ -463,7 +470,7 @@ If config/masterview/environments/development.rb was created during installation
 <tr>
 <td class="setting">enable_view_rhtml</td>
 <td class="default">true for development, otherwise false</td>
-<td class="description">Enable MasterView admin pages in a rails application to be able to view the generated rhtml. When enabled it creates links on the list page to click to view the rhtml source. Requires that enable_admin_pages is true.  
+<td class="description">Enable MasterView admin pages in a rails application to be able to view the generated rhtml. When enabled it creates links on the list page to click to view the rhtml source. Requires that enable_admin_pages is true.
 <!--Too clever, just set the default and be done with it:
 If config/masterview/environments/development.rb was created during installation then the default is true in development mode (false by default in production unless changed in settings.rb).
 -->
@@ -495,6 +502,8 @@ If config/masterview/environments/development.rb was created during installation
 &middot;&nbsp;
 <a href="./index.html">Doc Home</a>
 &nbsp;|&nbsp;
+<a href="./about.html">About</a>
+&nbsp;|&nbsp;
 <a href="./installation.html">Installation</a>
 &nbsp;|&nbsp;
 <a href="./configuration.html">Configuration</a>
@@ -502,8 +511,10 @@ If config/masterview/environments/development.rb was created during installation
 <a href="./guide.html">Usage</a>
 &nbsp;|&nbsp;
 <a href="./directives.html">Directives</a>
-&nbsp;&nbsp;
-<a href="./media_list.html">Media (Videos/Illustrations)</a>
+&nbsp;|&nbsp;
+<a href="./developer.html">Developers</a>
+&nbsp;|&nbsp;
+<a href="./media_list.html">Screencasts</a>
 &nbsp;&middot;
 </div>
 <table summary="layout area">
@@ -511,7 +522,9 @@ If config/masterview/environments/development.rb was created during installation
 <tr>
 <td class="copyright">&copy;&nbsp;Copyright MasterView 2006</td>
 <td class="validators">
-  <a href="http://validator.w3.org/check/referer">[Valid XHTML]</a>
+  <a href="http://validator.w3.org/check/referer"><img
+          src="http://www.w3.org/Icons/valid-xhtml10" class="w3c_validator"
+          title="Valid XHTML 1.0!" alt="Valid XHTML 1.0!" /></a>
 </td>
 </tr>
 </tbody>