Author: cbrisson
Date: Wed Jul 13 10:37:27 2016
New Revision: 1752389
URL: http://svn.apache.org/viewvc?rev=1752389&view=rev
Log:
[site] fixes EventHandler section layout, and blockquote margins
Modified:
velocity/site/cms/trunk/content/css/site.css
velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext
velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext
Modified: velocity/site/cms/trunk/content/css/site.css
URL:
http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/css/site.css?rev=1752389&r1=1752388&r2=1752389&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/css/site.css (original)
+++ velocity/site/cms/trunk/content/css/site.css Wed Jul 13 10:37:27 2016
@@ -90,6 +90,12 @@ section, div.section
margin: 1em 0;
}
+blockquote
+{
+ margin-left: 1em;
+ margin-right: 1em;
+}
+
body
{
/* font-family: "Droid Serif",Georgia,"Times New Roman",Times,serif; */
Modified: velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext
URL:
http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext?rev=1752389&r1=1752388&r2=1752389&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/1.7/developer-guide.mdtext Wed Jul
13 10:37:27 2016
@@ -519,7 +519,7 @@ Velocity contains a fine-grained event h
All event handler interfaces available in Velocity are in the package
`org.apache.velocity.app.event`. You may create your own implementation or use
one of the sample implementations in the package
`org.apache.velocity.app.event.implement`. (See the javadocs for more details
on the provided implementations).
-*`org.apache.velocity.app.event.IncludeEventHandler`*
+### `org.apache.velocity.app.event.IncludeEventHandler`
> The `IncludeEventHandler` can be used to modify the template that is
> included in a page with `#include` or `#parse`. For example, this may be
> used to make all includes relative to the current directory or to prevent
> access to unauthorized resources. Multiple `IncludeEventHandler`'s may be
> chained, with the return value of the final call used as the name of the
> template to retrieve.
>
@@ -531,10 +531,11 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.IncludeNotFound`
> + `org.apache.velocity.app.event.implement.IncludeRelativePath`
-*`org.apache.velocity.app.event.InvalidReferenceEventHandler`*
+### `org.apache.velocity.app.event.InvalidReferenceEventHandler`
> Normally, when a template contains a bad reference an error message is
> logged and (unless it is part of a `#set` or `#if`), the reference is
> included verbatim in a page. With the `InvalidReferenceEventHandler` this
> behavior can be changed. Substitute values can be inserted, invalid
> references may be logged, or an exception can be thrown. Multiple
> `InvalidReferenceEventHandler`'s may be chained. The exact manner in which
> chained method calls behave will differ per method. (See the javadoc for
> the details).
>
@@ -559,9 +560,10 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.ReportInvalidReferences`
-*`org.apache.velocity.app.event.MethodExceptionEventHandler`*
+### `org.apache.velocity.app.event.MethodExceptionEventHandler`
> When a user-supplied method throws an exception, the
> `MethodExceptionEventHandler` is invoked with the Class, method name and
> thrown Exception. The handler can either return a valid Object to be used
> as the return value of the method call or throw the passed-in or new
> Exception, which will be wrapped and propogated to the user as a
> `MethodInvocationException`. While `MethodExceptionEventHandler`'s can be
> chained only the first handler is actually called -- all others are ignored.
>
@@ -574,10 +576,11 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.PrintExceptions`
-*`org.apache.velocity.app.event.NullSetEventHandler`*
+### `org.apache.velocity.app.event.NullSetEventHandler`
> When a #set() rejects an assignment due to the right hand side being an
> invalid or null reference, this is normally logged. The
> `NullSetEventHandler` allows you to 'veto' the logging of this condition.
> Multiple `NullSetEventHandler`'s can be chained; each event handler is
> called in sequence until a false is returned.
>
@@ -588,9 +591,10 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + *none provided*
-*`org.apache.velocity.app.event.ReferenceInsertionEventHandler`*
+### `org.apache.velocity.app.event.ReferenceInsertionEventHandler`
> A `ReferenceInsertionEventHandler` allows the developer to intercept each
> write of a reference ($foo) value to the output stream and modify that
> output. Multiple `ReferenceInsertionEventHandler`'s may be chained with
> each step potentially altering the inserted reference.
>
@@ -601,6 +605,7 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.EscapeHtmlReference`
> + `org.apache.velocity.app.event.implement.EscapeJavascriptReference`
> + `org.apache.velocity.app.event.implement.EscapeSqlReference`
Modified: velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext
URL:
http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext?rev=1752389&r1=1752388&r2=1752389&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext
(original)
+++ velocity/site/cms/trunk/content/engine/devel/developer-guide.mdtext Wed Jul
13 10:37:27 2016
@@ -526,7 +526,7 @@ Velocity contains a fine-grained event h
All event handler interfaces available in Velocity are in the package
`org.apache.velocity.app.event`. You may create your own implementation or use
one of the sample implementations in the package
`org.apache.velocity.app.event.implement`. (See the javadocs for more details
on the provided implementations).
-*`org.apache.velocity.app.event.IncludeEventHandler`*
+### `org.apache.velocity.app.event.IncludeEventHandler`
> The `IncludeEventHandler` can be used to modify the template that is
> included in a page with `#include` or `#parse`. For example, this may be
> used to make all includes relative to the current directory or to prevent
> access to unauthorized resources. Multiple `IncludeEventHandler`'s may be
> chained, with the return value of the final call used as the name of the
> template to retrieve.
>
@@ -538,10 +538,11 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.IncludeNotFound`
> + `org.apache.velocity.app.event.implement.IncludeRelativePath`
-*`org.apache.velocity.app.event.InvalidReferenceEventHandler`*
+### `org.apache.velocity.app.event.InvalidReferenceEventHandler`
> Normally, when a template contains a bad reference an error message is
> logged and (unless it is part of a `#set` or `#if`), the reference is
> included verbatim in a page. With the `InvalidReferenceEventHandler` this
> behavior can be changed. Substitute values can be inserted, invalid
> references may be logged, or an exception can be thrown. Multiple
> `InvalidReferenceEventHandler`'s may be chained. The exact manner in which
> chained method calls behave will differ per method. (See the javadoc for
> the details).
>
@@ -566,9 +567,10 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.ReportInvalidReferences`
-*`org.apache.velocity.app.event.MethodExceptionEventHandler`*
+### `org.apache.velocity.app.event.MethodExceptionEventHandler`
> When a user-supplied method throws an exception, the
> `MethodExceptionEventHandler` is invoked with the Class, method name and
> thrown Exception. The handler can either return a valid Object to be used
> as the return value of the method call or throw the passed-in or new
> Exception, which will be wrapped and propogated to the user as a
> `MethodInvocationException`. While `MethodExceptionEventHandler`'s can be
> chained only the first handler is actually called -- all others are ignored.
>
@@ -581,10 +583,11 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.PrintExceptions`
-*`org.apache.velocity.app.event.NullSetEventHandler`*
+### `org.apache.velocity.app.event.NullSetEventHandler`
> When a #set() rejects an assignment due to the right hand side being an
> invalid or null reference, this is normally logged. The
> `NullSetEventHandler` allows you to 'veto' the logging of this condition.
> Multiple `NullSetEventHandler`'s can be chained; each event handler is
> called in sequence until a false is returned.
>
@@ -595,9 +598,10 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + *none provided*
-*`org.apache.velocity.app.event.ReferenceInsertionEventHandler`*
+### `org.apache.velocity.app.event.ReferenceInsertionEventHandler`
> A `ReferenceInsertionEventHandler` allows the developer to intercept each
> write of a reference ($foo) value to the output stream and modify that
> output. Multiple `ReferenceInsertionEventHandler`'s may be chained with
> each step potentially altering the inserted reference.
>
@@ -608,6 +612,7 @@ All event handler interfaces available i
> }
>
> Available implementations include:
+>
> + `org.apache.velocity.app.event.implement.EscapeHtmlReference`
> + `org.apache.velocity.app.event.implement.EscapeJavascriptReference`
> + `org.apache.velocity.app.event.implement.EscapeSqlReference`
