[Jifty-commit] r7553 - in Template-Declare/branches/mixmaster: lib/Template lib/Template/Declare
Jifty commits
jifty-commit at lists.jifty.org
Thu Oct 15 14:59:27 EDT 2009
Author: theory
Date: Thu Oct 15 14:59:27 2009
New Revision: 7553
Added:
Template-Declare/branches/mixmaster/t/pod-spelling.t
Modified:
Template-Declare/branches/mixmaster/lib/Template/Declare.pm
Template-Declare/branches/mixmaster/lib/Template/Declare/TagSet.pm
Template-Declare/branches/mixmaster/lib/Template/Declare/Tags.pm
Log:
I kant spel. kan yoo?
Modified: Template-Declare/branches/mixmaster/lib/Template/Declare.pm
==============================================================================
--- Template-Declare/branches/mixmaster/lib/Template/Declare.pm (original)
+++ Template-Declare/branches/mixmaster/lib/Template/Declare.pm Thu Oct 15 14:59:27 2009
@@ -97,7 +97,7 @@
=item *
-"Native" XML namespace and declarator support
+"Native" XML namespace and declaration support
=item *
@@ -178,7 +178,7 @@
=item helper
A subroutine used in templates to assist in the generation of output, or in
-template classes to assit in the mixing-in of templates. Output helpers
+template classes to assist in the mixing-in of templates. Output helpers
include C<outs()> for rending text output and C<xml_decl()> for rendering XML
declarations. Mixin helpers include C<into> for specifying a template class to
mix into, and C<under> for specifying a path prefix under which to mix
@@ -225,7 +225,7 @@
dealing with templates. The second thing is to C<use Template::Declare::Tags>
to import the set of tag subroutines you need to generate the output you want.
In this case, we've imported tags to support the creation of XUL. Other tag
-sets incdlude HTML (the default), and RDF.
+sets include HTML (the default), and RDF.
Templates are created using the C<template> keyword:
@@ -238,7 +238,7 @@
the output for the template.
The the tag subs imported into your class take blocks as arguments, while a
-number of helper subs take other arguments. For exmaple, the C<xml_decl>
+number of helper subs take other arguments. For example, the C<xml_decl>
helper takes as its first argument the name of the XML declaration to be
output, and then a hash reference of the attributes of that declaration:
@@ -275,7 +275,7 @@
print Template::Declare->show( 'main' );
The path passed to C<show> can be either C<main> or </main>, as you prefer. In
-either event, the output woud look like this:
+either event, the output would look like this:
<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>
@@ -380,7 +380,7 @@
=item *
In the same way, note that the C<simple> template expects an additional
-argument, a username.
+argument, a user name.
=item *
@@ -476,7 +476,7 @@
_underscores_ and turns them into C<< <em>emphasis</em> >> HTML elements.
We then execute both the C<before> and the C<after> templates with the output
-ening up as:
+ending up as:
<h1>Welcome to
<em>my</em> site. It's
@@ -519,7 +519,7 @@
};
Here we have two template classes; the second, C<MyApp::Templates::BlogPost>,
-inherits from the firt, C<MyApp::Templates::GeniricItem>. Note also that
+inherits from the first, C<MyApp::Templates::GeniricItem>. Note also that
C<MyApp::Templates::BlogPost> overrides the C<item> template. So execute these
templates:
@@ -811,7 +811,7 @@
The second template class, C<MyApp::Templates>, mixes C<MyApp::UtilTemplates>
into itself under the path C</util> and defines a C<get_title()> method as
required by the mixin. Then, its C<story> template calls the mixed-in template
-as C<util/content>, becaus the C<content> template was mixed into the current
+as C<util/content>, because the C<content> template was mixed into the current
template under C</util>. Get it?
Now we can use the usual template invocation:
@@ -837,7 +837,7 @@
Mixins are a very useful tool for template authors to add functionality to
their template classes. But it's important to pay attention to the mixin
-contracts so that you're sure to implement the required API in your temlate
+contracts so that you're sure to implement the required API in your template
class (here, the C<get_title()> method).
=head3 Aliases
@@ -867,7 +867,7 @@
};
};
-Note the use of teh C<img_path()> method defined in the template class and
+Note the use of the C<img_path()> method defined in the template class and
used by the C<sidebar> template. Now let's use it:
package MyApp::Render;
@@ -962,7 +962,7 @@
alias My::UI::Widgets into Your::UI::View under '/widgets';
-Now the templates defined in C<Your::UI::View> are availabie in
+Now the templates defined in C<Your::UI::View> are available in
C<My::UI::Widgets> under C</widgets>. The C<mix> method supports this syntax
as well, though it's not necessarily recommended, given that you would not be
able to fulfill any contracts unless you re-opened the class into which you
@@ -970,8 +970,8 @@
find this functionality useful for automatically aliasing template classes
into a single dispatch template class.
-Another trick is to alias or mix your templats with package variables specific
-to the composition. Do so via the C<setting> keyword:
+Another trick is to alias or mix your templates with package variables
+specific to the composition. Do so via the C<setting> keyword:
package My::Templates;
mix Some::Mixin under '/mymix', setting { name => 'Larry' };
@@ -1114,7 +1114,7 @@
theis keyword, C<mix> will mix them into the calling class.
For those who prefer a direct OO syntax for mixins, just call C<mix()> as a
-method on the class to be mixed in. To replicate the above three exmaples
+method on the class to be mixed in. To replicate the above three examples
without the use of the sugar:
Some::Clever::Mixin->mix( '/mixin' );
@@ -1153,7 +1153,7 @@
Without this keyword, C<alias> will alias them into the calling class.
For those who prefer a direct OO syntax for mixins, just call C<alias()> as a
-method on the class to be mixed in. To replicate the above three exmaples
+method on the class to be mixed in. To replicate the above three examples
without the use of the sugar:
Some::Clever:Templates->alias( '/delegate' );
Modified: Template-Declare/branches/mixmaster/lib/Template/Declare/TagSet.pm
==============================================================================
--- Template-Declare/branches/mixmaster/lib/Template/Declare/TagSet.pm (original)
+++ Template-Declare/branches/mixmaster/lib/Template/Declare/TagSet.pm Thu Oct 15 14:59:27 2009
@@ -59,7 +59,7 @@
Template::Declare::TagSet is the base class for declaring packages of
Template::Delcare tags. If you need to create new tags for use in your
-temlates, this is the base class for you! Review the source code of
+templates, this is the base class for you! Review the source code of
L<Template::Declare::TagSet::HTML|Template::Declare::TagSet::HTML> for a
useful example.
Modified: Template-Declare/branches/mixmaster/lib/Template/Declare/Tags.pm
==============================================================================
--- Template-Declare/branches/mixmaster/lib/Template/Declare/Tags.pm (original)
+++ Template-Declare/branches/mixmaster/lib/Template/Declare/Tags.pm Thu Oct 15 14:59:27 2009
@@ -223,7 +223,7 @@
C<MyApp::Templates> in the previous example.
There may be cases when you want to specify a different Perl package for a
-perticular XML namespace. For instance, if the C<html> Perl package has
+particular XML namespace. For instance, if the C<html> Perl package has
already been used for other purposes in your application and you don't want to
install subs there and mess things up, use the C<package> option to install
them elsewhere:
@@ -266,7 +266,7 @@
}
};
-Declares a template in the current package. The first agument to the template
+Declares a template in the current package. The first argument to the template
subroutine will always be a C<Template::Declare> object. Subsequent arguments
will be all those passed to C<show()>. For example, to use the above example
to output a select list of colors, you'd call it like so:
@@ -338,7 +338,7 @@
show( main => { user => 'Bob' } );
-Displays templates. The first agument is the name of the template to be
+Displays templates. The first argument is the name of the template to be
displayed. Any additional arguments will be passed directly to the template.
C<show> can either be called with a template name or a package/object and a
@@ -346,7 +346,7 @@
If called from within a Template::Declare subclass, then private templates are
accessible and visible. If called from something that isn't a
-Template::Declare, only public templates wil be visible.
+Template::Declare, only public templates will be visible.
From the outside world, users can either call C<< Template::Declare->show() >>,
C<< show() >> exported from Template::Declare::Tags or
@@ -482,7 +482,7 @@
HTML-encodes its arguments and appends them to C<Template::Declare>'s output
buffer. This is similar to simply returning a string from a tag function call,
-but is occaisionally useful when you need to output a mix of things, as in:
+but is occasionally useful when you need to output a mix of things, as in:
p { outs 'hello'; em { 'world' } }
@@ -592,7 +592,7 @@
attribute arguments specified via C<with>. It passes those arguments in to the
wrapped code in C<@_>. It also takes care of putting the output in the right
place and tidying up after itself. This might be useful to change the behavior
-of a template based on attributs passed to C<with>.
+of a template based on attributes passed to C<with>.
=cut
@@ -1007,7 +1007,7 @@
=head1 COPYRIGHT
-Copyright 2006-2009 Best Practical Solutions, LLC
+Copyright 2006-2009 Best Practical Solutions, LLC.
=cut
Added: Template-Declare/branches/mixmaster/t/pod-spelling.t
==============================================================================
--- (empty file)
+++ Template-Declare/branches/mixmaster/t/pod-spelling.t Thu Oct 15 14:59:27 2009
@@ -0,0 +1,41 @@
+#!/usr/bin/env perl -w
+
+use strict;
+use Test::More;
+eval "use Test::Spelling";
+plan skip_all => "Test::Spelling required for testing POD spelling" if $@;
+
+add_stopwords(<DATA>);
+all_pod_files_spelling_ok();
+
+__DATA__
+API
+CMS
+Mixin
+Mixins
+PHP
+Postprocessing
+RDF
+XUL
+inline
+invocant
+mixin
+mixins
+mixin's
+namespace
+postprocessor
+Zhang
+namespaces
+postprocessing
+ATTR
+OO
+TAGNAME
+TAGSET
+TEMPLATENAME
+WRAPPERNAME
+LLC
+attr
+PARAMS
+XHTML
+Mozilla's
+rdf
More information about the Jifty-commit
mailing list