You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by ad...@apache.org on 2015/12/04 23:49:44 UTC
[19/19] wicket-site git commit: WICKET-6049 updated links to example
site
WICKET-6049 updated links to example site
Project: http://git-wip-us.apache.org/repos/asf/wicket-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/wicket-site/commit/f39616cb
Tree: http://git-wip-us.apache.org/repos/asf/wicket-site/tree/f39616cb
Diff: http://git-wip-us.apache.org/repos/asf/wicket-site/diff/f39616cb
Branch: refs/heads/asf-site
Commit: f39616cbdeecb4cc9e0559cb97f08d22b9bf8145
Parents: 08722d8
Author: bitstorm <an...@gmail.com>
Authored: Fri Dec 4 23:33:58 2015 +0100
Committer: bitstorm <an...@gmail.com>
Committed: Fri Dec 4 23:33:58 2015 +0100
----------------------------------------------------------------------
content/atom.xml | 55 +--
content/contribute/build.html | 6 +-
content/contribute/ides.html | 4 +-
content/contribute/release.html | 10 +-
content/contribute/write.html | 14 +-
content/index.html | 12 +-
content/learn/examples/ajaxcounter.html | 20 +-
content/learn/examples/dropdownchoice.html | 28 +-
content/learn/examples/guestbook.html | 44 +--
content/learn/examples/helloworld.html | 20 +-
content/learn/examples/index.html | 4 +-
content/learn/examples/markupinheritance.html | 52 +--
content/learn/examples/navomatic.html | 26 +-
content/learn/examples/usingfragments.html | 22 +-
content/learn/index.html | 6 +-
.../news/2009/07/30/wicket-1-3-7-released.html | 155 ---------
...-1-4-takes-typesafety-to-the-next-level.html | 157 ---------
.../news/2009/07/30/wicket-1.3.7-released.html | 155 +++++++++
...-1.4-takes-typesafety-to-the-next-level.html | 157 +++++++++
content/news/2009/07/index.html | 4 +-
.../news/2009/08/21/wicket-1-4-1-released.html | 90 -----
.../news/2009/08/21/wicket-1.4.1-released.html | 90 +++++
content/news/2009/08/index.html | 2 +-
.../news/2009/10/12/wicket-1-4-2-released.html | 84 -----
.../news/2009/10/12/wicket-1.4.2-released.html | 84 +++++
.../news/2009/10/24/wicket-1-4-3-released.html | 83 -----
.../news/2009/10/24/wicket-1.4.3-released.html | 83 +++++
content/news/2009/10/index.html | 4 +-
.../news/2009/12/13/wicket-1-4-4-released.html | 84 -----
.../news/2009/12/13/wicket-1.4.4-released.html | 84 +++++
.../news/2009/12/21/wicket-1-4-5-released.html | 86 -----
.../news/2009/12/21/wicket-1.4.5-released.html | 86 +++++
content/news/2009/12/index.html | 4 +-
content/news/2009/index.html | 28 +-
.../news/2010/02/01/wicket-1-4-6-released.html | 84 -----
.../news/2010/02/01/wicket-1.4.6-released.html | 84 +++++
content/news/2010/02/index.html | 2 +-
.../news/2010/03/05/wicket-1-4-7-released.html | 82 -----
.../news/2010/03/05/wicket-1.4.7-released.html | 82 +++++
content/news/2010/03/index.html | 2 +-
.../news/2010/05/03/wicket-1-4-8-released.html | 85 -----
.../news/2010/05/03/wicket-1.4.8-released.html | 85 +++++
.../news/2010/05/24/wicket-1-4-9-released.html | 124 -------
.../news/2010/05/24/wicket-1.4.9-released.html | 124 +++++++
content/news/2010/05/index.html | 4 +-
.../news/2010/08/11/wicket-1-4-10-released.html | 179 ----------
.../news/2010/08/11/wicket-1-5-m1-released.html | 86 -----
.../news/2010/08/11/wicket-1.4.10-released.html | 179 ++++++++++
.../news/2010/08/11/wicket-1.5-M1-released.html | 86 +++++
content/news/2010/08/index.html | 4 +-
.../news/2010/09/09/wicket-1-4-11-released.html | 84 -----
.../news/2010/09/09/wicket-1.4.11-released.html | 84 +++++
.../news/2010/09/17/wicket-1-4-12-released.html | 83 -----
.../2010/09/17/wicket-1-5-m2-1-released.html | 87 -----
.../news/2010/09/17/wicket.1.4.12-released.html | 83 +++++
.../2010/09/17/wicket.1.5-M2.1-released.html | 87 +++++
content/news/2010/09/index.html | 6 +-
.../news/2010/11/01/wicket-1-4-13-released.html | 83 -----
.../news/2010/11/01/wicket-1.4.13-released.html | 83 +++++
.../news/2010/11/05/wicket-1-5-m3-released.html | 83 -----
.../news/2010/11/05/wicket-1.5-M3-released.html | 83 +++++
.../news/2010/11/29/wicket-1-4-14-released.html | 83 -----
.../news/2010/11/29/wicket-1.4.14-released.html | 83 +++++
content/news/2010/11/index.html | 6 +-
.../news/2010/12/24/wicket-1-4-15-released.html | 83 -----
.../news/2010/12/24/wicket-1.4.15-released.html | 83 +++++
content/news/2010/12/index.html | 2 +-
content/news/2010/index.html | 52 +--
.../2011/01/22/wicket-1-5-rc1-released.html | 88 -----
.../2011/01/22/wicket-1.5-RC1-released.html | 88 +++++
content/news/2011/01/index.html | 2 +-
.../news/2011/02/25/wicket-1-4-16-released.html | 83 -----
.../2011/02/25/wicket-1-5-rc2-released.html | 83 -----
.../news/2011/02/25/wicket-1.4.16-released.html | 83 +++++
.../2011/02/25/wicket-1.5-rc2-released.html | 83 +++++
content/news/2011/02/index.html | 4 +-
.../news/2011/04/02/wicket-1-4-17-released.html | 83 -----
.../2011/04/02/wicket-1-5-rc3-released.html | 83 -----
.../news/2011/04/02/wicket-1.4.17-released.html | 83 +++++
.../2011/04/02/wicket-1.5-RC3-released.html | 83 +++++
content/news/2011/04/index.html | 4 +-
.../2011/05/11/wicket-1-5-rc4-2-released.html | 83 -----
.../2011/05/11/wicket-1.5-RC4.2-released.html | 83 +++++
content/news/2011/05/index.html | 2 +-
.../2011/06/25/wicket-1-5-rc5-1-released.html | 83 -----
.../2011/06/25/wicket-1.5-RC5.1-released.html | 83 +++++
content/news/2011/06/index.html | 2 +-
.../news/2011/08/09/wicket-1-4-18-released.html | 83 -----
.../news/2011/08/09/wicket-1.4.18-released.html | 83 +++++
content/news/2011/08/28/1-5-rc7-released.html | 84 -----
content/news/2011/08/28/1.5-RC7-released.html | 84 +++++
content/news/2011/08/index.html | 4 +-
.../news/2011/09/07/wicket-1-5-released.html | 147 --------
.../news/2011/09/07/wicket-1.5-released.html | 147 ++++++++
.../news/2011/09/29/wicket-1-5-1-released.html | 83 -----
.../news/2011/09/29/wicket-1.5.1-released.html | 83 +++++
content/news/2011/09/index.html | 4 +-
.../news/2011/10/17/wicket-1-4-19-released.html | 83 -----
.../news/2011/10/17/wicket-1.4.19-released.html | 83 +++++
.../news/2011/10/24/wicket-1-5-2-released.html | 83 -----
.../news/2011/10/24/wicket-1.5.2-released.html | 83 +++++
content/news/2011/10/index.html | 4 +-
.../news/2011/11/14/wicket-1-5-3-released.html | 83 -----
.../news/2011/11/14/wicket-1.5.3-released.html | 83 +++++
content/news/2011/11/index.html | 2 +-
content/news/2011/index.html | 56 +--
.../news/2012/01/23/wicket-1-5-4-released.html | 83 -----
.../news/2012/01/23/wicket-1.5.4-released.html | 83 +++++
content/news/2012/01/index.html | 2 +-
.../news/2012/03/12/wicket-1-4-20-released.html | 83 -----
.../news/2012/03/12/wicket-1-5-5-released.html | 83 -----
.../news/2012/03/12/wicket-1.4.20-released.html | 83 +++++
.../news/2012/03/12/wicket-1.5.5-released.html | 83 +++++
.../2012/03/26/wicket-6-0-0-beta1-released.html | 85 -----
.../2012/03/26/wicket-6.0.0-beta1-released.html | 85 +++++
content/news/2012/03/index.html | 6 +-
.../news/2012/05/07/wicket-1-5-6-released.html | 83 -----
.../news/2012/05/07/wicket-1.5.6-released.html | 83 +++++
.../2012/05/29/wicket-6-0-0-beta2-released.html | 106 ------
.../2012/05/29/wicket-6.0.0-beta2-released.html | 106 ++++++
content/news/2012/05/index.html | 4 +-
.../news/2012/06/04/wicket-1-5-7-released.html | 83 -----
.../news/2012/06/04/wicket-1.5.7-released.html | 83 +++++
content/news/2012/06/index.html | 2 +-
.../2012/07/16/wicket-6-0-0-beta3-released.html | 165 ---------
.../2012/07/16/wicket-6.0.0-beta3-released.html | 169 +++++++++
content/news/2012/07/index.html | 2 +-
.../news/2012/08/24/wicket-1-5-8-released.html | 83 -----
.../news/2012/08/24/wicket-1.5.8-released.html | 83 +++++
content/news/2012/08/index.html | 2 +-
.../news/2012/09/05/wicket-1-4-21-released.html | 85 -----
.../news/2012/09/05/wicket-1.4.21-released.html | 85 +++++
.../news/2012/09/05/wicket-6-0-0-released.html | 99 ------
.../news/2012/09/05/wicket-6.0.0-released.html | 99 ++++++
content/news/2012/09/index.html | 4 +-
.../news/2012/10/04/wicket-6-1-0-released.html | 153 ---------
.../news/2012/10/04/wicket-6.1.0-released.html | 153 +++++++++
.../news/2012/10/08/wicket-6-1-1-released.html | 102 ------
.../news/2012/10/08/wicket-6.1.1-released.html | 102 ++++++
.../news/2012/10/23/wicket-6-2-0-released.html | 151 --------
.../news/2012/10/23/wicket-6.2.0-released.html | 151 ++++++++
content/news/2012/10/index.html | 6 +-
.../news/2012/11/09/wicket-1-5-9-released.html | 83 -----
.../news/2012/11/09/wicket-1.5.9-released.html | 83 +++++
.../news/2012/11/16/wicket-6-3-0-released.html | 137 --------
.../news/2012/11/16/wicket-6.3.0-released.html | 137 ++++++++
content/news/2012/11/index.html | 4 +-
.../news/2012/12/14/wicket-6-4-0-released.html | 178 ----------
.../news/2012/12/14/wicket-6.4.0-released.html | 179 ++++++++++
content/news/2012/12/index.html | 2 +-
content/news/2012/index.html | 68 ++--
.../news/2013/01/23/wicket-6-5-0-released.html | 153 ---------
.../news/2013/01/23/wicket-6.5.0-released.html | 157 +++++++++
content/news/2013/01/index.html | 2 +-
.../news/2013/02/15/wicket-6-6-0-released.html | 155 ---------
.../news/2013/02/15/wicket-6.6.0-released.html | 155 +++++++++
.../news/2013/02/26/wicket-1-5-10-released.html | 83 -----
.../news/2013/02/26/wicket-1.5.10-released.html | 83 +++++
content/news/2013/02/index.html | 4 +-
.../news/2013/04/12/wicket-6-7-0-released.html | 204 -----------
.../news/2013/04/12/wicket-6.7.0-released.html | 204 +++++++++++
content/news/2013/04/index.html | 2 +-
.../news/2013/05/17/wicket-6-8-0-released.html | 140 --------
.../news/2013/05/17/wicket-6.8.0-released.html | 140 ++++++++
content/news/2013/05/index.html | 2 +-
.../news/2013/06/27/wicket-6-9-0-released.html | 144 --------
.../news/2013/06/27/wicket-6.9.0-released.html | 144 ++++++++
content/news/2013/06/index.html | 2 +-
.../news/2013/07/10/wicket-6-9-1-released.html | 134 --------
.../news/2013/07/10/wicket-6.9.1-released.html | 134 ++++++++
content/news/2013/07/index.html | 2 +-
.../news/2013/08/18/wicket-6-10-0-released.html | 192 -----------
.../news/2013/08/18/wicket-6.10.0-released.html | 192 +++++++++++
content/news/2013/08/index.html | 2 +-
.../news/2013/09/20/wicket-6-11-0-released.html | 186 ----------
.../news/2013/09/20/wicket-6.11.0-released.html | 186 ++++++++++
content/news/2013/09/index.html | 2 +-
.../news/2013/11/01/wicket-6-12-0-released.html | 181 ----------
.../news/2013/11/01/wicket-6.12.0-released.html | 181 ++++++++++
content/news/2013/11/index.html | 2 +-
content/news/2013/index.html | 40 +--
.../news/2014/01/05/wicket-6-13-0-released.html | 257 --------------
.../news/2014/01/05/wicket-6.13.0-released.html | 257 ++++++++++++++
content/news/2014/01/index.html | 2 +-
.../news/2014/02/06/wicket-1-4-23-released.html | 83 -----
.../news/2014/02/06/wicket-1-5-11-released.html | 83 -----
.../news/2014/02/06/wicket-1.4.23-released.html | 83 +++++
.../news/2014/02/06/wicket-1.5.11-released.html | 83 +++++
.../news/2014/02/20/wicket-6-14-0-released.html | 149 --------
.../news/2014/02/20/wicket-6.14.0-released.html | 153 +++++++++
content/news/2014/02/index.html | 6 +-
.../news/2014/04/23/wicket-6-15-0-released.html | 157 ---------
.../news/2014/04/23/wicket-6.15.0-released.html | 163 +++++++++
.../2014/04/30/wicket-7-0-0-m1-released.html | 112 ------
.../2014/04/30/wicket-7.0.0-M1-released.html | 112 ++++++
content/news/2014/04/index.html | 4 +-
.../2014/06/20/wicket-7-0-0-m2-released.html | 112 ------
.../2014/06/20/wicket-7.0.0-M2-released.html | 112 ++++++
.../news/2014/06/21/wicket-6-16-0-released.html | 139 --------
.../news/2014/06/21/wicket-6.16.0-released.html | 142 ++++++++
content/news/2014/06/index.html | 4 +-
.../2014/08/23/wicket-7-0-0-m3-released.html | 112 ------
.../2014/08/23/wicket-7.0.0-M3-released.html | 112 ++++++
.../news/2014/08/24/wicket-6-17-0-released.html | 173 ----------
.../news/2014/08/24/wicket-6.17.0-released.html | 177 ++++++++++
content/news/2014/08/index.html | 4 +-
.../news/2014/09/15/wicket-1-5-12-released.html | 83 -----
.../news/2014/09/15/wicket-1.5.12-released.html | 83 +++++
content/news/2014/09/index.html | 2 +-
.../news/2014/11/05/wicket-6-18-0-released.html | 161 ---------
.../news/2014/11/05/wicket-6.18.0-released.html | 161 +++++++++
.../2014/11/05/wicket-7-0-0-m4-released.html | 196 -----------
.../2014/11/05/wicket-7.0.0-M4-released.html | 196 +++++++++++
content/news/2014/11/index.html | 4 +-
content/news/2014/index.html | 52 +--
.../news/2015/02/02/wicket-6-19-0-released.html | 167 ---------
.../news/2015/02/02/wicket-6.19.0-released.html | 167 +++++++++
.../2015/02/02/wicket-7-0-0-m5-released.html | 202 -----------
.../2015/02/02/wicket-7.0.0-M5-released.html | 202 +++++++++++
.../02/13/new-committer-Sebastien-Briquet.html | 76 +++++
.../02/13/new-committer-sebastien-briquet.html | 76 -----
.../news/2015/02/13/wicket-1-5-13-released.html | 83 -----
.../news/2015/02/13/wicket-1.5.13-released.html | 83 +++++
content/news/2015/02/index.html | 8 +-
.../news/2015/06/14/wicket-6-20-0-released.html | 164 ---------
.../news/2015/06/14/wicket-6.20.0-released.html | 164 +++++++++
.../2015/06/21/wicket-7-0-0-m6-released.html | 239 -------------
.../2015/06/21/wicket-7.0.0-M6-released.html | 244 +++++++++++++
content/news/2015/06/index.html | 4 +-
.../news/2015/07/28/wicket-7-0-released.html | 91 -----
.../news/2015/07/28/wicket-7.0-released.html | 91 +++++
content/news/2015/07/index.html | 2 +-
.../news/2015/10/24/wicket-1-5-14-released.html | 92 -----
.../news/2015/10/24/wicket-1.5.14-released.html | 95 ++++++
.../news/2015/10/25/wicket-7-1-0-released.html | 170 ----------
.../news/2015/10/25/wicket-7.1.0-released.html | 173 ++++++++++
content/news/2015/10/index.html | 12 +-
content/news/2015/11/15/wicket-1-4-x-eol.html | 78 -----
content/news/2015/11/15/wicket-1.4.x-eol.html | 78 +++++
.../news/2015/11/16/wicket-6-21-0-released.html | 139 --------
.../news/2015/11/16/wicket-6.21.0-released.html | 139 ++++++++
content/news/2015/11/index.html | 4 +-
content/news/2015/index.html | 44 +--
content/news/index.html | 340 +++++++++----------
content/start/quickstart.html | 5 +-
content/start/wicket-1.3.x.html | 2 +-
content/start/wicket-1.4.x.html | 2 +-
content/start/wicket-1.5.x.html | 2 +-
content/start/wicket-6.x.html | 2 +-
content/start/wicket-7.x.html | 2 +-
content/start/wicket-8.x.html | 2 +-
learn/examples/index.md | 4 +-
252 files changed, 10574 insertions(+), 10523 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/atom.xml
----------------------------------------------------------------------
diff --git a/content/atom.xml b/content/atom.xml
index b1eaa12..47ad226 100644
--- a/content/atom.xml
+++ b/content/atom.xml
@@ -3,7 +3,7 @@
<title>Apache Wicket</title>
<link href="http://wicket.apache.org/atom.xml" rel="self"/>
<link href="http://wicket.apache.org/"/>
- <updated>2015-11-20T16:08:09+01:00</updated>
+ <updated>2015-12-04T23:32:06+01:00</updated>
<id>http://wicket.apache.org/</id>
<author>
<name>Apache Wicket</name>
@@ -13,7 +13,7 @@
<entry>
<title>Apache Wicket 6.21.0 released</title>
- <link href="http://wicket.apache.org/news/2015/11/16/wicket-6-21-0-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/11/16/wicket-6.21.0-released.html"/>
<updated>2015-11-16T00:00:00+01:00</updated>
<id>http://wicket.apache.org/news/2015/11/16/wicket-6.21.0-released</id>
<content type="html"><p>The Apache Wicket PMC is proud to announce Apache Wicket 6.21.0!</p>
@@ -111,7 +111,7 @@ migration guide found at</p>
<entry>
<title>Apache Wicket 1.4.x end of life</title>
- <link href="http://wicket.apache.org/news/2015/11/15/wicket-1-4-x-eol.html"/>
+ <link href="http://wicket.apache.org/news/2015/11/15/wicket-1.4.x-eol.html"/>
<updated>2015-11-15T00:00:00+01:00</updated>
<id>http://wicket.apache.org/news/2015/11/15/wicket-1.4.x-eol</id>
<content type="html"><p>The Apache Wicket team announces that support for Apache Wicket 1.4.x ends on 16 November 2015.
@@ -130,7 +130,7 @@ On the same day Wicket 1.5.x enters “security fixes” maintenance mode.</p
<entry>
<title>Apache Wicket 7.1.0 released</title>
- <link href="http://wicket.apache.org/news/2015/10/25/wicket-7-1-0-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/10/25/wicket-7.1.0-released.html"/>
<updated>2015-10-25T00:00:00+02:00</updated>
<id>http://wicket.apache.org/news/2015/10/25/wicket-7.1.0-released</id>
<content type="html"><p>The Apache Wicket PMC is proud to announce Apache Wicket 7.1.0!</p>
@@ -219,7 +219,7 @@ iEYEABECAAYFAlYldl4ACgkQJBX8W/xy/UXNzgCgtL4H8bRjZewltF1BX7H3F+Ph
<h4 id="bug">Bug</h4>
-<pre><code>* [WICKET-5882] - AutoComplete suggestion list disappear when I click on autoComplete scrollbar in IE
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5882] - AutoComplete suggestion list disappear when I click on autoComplete scrollbar in IE
* [WICKET-5941] - Headers not rendered for components inside TransparentWebMarkupContainer on ajax update
* [WICKET-5959] - HTML input placeholder text breaks AutoCompleteTextField in IE11
* [WICKET-5960] - Page header isn't rendered for pages where URL has changed during render
@@ -245,21 +245,24 @@ iEYEABECAAYFAlYldl4ACgkQJBX8W/xy/UXNzgCgtL4H8bRjZewltF1BX7H3F+Ph
* [WICKET-5999] - AjaxFormValidatingBehavior not updates initially hidden feedback component
* [WICKET-6005] - WicketRuntimeException from AjaxPagingNavigator#onAjaxEvent
</code></pre>
+</div>
<h4 id="improvement">Improvement</h4>
-<pre><code>* [WICKET-5948] - wicket-ajax.js probably doesn't traverse the children of &lt;div&gt; or &lt;span&gt;
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5948] - wicket-ajax.js probably doesn't traverse the children of &lt;div&gt; or &lt;span&gt;
* [WICKET-5971] - Code cleanup in ServletWebResponse
* [WICKET-5974] - Change AjaxPagingNavigator#onAjaxEvent() to only consider parent components that have setOutputMarkupId(true)
* [WICKET-5976] - Improve the documentation of FeedbackMessages first(int level)
* [WICKET-5984] - ReplaceHandlerException lacks an accessor for the replacement RequestHandler
* [WICKET-5986] - NumberTextField&lt;N&gt; should use Models for minimum, maximum and step
</code></pre>
+</div>
<h4 id="task">Task</h4>
-<pre><code>* [WICKET-5951] - Upgrade Atmosphere to 2.2.8
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5951] - Upgrade Atmosphere to 2.2.8
</code></pre>
+</div>
<p>Have fun!</p>
@@ -269,26 +272,29 @@ iEYEABECAAYFAlYldl4ACgkQJBX8W/xy/UXNzgCgtL4H8bRjZewltF1BX7H3F+Ph
<entry>
<title>Wicket 1.5.14 released</title>
- <link href="http://wicket.apache.org/news/2015/10/24/wicket-1-5-14-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/10/24/wicket-1.5.14-released.html"/>
<updated>2015-10-24T00:00:00+02:00</updated>
<id>http://wicket.apache.org/news/2015/10/24/wicket-1.5.14-released</id>
<content type="html"><p>This is the fourteenth maintenance release of the Wicket 1.5.x series. This release brings over 4 bug fixes and 1 improvement.</p>
-<pre><code>CHANGELOG for 1.5.14:
+<div class="highlighter-rouge"><pre class="highlight"><code>CHANGELOG for 1.5.14:
</code></pre>
+</div>
<p>** Bug</p>
-<pre><code>* [WICKET-5838] - Last-modified header of external markup is ignored
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5838] - Last-modified header of external markup is ignored
* [WICKET-5927] - Velocity remote code execution
* [WICKET-6000] - Wicket 1.5 DTD link on website does not point to valid location
* [WICKET-6005] - WicketRuntimeException from AjaxPagingNavigator#onAjaxEvent
</code></pre>
+</div>
<p>** Improvement</p>
-<pre><code>* [WICKET-5974] - Change AjaxPagingNavigator#onAjaxEvent() to only consider parent components that have setOutputMarkupId(true)
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5974] - Change AjaxPagingNavigator#onAjaxEvent() to only consider parent components that have setOutputMarkupId(true)
</code></pre>
+</div>
<ul>
<li>To use in Maven:</li>
@@ -308,7 +314,7 @@ iEYEABECAAYFAlYldl4ACgkQJBX8W/xy/UXNzgCgtL4H8bRjZewltF1BX7H3F+Ph
<entry>
<title>Apache Wicket v7.0 released</title>
- <link href="http://wicket.apache.org/news/2015/07/28/wicket-7-0-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/07/28/wicket-7.0-released.html"/>
<updated>2015-07-28T00:00:00+02:00</updated>
<id>http://wicket.apache.org/news/2015/07/28/wicket-7.0-released</id>
<content type="html"><p>The Apache Software Foundation announces Apache Wicket™ v7.0 Open Source Java web framework that powers thousands of web applications and web sites for governments, stores, universities, cities, banks, email providers, and more.</p>
@@ -348,7 +354,7 @@ All other brands and trademarks are the property of their respective owners.<
<entry>
<title>Apache Wicket 7.0.0-M6 released</title>
- <link href="http://wicket.apache.org/news/2015/06/21/wicket-7-0-0-m6-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/06/21/wicket-7.0.0-M6-released.html"/>
<updated>2015-06-21T00:00:00+02:00</updated>
<id>http://wicket.apache.org/news/2015/06/21/wicket-7.0.0-M6-released</id>
<content type="html"><p>The Apache Wicket PMC is proud to announce Apache Wicket 7.0.0-M6!</p>
@@ -469,7 +475,7 @@ yPIAoMU7z9Go0pn5ZFKZwq+VDA0cvoh4
<h4 id="bugs">Bugs</h4>
-<pre><code>* [WICKET-5790] - VariableInterpolator &amp; #getThrowExceptionOnMissingResource
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5790] - VariableInterpolator &amp; #getThrowExceptionOnMissingResource
* [WICKET-5814] - CryptoMapper clears feedback messages
* [WICKET-5816] - Apps can't use Application.setName instead of WicketFilter for e.g. JMX names
* [WICKET-5822] - AjaxSelfUpdatingTimer stops working after ajax download
@@ -515,10 +521,11 @@ yPIAoMU7z9Go0pn5ZFKZwq+VDA0cvoh4
* [WICKET-5916] - StackOverflowError when calling getObject() from load() in LDM
* [WICKET-5917] - Do not use jQuery's $ in String snippets in Java code
</code></pre>
+</div>
<h4 id="improvement">Improvement</h4>
-<pre><code>* [WICKET-5314] - AbstractAutoCompleteBehavior does not support AjaxChannels
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5314] - AbstractAutoCompleteBehavior does not support AjaxChannels
* [WICKET-5749] - Wicket-auth-roles should deal with resource authorization
* [WICKET-5789] - Make org.apache.wicket.protocol.ws.javax.WicketServerEndpointConfig publicly visible
* [WICKET-5801] - Responsive Images
@@ -541,25 +548,29 @@ yPIAoMU7z9Go0pn5ZFKZwq+VDA0cvoh4
* [WICKET-5905] - allow listening to Ajax calls before scheduling
* [WICKET-5921] - Provide a default implementation of IModelComparator that always returns false
</code></pre>
+</div>
<h4 id="new-feature">New Feature</h4>
-<pre><code>* [WICKET-5819] - Support for HTML 5 media tags (audio / video)
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5819] - Support for HTML 5 media tags (audio / video)
* [WICKET-5827] - Allow to apply multiple Javascript / CSS compressors
* [WICKET-5897] - Use the #isEnabled() method with validators
* [WICKET-5918] - Create an Image component that uses the new data: protocol (an InlineImage)
* [WICKET-5919] - Add support for CSRF prevention
</code></pre>
+</div>
<h4 id="task">Task</h4>
-<pre><code>* [WICKET-5896] - Upgrade jQuery to latest stable versions (1.11.4 &amp; 2.1.3)
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5896] - Upgrade jQuery to latest stable versions (1.11.4 &amp; 2.1.3)
</code></pre>
+</div>
<h4 id="wish">Wish</h4>
-<pre><code>* [WICKET-5848] - Remove .settings folders of projects
+<div class="highlighter-rouge"><pre class="highlight"><code>* [WICKET-5848] - Remove .settings folders of projects
</code></pre>
+</div>
<p>Have fun!</p>
@@ -569,7 +580,7 @@ yPIAoMU7z9Go0pn5ZFKZwq+VDA0cvoh4
<entry>
<title>Apache Wicket 6.20.0 released</title>
- <link href="http://wicket.apache.org/news/2015/06/14/wicket-6-20-0-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/06/14/wicket-6.20.0-released.html"/>
<updated>2015-06-14T00:00:00+02:00</updated>
<id>http://wicket.apache.org/news/2015/06/14/wicket-6.20.0-released</id>
<content type="html"><p>The Apache Wicket PMC is proud to announce Apache Wicket 6.20.0!</p>
@@ -696,7 +707,7 @@ migration guide found at</p>
<entry>
<title>Wicket 1.5.13 released</title>
- <link href="http://wicket.apache.org/news/2015/02/13/wicket-1-5-13-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/02/13/wicket-1.5.13-released.html"/>
<updated>2015-02-13T00:00:00+01:00</updated>
<id>http://wicket.apache.org/news/2015/02/13/wicket-1.5.13-released</id>
<content type="html"><p>This is the thirteenth maintenance release of the Wicket 1.5.x series. This release brings over 1 bug fix and 1 improvement.</p>
@@ -721,7 +732,7 @@ migration guide found at</p>
<entry>
<title>New committer - Sebastien Briquet</title>
- <link href="http://wicket.apache.org/news/2015/02/13/new-committer-sebastien-briquet.html"/>
+ <link href="http://wicket.apache.org/news/2015/02/13/new-committer-Sebastien-Briquet.html"/>
<updated>2015-02-13T00:00:00+01:00</updated>
<id>http://wicket.apache.org/news/2015/02/13/new-committer-Sebastien-Briquet</id>
<content type="html"><p>The Project Management Committee (PMC) for Apache Wicket
@@ -740,7 +751,7 @@ to announce that he has accepted.</p>
<entry>
<title>Apache Wicket 7.0.0-M5 released</title>
- <link href="http://wicket.apache.org/news/2015/02/02/wicket-7-0-0-m5-released.html"/>
+ <link href="http://wicket.apache.org/news/2015/02/02/wicket-7.0.0-M5-released.html"/>
<updated>2015-02-02T00:00:00+01:00</updated>
<id>http://wicket.apache.org/news/2015/02/02/wicket-7.0.0-M5-released</id>
<content type="html"><p>The Apache Wicket PMC is proud to announce Apache Wicket 7.0.0-M5!</p>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/contribute/build.html
----------------------------------------------------------------------
diff --git a/content/contribute/build.html b/content/contribute/build.html
index ace2f8b..5cf49de 100644
--- a/content/contribute/build.html
+++ b/content/contribute/build.html
@@ -132,10 +132,10 @@ is then as simple as:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">mvn eclipse:eclipse</code></pre></figure>
<p>or opening the project using Netbeans or IDEAs Maven integration.</p>
<p>Maven will then add all the necessary JAR files to the project’s classpath.</p>
-<p>One thing you need to make sure is that you have set the <code>M2_REPO</code> classpath
+<p>One thing you need to make sure is that you have set the <code class="highlighter-rouge">M2_REPO</code> classpath
variable in Eclipse (or a similar construct in Netbeans), and point it to your
-local repository, typically found in <code>C:\Documents and Settings\username\.m2\repo</code>
-or (for unix buffs) <code>~/.m2/repo</code></p>
+local repository, typically found in <code class="highlighter-rouge">C:\Documents and Settings\username\.m2\repo</code>
+or (for unix buffs) <code class="highlighter-rouge">~/.m2/repo</code></p>
<p>You can add this setting using maven:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo</code></pre></figure>
</section>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/contribute/ides.html
----------------------------------------------------------------------
diff --git a/content/contribute/ides.html b/content/contribute/ides.html
index ba4ceff..66b5e2f 100644
--- a/content/contribute/ides.html
+++ b/content/contribute/ides.html
@@ -65,8 +65,8 @@ by their respective development teams.</p>
<p>Alternatively, you can generate an Eclipse project typing the following command on project’s root:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">mvn eclipse:eclipse</code></pre></figure>
<p>Maven will add all the necessary JAR files to the project’s classpath. Now the sources can be imported in Eclipse using the “Existing Projects into Workspace” wizard.</p>
-<p>If not already present the <code>M2_REPO</code> classpath variable has to point to your local Maven repository.
-The repository is typically found in <code>C:\Documents and Settings\<username>\.m2\repo</code> or (for unix buffs) <code>~/.m2/repo</code>. It can be set within Eclipse (Preferences->Java->Build Path->Classpath Variables) or with the help of Maven:</p>
+<p>If not already present the <code class="highlighter-rouge">M2_REPO</code> classpath variable has to point to your local Maven repository.
+The repository is typically found in <code class="highlighter-rouge">C:\Documents and Settings\<username>\.m2\repo</code> or (for unix buffs) <code class="highlighter-rouge">~/.m2/repo</code>. It can be set within Eclipse (Preferences->Java->Build Path->Classpath Variables) or with the help of Maven:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo</code></pre></figure>
<p>If you want to go along with the Wicket way of code formatting you should import the Wicket code format profile into your workspace (Preferences->Java->Code Style->Formatter), found in:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console"><path-to-eclipse-workspace>/wicket-core/EclipseCodeFormat.xml</code></pre></figure>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/contribute/release.html
----------------------------------------------------------------------
diff --git a/content/contribute/release.html b/content/contribute/release.html
index e5dbbf1..576fa68 100644
--- a/content/contribute/release.html
+++ b/content/contribute/release.html
@@ -132,7 +132,7 @@ gpg --print-md MD5 apache-wicket-$NEWVERSION.zip > apache-wicket-$NEWVERSION
<h4 id="staging-the-build">Staging the build</h4>
<figure class="highlight"><pre><code class="language-console" data-lang="console">ssh APACHE_ID@people.apache.org mkdir public_html/wicket-$NEWVERSION
scp apache-wicket-* APACHE_ID@people.apache.org:public_html/wicket-$NEWVERSION</code></pre></figure>
-<p><strong>TODO</strong> figure out how to let <code>release:perform</code> work from a local checkout, such that we can actually <em>stage</em> the build instead of having to push the tag to our git repo.</p>
+<p><strong>TODO</strong> figure out how to let <code class="highlighter-rouge">release:perform</code> work from a local checkout, such that we can actually <em>stage</em> the build instead of having to push the tag to our git repo.</p>
<p>The following steps are ONLY necessary as long as the above TODO has not been resolved.</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">git push origin build/wicket-$NEWVERSION:refs/heads/build/wicket-$NEWVERSION
git push -tags origin</code></pre></figure>
@@ -144,7 +144,7 @@ git push -tags origin</code></pre></figure>
<p>This will upload artifacts and signatures to Apache nexus in a staging repository.</p>
<h4 id="create-a-binary-release">Create a binary release</h4>
<p>As we don’t vote on binary packages, but do want to cater to developers not using Maven, it is very convenient to create a download for non-Maven users.</p>
-<p>The binary distribution should contain the same jar files that are uploaded to Maven Central. Unfortunately the Maven build creates duplicate jar files, but with different manifests (due to the inclusion of date/time of build), and the jar files have different signatures. Therefore it is necessary to create a distribution of the artifacts generated by the <code>mvn release:perform</code> command.</p>
+<p>The binary distribution should contain the same jar files that are uploaded to Maven Central. Unfortunately the Maven build creates duplicate jar files, but with different manifests (due to the inclusion of date/time of build), and the jar files have different signatures. Therefore it is necessary to create a distribution of the artifacts generated by the <code class="highlighter-rouge">mvn release:perform</code> command.</p>
<p>Perform the following commands in the root of your Wicket checkout to create the binary release files.</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console">mkdir apache-wicket-$NEWVERSION
cd apache-wicket-$NEWVERSION
@@ -182,7 +182,7 @@ git push -tags origin</code></pre></figure>
<li>Assuming there are none, and you are now in build mode, update the CHANGELOG-x.y file
(you can use JIRA for this list: go to “releases”, and under “unreleased”, next to your version, there’s a release notes link)</li>
</ul>
-<p>Make sure your <code>~/.m2/settings.xml</code> contains the following definition</p>
+<p>Make sure your <code class="highlighter-rouge">~/.m2/settings.xml</code> contains the following definition</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console"><?xml version="1.0"?>
<settings>
<servers>
@@ -227,8 +227,8 @@ git push --tags</code></pre></figure>
<p><strong>Note</strong>: The steps below are part of release-igor.sh script!</p>
<p>When you run <strong>mvn -P release deploy</strong> the generated artifacts will be uploaded into a Nexus staging repository.</p>
<p>Maven sends a username/password when attempting to upload the artifacts.</p>
-<p>The <code><id></code> of the staging repository is: <strong>apache.releases.https</strong>.</p>
-<p>Place a <code><server></code> definition in your <code>~/.m2/settings.xml</code> file like this:</p>
+<p>The <code class="highlighter-rouge"><id></code> of the staging repository is: <strong>apache.releases.https</strong>.</p>
+<p>Place a <code class="highlighter-rouge"><server></code> definition in your <code class="highlighter-rouge">~/.m2/settings.xml</code> file like this:</p>
<figure class="highlight"><pre><code class="language-console" data-lang="console"><?xml version="1.0"?>
<settings>
<servers>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/contribute/write.html
----------------------------------------------------------------------
diff --git a/content/contribute/write.html b/content/contribute/write.html
index 6bfd806..e9fa9cb 100644
--- a/content/contribute/write.html
+++ b/content/contribute/write.html
@@ -89,14 +89,14 @@ and other variables. If it doesn’t include the YAML preamble, it won’t be
rendered correctly.</p>
<p>The default layout supports a property to specify the main title for the page and
another property for an additional subtitle.</p>
-<p>For example: (the <code>---</code> must be included):</p>
+<p>For example: (the <code class="highlighter-rouge">---</code> must be included):</p>
<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="nn">---</span>
<span class="s">layout</span><span class="pi">:</span> <span class="s">default</span>
<span class="s">title</span><span class="pi">:</span> <span class="s">Main title</span>
<span class="s">subtitle</span><span class="pi">:</span> <span class="s">Subtitle</span>
<span class="nn">---</span></code></pre></figure>
<p>A more advanced feature for the default layout is the ability to specify more files to include
-in the final page. This can be done with property <code>additionalContents</code> where we can list additional files
+in the final page. This can be done with property <code class="highlighter-rouge">additionalContents</code> where we can list additional files
with an id for their section tag and a value for the CSS class:</p>
<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="nn">---</span>
<span class="s">layout</span><span class="pi">:</span> <span class="s">default</span>
@@ -115,8 +115,8 @@ with an id for their section tag and a value for the CSS class:</p>
<h4 id="additional-conventions">Additional conventions</h4>
<p>The following conventions have been adopted for the templeates of the site pages:</p>
<ul>
- <li>Any link to static resources (css, js, pictures, etc.) is prefixed with <code>site.baseurl</code> to support <a href="http://jekyllrb.com/docs/github-pages/#project-page-url-structure">GitHub free hosting</a>. However, to run the project locally you don’t need to specify any baseurl.</li>
- <li>Site posts use custom tag <code><!--more--></code> as <code>excerpt_separator</code>.</li>
+ <li>Any link to static resources (css, js, pictures, etc.) is prefixed with <code class="highlighter-rouge">site.baseurl</code> to support <a href="http://jekyllrb.com/docs/github-pages/#project-page-url-structure">GitHub free hosting</a>. However, to run the project locally you don’t need to specify any baseurl.</li>
+ <li>Site posts use custom tag <code class="highlighter-rouge"><!--more--></code> as <code class="highlighter-rouge">excerpt_separator</code>.</li>
</ul>
<h3 id="syntax-highlighting">Syntax highlighting</h3>
<p>If you have a need to render code in your templates and have it syntax
@@ -124,13 +124,13 @@ highlighted, surround the code with {\% highlight java \%} (substitute java
with the language you want highlighted.)</p>
<h3 id="menu">Menu</h3>
<p>If you want your page linked from every page, include the link in
-<code>_includes/header.html</code>.</p>
+<code class="highlighter-rouge">_includes/header.html</code>.</p>
<h3 id="blog-posts">Blog posts</h3>
<p>For news items such as release announcements, new committers and other
happenings, it is appriorate to create a blog post. The blog post is
automatically added to the front page and the RSS feed.</p>
<p>The blog items are written using the normal Jekyll syntax. The filename needs
-to be formatted as <code>yyyy-mm-dd-title.md</code> and the blog item should start with a
+to be formatted as <code class="highlighter-rouge">yyyy-mm-dd-title.md</code> and the blog item should start with a
YAML preamble, similar to normal pages:</p>
<figure class="highlight"><pre><code class="language-yaml" data-lang="yaml"><span class="nn">---</span>
<span class="s">layout</span><span class="pi">:</span> <span class="s">post</span>
@@ -140,7 +140,7 @@ YAML preamble, similar to normal pages:</p>
<p>When you’re done with making your changes, please check the following:</p>
<ul>
<li>Do the modified files contain only those changes that you actually want to
-publish? (Use <code>git status</code> to check)</li>
+publish? (Use <code class="highlighter-rouge">git status</code> to check)</li>
<li>Did you start Jekyll to generate the site?</li>
</ul>
<p>If these things are OK, you can either create a pull request when
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/index.html
----------------------------------------------------------------------
diff --git a/content/index.html b/content/index.html
index 42ac641..82b120e 100644
--- a/content/index.html
+++ b/content/index.html
@@ -316,7 +316,7 @@ migration guide found at</p>
<ul>
<li>[WICKET-5951] - Upgrade Atmosphere to 2.2.8</li>
</ul>
- <a href="/news/2015/11/16/wicket-6-21-0-released.html">Read more...</a>
+ <a href="/news/2015/11/16/wicket-6.21.0-released.html">Read more...</a>
</article>
</div>
<div class="l-one-third news">
@@ -331,31 +331,31 @@ get updates in your favorite RSS reader the moment they happen.</p>
<h3>Apache Wicket 1.4.x end of life</h3>
<small>15 Nov 2015</small>
The Apache Wicket team announces that support for Apache Wicket 1.4.x ends on 16 November 2015. On the same day Wicket 1.5.x enters “security fixes”...
- <a href="/news/2015/11/15/wicket-1-4-x-eol.html">more</a>
+ <a href="/news/2015/11/15/wicket-1.4.x-eol.html">more</a>
</li>
<li>
<h3>Apache Wicket 7.1.0 released</h3>
<small>25 Oct 2015</small>
The Apache Wicket PMC is proud to announce Apache Wicket 7.1.0! This release marks another minor release of Wicket 7. We use semantic versioning for...
- <a href="/news/2015/10/25/wicket-7-1-0-released.html">more</a>
+ <a href="/news/2015/10/25/wicket-7.1.0-released.html">more</a>
</li>
<li>
<h3>Wicket 1.5.14 released</h3>
<small>24 Oct 2015</small>
This is the fourteenth maintenance release of the Wicket 1.5.x series. This release brings over 4 bug fixes and 1 improvement. CHANGELOG for 1.5.14: **...
- <a href="/news/2015/10/24/wicket-1-5-14-released.html">more</a>
+ <a href="/news/2015/10/24/wicket-1.5.14-released.html">more</a>
</li>
<li>
<h3>Apache Wicket v7.0 released</h3>
<small>28 Jul 2015</small>
The Apache Software Foundation announces Apache Wicket™ v7.0 Open Source Java web framework that powers thousands of web applications and web sites for governments, stores,...
- <a href="/news/2015/07/28/wicket-7-0-released.html">more</a>
+ <a href="/news/2015/07/28/wicket-7.0-released.html">more</a>
</li>
<li>
<h3>Apache Wicket 7.0.0-M6 released</h3>
<small>21 Jun 2015</small>
The Apache Wicket PMC is proud to announce Apache Wicket 7.0.0-M6! We have released another milestone release for Apache Wicket 7. We aim to finalise...
- <a href="/news/2015/06/21/wicket-7-0-0-m6-released.html">more</a>
+ <a href="/news/2015/06/21/wicket-7.0.0-M6-released.html">more</a>
</li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/ajaxcounter.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/ajaxcounter.html b/content/learn/examples/ajaxcounter.html
index 8460f2d..1198423 100644
--- a/content/learn/examples/ajaxcounter.html
+++ b/content/learn/examples/ajaxcounter.html
@@ -54,8 +54,8 @@ building a simple counter that updates through Ajax link clicks.</p>
<p>In all the Wicket examples, you have to put all files in the same package
directory. This means putting the markup files and the java files next to one
another. It is possible to alter this behavior, but that is beyond the scope
-of this example. The only exception is the obligatory <code>web.xml</code> file which
-should reside in the <code>WEB-INF/</code> directory of your web application root
+of this example. The only exception is the obligatory <code class="highlighter-rouge">web.xml</code> file which
+should reside in the <code class="highlighter-rouge">WEB-INF/</code> directory of your web application root
folder.</p>
<p>In this example we assume you already have read and understood the other
examples which give you information on the structure and nature of Wicket
@@ -96,8 +96,8 @@ how it works on the Java side:</p>
<span class="n">add</span><span class="o">(</span><span class="k">new</span> <span class="n">Label</span><span class="o"><</span><span class="n">Integer</span><span class="o">>(</span><span class="s">"counter"</span><span class="o">,</span> <span class="n">model</span><span class="o">));</span>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
-<p>In this class we created a <code>Model</code> subclass that increases its counter
-everytime the <code>getObject</code> method gets called, and returns its value. We set
+<p>In this class we created a <code class="highlighter-rouge">Model</code> subclass that increases its counter
+everytime the <code class="highlighter-rouge">getObject</code> method gets called, and returns its value. We set
this model on the label component, so that each time the label gets rendered
the counter gets increased.</p>
<p>The link doesn’t do anything, just listen to the requests and update the
@@ -108,7 +108,7 @@ so let’s make it more modern by adding some Ajax stuff.</p>
<h2 id="adding-ajax">Adding Ajax</h2>
<p>To make this a more modern UI we’ll have to change a couple of things. First
we need to make the link an Ajax link. Wicket provides several types of Ajax
-links, but the best one for our purposes is the <code>AjaxFallbackLink</code>, as it
+links, but the best one for our purposes is the <code class="highlighter-rouge">AjaxFallbackLink</code>, as it
provides a fallback to a normal request in case no Ajax is available.</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">package</span> <span class="n">wicket</span><span class="o">.</span><span class="na">quickstart</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">wicket.Component</span><span class="o">;</span>
@@ -133,8 +133,8 @@ provides a fallback to a normal request in case no Ajax is available.</p>
<span class="n">add</span><span class="o">(</span><span class="k">new</span> <span class="n">Label</span><span class="o"><</span><span class="n">Integer</span><span class="o">>(</span><span class="s">"counter"</span><span class="o">,</span> <span class="n">model</span><span class="o">));</span>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
-<p>As you can see, the <code>Link</code> has been replaced with the <code>AjaxFallbackLink</code>, and the
-<code>onClick</code> method now takes a new argument: the <code>AjaxRequestTarget</code>. If you want a
+<p>As you can see, the <code class="highlighter-rouge">Link</code> has been replaced with the <code class="highlighter-rouge">AjaxFallbackLink</code>, and the
+<code class="highlighter-rouge">onClick</code> method now takes a new argument: the <code class="highlighter-rouge">AjaxRequestTarget</code>. If you want a
component to be updated in the Ajax request, you’ll have to add them to the
target. So let’s alter the file to make it possible to add the label to the
request target.</p>
@@ -168,7 +168,7 @@ request target.</p>
<p>We’ve moved the instantiation of the label to the beginning of the page
constructor and made a local, final variable. This way we can reference the
label in the event handler of the link component.</p>
-<p>We also had to call <code>setOutputMarkupId(true)</code> on the label to be able to
+<p>We also had to call <code class="highlighter-rouge">setOutputMarkupId(true)</code> on the label to be able to
update the component when the request is returned to the client browser. If
we don’t, Wicket will not know how to update the markup in the client.</p>
<p>If you put this code into your page’s class, then you’ll have a working Ajax
@@ -179,9 +179,9 @@ require a degree in JavaScript. Even better, you don’t necessarily need to
update your markup file to work with Ajax. In this (simple) example we were
able to add Ajax behavior to the page without touching the markup file.</p>
<p>The most important lesson here is that in order to update components using
-Ajax is that you need to add those components to the <code>AjaxRequestTarget</code> and
+Ajax is that you need to add those components to the <code class="highlighter-rouge">AjaxRequestTarget</code> and
that the components that are to be updated in that request, should have
-<code>setOutputMarkupId(true)</code>.</p>
+<code class="highlighter-rouge">setOutputMarkupId(true)</code>.</p>
</section>
</div>
</main>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/dropdownchoice.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/dropdownchoice.html b/content/learn/examples/dropdownchoice.html
index 627cf5e..6f69ead 100644
--- a/content/learn/examples/dropdownchoice.html
+++ b/content/learn/examples/dropdownchoice.html
@@ -50,14 +50,14 @@
</section>
<section class="l-two-third left">
<p>One of the most problematic components for beginners of Wicket is the
-<code>DropDownChoice</code> component. In this example we will work the component to
+<code class="highlighter-rouge">DropDownChoice</code> component. In this example we will work the component to
give a little more insight into its workings. This example requires that you
have some understanding of the Wicket component model (nothing fancy though,
but you might want to read the other examples first), and the Model concept
used in Wicket (you can read more on models
<a href="https://cwiki.apache.org/confluence/display/WICKET/Working+with+Wicket+models">here</a>).</p>
<h2 id="the-example-domain">The example domain</h2>
-<p>The <code>DropDownChoice</code> component is typically used <em>inside</em> a form. This
+<p>The <code class="highlighter-rouge">DropDownChoice</code> component is typically used <em>inside</em> a form. This
example will expand on that usage. The component is particularly designed to
work with objects. So let’s say we have a list of people and we want to
select the manager of an employee.</p>
@@ -110,8 +110,8 @@ is how the page would look like in HTML:</p>
<li>a label (to show the name of the employee) and</li>
<li>a select box for picking the manager.</li>
</ul>
-<p>We will focus on the select box, because that will be our <code>DropDownChoice</code>.
-The <code><option></code> tags are there for preview, our component will replace them
+<p>We will focus on the select box, because that will be our <code class="highlighter-rouge">DropDownChoice</code>.
+The <code class="highlighter-rouge"><option></code> tags are there for preview, our component will replace them
with the generated choices.</p>
<p>Let’s see how the page looks like from the Java side:</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kd">public</span> <span class="kd">class</span> <span class="nc">AssignManagerPage</span> <span class="kd">extends</span> <span class="n">WebPage</span> <span class="o">{</span>
@@ -132,12 +132,12 @@ with the generated choices.</p>
<span class="n">form</span><span class="o">.</span><span class="na">add</span><span class="o">(</span><span class="n">ddc</span><span class="o">));</span>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
-<p>In this example you see that we add the <code>DropDownChoice</code> to the form, and
+<p>In this example you see that we add the <code class="highlighter-rouge">DropDownChoice</code> to the form, and
provide it with 3 parameters. The first is the component identifier. The
-second is the item that needs to be updated, in this case the <code>managedBy</code>
-field of the <code>employee</code>. The third parameter is a <code>LoadableDetachableModel</code>
+second is the item that needs to be updated, in this case the <code class="highlighter-rouge">managedBy</code>
+field of the <code class="highlighter-rouge">employee</code>. The third parameter is a <code class="highlighter-rouge">LoadableDetachableModel</code>
that retrieves the list of available choices.</p>
-<p>Note that the <code>DropDownChoice</code> component has many constructors, and that you
+<p>Note that the <code class="highlighter-rouge">DropDownChoice</code> component has many constructors, and that you
need to read the JavaDoc documentation to pick the right one for you.</p>
<p>This generates (basically) the following markup when the list of managers is
Kyle Brovlovski, Stan Marsh, Eric Cartman, and Kenny McCormick:</p>
@@ -157,17 +157,17 @@ Kyle Brovlovski, Stan Marsh, Eric Cartman, and Kenny McCormick:</p>
managers list and numbered the values of the options. These are the indices
of the items in the list. If the order of the list can change between
requests, <em>or</em> if the list itself can change, then please use an
-<code>IChoiceRenderer</code>.</p>
+<code class="highlighter-rouge">IChoiceRenderer</code>.</p>
<h2 id="selecting-a-choice">Selecting a choice</h2>
<p>Now if a user selects a value and submits the form, Wicket will assign the
-manager to the employee (the <code>PropertyModel</code> takes care of that). The
+manager to the employee (the <code class="highlighter-rouge">PropertyModel</code> takes care of that). The
following list shows what basically happens:</p>
<ol>
- <li>create new Employee, with <code>null</code> for its manager</li>
+ <li>create new Employee, with <code class="highlighter-rouge">null</code> for its manager</li>
<li>create AssignManagerPage with the employee</li>
- <li>render page, selected value is <code>"Choose one"</code></li>
+ <li>render page, selected value is <code class="highlighter-rouge">"Choose one"</code></li>
<li>user selects “Eric Cartman” and submits form</li>
- <li>Wicket assigns manager “Eric Cartman” to <code>managedBy</code> field of the employee</li>
+ <li>Wicket assigns manager “Eric Cartman” to <code class="highlighter-rouge">managedBy</code> field of the employee</li>
</ol>
<p>So there is no need for getting or setting the value from the drop down
component: Wicket binds directly to your domain objects if you use the
@@ -182,7 +182,7 @@ the rest:</p>
<span class="n">newEmployee</span><span class="o">.</span><span class="na">setManagedBy</span><span class="o">(</span><span class="n">manager</span><span class="o">);</span>
<span class="n">setResponsePage</span><span class="o">(</span><span class="k">new</span> <span class="n">AssignManagerPage</span><span class="o">(</span><span class="n">newEmployee</span><span class="o">));</span></code></pre></figure>
<h2 id="summary">Summary</h2>
-<p>This concludes the (small) example of using a <code>DropDownChoice</code> component
+<p>This concludes the (small) example of using a <code class="highlighter-rouge">DropDownChoice</code> component
correctly. The ideas behind Wicket are perfectly reflected in this component:
work with your domain objects, bind them to your components and get on with
the rest of your application.</p>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/guestbook.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/guestbook.html b/content/learn/examples/guestbook.html
index 6367fa4..a9762f2 100644
--- a/content/learn/examples/guestbook.html
+++ b/content/learn/examples/guestbook.html
@@ -51,7 +51,7 @@
<section class="l-two-third left">
<p>The GuestBook application allows users to enter comments that appear on a
page like a weblog. Drawing the list of comments is very easy with the Wicket
-<code>ListView</code> component. This example also gives an impression of what form
+<code class="highlighter-rouge">ListView</code> component. This example also gives an impression of what form
handling is like.</p>
<p><img src="guestbook.png" alt="Guestbook screenshot" /></p>
<p>As with all examples, you have to put all files in the same package
@@ -89,17 +89,17 @@ of this example.</p>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
<h2 id="guestbookjava">GuestBook.java</h2>
-<p>In the file <code>GuestBook.java</code> we have put the Java component code for the
+<p>In the file <code class="highlighter-rouge">GuestBook.java</code> we have put the Java component code for the
guestbook page. This is the homepage for the guestbook application. The page
consists of a form for entering new items to the guestbook and a list of
repeating markup for showing the guestbook entries.</p>
-<p>The <code>GuestBook</code> constructor adds a <code>CommentForm</code> and a <code>ListView</code> of
+<p>The <code class="highlighter-rouge">GuestBook</code> constructor adds a <code class="highlighter-rouge">CommentForm</code> and a <code class="highlighter-rouge">ListView</code> of
the comments. Notice how the model is passed in as the second argument to the
-<code>ListView</code> constructor.</p>
-<p>Then as the view renders, the <code>populateItem</code> method is called passing in a
-<code>ListItem</code> container for the current row in the list.</p>
-<p>The implementation below obtains the <code>Comment</code> POJO from the list item and
-adds label components for the date and text of the <code>Comment</code>. This is all
+<code class="highlighter-rouge">ListView</code> constructor.</p>
+<p>Then as the view renders, the <code class="highlighter-rouge">populateItem</code> method is called passing in a
+<code class="highlighter-rouge">ListItem</code> container for the current row in the list.</p>
+<p>The implementation below obtains the <code class="highlighter-rouge">Comment</code> POJO from the list item and
+adds label components for the date and text of the <code class="highlighter-rouge">Comment</code>. This is all
accomplished in just a few lines of code.</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">package</span> <span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class="o">.</span><span class="na">wicket</span><span class="o">.</span><span class="na">examples</span><span class="o">.</span><span class="na">guestbook</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">java.util.ArrayList</span><span class="o">;</span>
@@ -177,26 +177,26 @@ accomplished in just a few lines of code.</p>
<span class="n">commentList</span><span class="o">.</span><span class="na">clear</span><span class="o">();</span>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
-<p>When the <code>CommentForm</code> is submitted, the <code>onSubmit()</code> method is called.
-Notice that nothing gets the value of the <code>TextArea</code> that was added in the
-<code>CommentForm</code> constructor. This is because the comment is the model and the
-third parameter to the <code>TextArea</code> constructor specified the property of the
-model to update. So all <code>onSubmit()</code> has to do is create a new comment from
+<p>When the <code class="highlighter-rouge">CommentForm</code> is submitted, the <code class="highlighter-rouge">onSubmit()</code> method is called.
+Notice that nothing gets the value of the <code class="highlighter-rouge">TextArea</code> that was added in the
+<code class="highlighter-rouge">CommentForm</code> constructor. This is because the comment is the model and the
+third parameter to the <code class="highlighter-rouge">TextArea</code> constructor specified the property of the
+model to update. So all <code class="highlighter-rouge">onSubmit()</code> has to do is create a new comment from
the model that was updated and add it to the comment list. When the page
redraws, the new list will be rendered.</p>
-<p>We use a synchronized list as our shared static model used by <code>commentListView</code>
-(<code>commentList</code>) to ensure that it is only updated by one thread at a time.
+<p>We use a synchronized list as our shared static model used by <code class="highlighter-rouge">commentListView</code>
+(<code class="highlighter-rouge">commentList</code>) to ensure that it is only updated by one thread at a time.
Remember, this is a multi-user application with a shared model!</p>
-<p>Finally, you may notice the call to <code>commentListView.modelChanged()</code>. This
+<p>Finally, you may notice the call to <code class="highlighter-rouge">commentListView.modelChanged()</code>. This
informs the list view that its model has been modified. In more advanced
usage scenarios, this would allow Wicket to expire stale pages accessed with
the browser’s back button.</p>
<h2 id="guestbookhtml">GuestBook.html</h2>
-<p>In the HTML below, notice the way that the <code>TextArea</code> component is being
-nested inside the <code>CommentForm</code>. Wicket is able to keep everything straight
-because the Java <code>Component.add()</code> calls have to result in the same nesting
+<p>In the HTML below, notice the way that the <code class="highlighter-rouge">TextArea</code> component is being
+nested inside the <code class="highlighter-rouge">CommentForm</code>. Wicket is able to keep everything straight
+because the Java <code class="highlighter-rouge">Component.add()</code> calls have to result in the same nesting
structure as the HTML.</p>
-<p>Finally, notice the <code><wicket:remove></code> block. This is simply markup that is
+<p>Finally, notice the <code class="highlighter-rouge"><wicket:remove></code> block. This is simply markup that is
there for previewing purposes only. When the page renders, it is stripped
out.</p>
<figure class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt"><html</span> <span class="na">xmlns:wicket=</span><span class="s">"http://wicket.apache.org/"</span><span class="nt">></span>
@@ -230,8 +230,8 @@ out.</p>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
<h2 id="guestbookapplicationjava">GuestBookApplication.java</h2>
-<p>For completeness, we’ve included the <code>GuestBookApplication</code> class, and as a
-final treat the modifications to the <code>web.xml</code> file.</p>
+<p>For completeness, we’ve included the <code class="highlighter-rouge">GuestBookApplication</code> class, and as a
+final treat the modifications to the <code class="highlighter-rouge">web.xml</code> file.</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">package</span> <span class="n">org</span><span class="o">.</span><span class="na">apache</span><span class="o">.</span><span class="na">wicket</span><span class="o">.</span><span class="na">examples</span><span class="o">.</span><span class="na">guestbook</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">org.apache.wicket.Page</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">org.apache.wicket.examples.WicketExampleApplication</span><span class="o">;</span>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/helloworld.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/helloworld.html b/content/learn/examples/helloworld.html
index 3889498..fdc6dcf 100644
--- a/content/learn/examples/helloworld.html
+++ b/content/learn/examples/helloworld.html
@@ -78,7 +78,7 @@ defines what the home page is, and allows for some configuration.</p>
<span class="k">return</span> <span class="n">HelloWorld</span><span class="o">.</span><span class="na">class</span><span class="o">;</span>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
-<p>Here you can see that we define <code>wicket.examples.helloworld.HelloWorld</code> to be
+<p>Here you can see that we define <code class="highlighter-rouge">wicket.examples.helloworld.HelloWorld</code> to be
our home page. When the base URL of our application is requested, the markup
rendered by the HelloWorld page is returned.</p>
<h3 id="helloworldjava">HelloWorld.java</h3>
@@ -99,8 +99,8 @@ rendered by the HelloWorld page is returned.</p>
</li>
</ol>
<p>The first parameter is the component identifier, which Wicket uses to identify
-the <code>Label</code> component in your HTML markup. The second parameter is the message
-which the <code>Label</code> should render.</p>
+the <code class="highlighter-rouge">Label</code> component in your HTML markup. The second parameter is the message
+which the <code class="highlighter-rouge">Label</code> should render.</p>
<h3 id="helloworldhtml">HelloWorld.html</h3>
<p>The HTML file that defines our Hello World functionality is as follows:</p>
<figure class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt"><html></span>
@@ -111,16 +111,16 @@ which the <code>Label</code> should render.</p>
<p>In this file, you see two elements that need some attention:</p>
<ul>
<li>
- <p>the component declaration <code><span wicket:id="message"></code></p>
+ <p>the component declaration <code class="highlighter-rouge"><span wicket:id="message"></code></p>
</li>
<li>
- <p>the text <code>Message goes here</code></p>
+ <p>the text <code class="highlighter-rouge">Message goes here</code></p>
</li>
</ul>
-<p>The component declaration consists of the Wicket identifier <code>wicket:id</code> and the
-component identifier <code>message</code>. The component identifier should be the same as
-the name of the component you defined in your <code>WebPage</code>. The text between
-the <code><span></code> tags is removed when the component renders its message. The final
+<p>The component declaration consists of the Wicket identifier <code class="highlighter-rouge">wicket:id</code> and the
+component identifier <code class="highlighter-rouge">message</code>. The component identifier should be the same as
+the name of the component you defined in your <code class="highlighter-rouge">WebPage</code>. The text between
+the <code class="highlighter-rouge"><span></code> tags is removed when the component renders its message. The final
content of the component is determined by your Java code.</p>
<h3 id="webxml">web.xml</h3>
<p>In order to deploy our HelloWorld program, we need to make our application
@@ -155,7 +155,7 @@ JavaScript files, images and so forth will be served by the container.</p>
<h2 id="ready-to-deploy">Ready to deploy</h2>
<p>That’s it. No more configuration necessary! All you need to do now is to
deploy the web application into your favorite application server. Point your
-browser to the url: <code>http://<servername>/<warfilename>/</code>, substituting
+browser to the url: <code class="highlighter-rouge">http://<servername>/<warfilename>/</code>, substituting
servername and warfilename to the appropriate values, such as
http://localhost:8080/helloworld/.</p>
<p>As you can see: no superfluous XML configuration files are needed to enable a
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/index.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/index.html b/content/learn/examples/index.html
index ec871fe..950b7f8 100644
--- a/content/learn/examples/index.html
+++ b/content/learn/examples/index.html
@@ -54,8 +54,8 @@ should speak for themselves in demonstrating how easy it is to get things done
in Wicket when compared to other frameworks. You will discover that Wicket’s
component-oriented structure and its “low touch” approach to HTML is quite
inviting.</p>
-<p>You can see these examples and many more in <a href="http://www.wicket-library.com">live
-action</a> without having to install anything.</p>
+<p>You can see these examples and many more in live
+action (available for version <a href="http://examples7x.wicket.apache.org/index.html">7.x</a> and <a href="http://examples6x.wicket.apache.org/index.html">6.x</a>) without having to install anything.</p>
<ul>
<li><a href="helloworld.html">Hello World!</a> - Everybody’s favorite example</li>
<li><a href="navomatic.html">Navomatic</a> - Automatic navigation using Borders and Links</li>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/markupinheritance.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/markupinheritance.html b/content/learn/examples/markupinheritance.html
index cb5ffeb..152b29c 100644
--- a/content/learn/examples/markupinheritance.html
+++ b/content/learn/examples/markupinheritance.html
@@ -54,8 +54,8 @@ and panel layouts.</p>
<p>In all the Wicket examples, you have to put all files in the same package
directory. This means putting the markup files and the java files next to one
another. It is possible to alter this behavior, but that is beyond the scope
-of this example. The only exception is the obligatory <code>web.xml</code> file which
-should reside in the <code>WEB-INF/</code> directory of your web application root
+of this example. The only exception is the obligatory <code class="highlighter-rouge">web.xml</code> file which
+should reside in the <code class="highlighter-rouge">WEB-INF/</code> directory of your web application root
folder.</p>
<p>In this example we assume you already have read and understood the other
examples which give you information on the structure and nature of Wicket
@@ -71,8 +71,8 @@ focuses on one strategy: markup inheritance.</p>
<p>In Java you can extend classes. This same concept has been fitted into the
markup parsing of Java. Markup containers that have files associated (page
and panels) can inherit the markup of their super containers.</p>
-<p>This is done using two special Wicket tags: <code><wicket:child></code> and
-<code><wicket:extend></code>. In the super markup you define where the child markup
+<p>This is done using two special Wicket tags: <code class="highlighter-rouge"><wicket:child></code> and
+<code class="highlighter-rouge"><wicket:extend></code>. In the super markup you define where the child markup
should be put, and in the sub markup you delineate where the child markup
starts and ends.</p>
<figure class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt"><html></span>
@@ -83,9 +83,9 @@ starts and ends.</p>
This is in the super markup.<span class="nt"><br></span>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
-<p>In this markup you see two sentences that surround the <code><wicket:child></code> tag.
+<p>In this markup you see two sentences that surround the <code class="highlighter-rouge"><wicket:child></code> tag.
All markup in this file will remain when a sub class of this page is created,
-only the <code><wicket:child></code> tag will be replaced with the child markup. So if we
+only the <code class="highlighter-rouge"><wicket:child></code> tag will be replaced with the child markup. So if we
look at the following markup:</p>
<figure class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt"><html></span>
<span class="nt"><head></head></span>
@@ -98,7 +98,7 @@ look at the following markup:</p>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
<p>we can see the markup that should be included in the parent. Only the markup
-between the <code><wicket:extend></code> tags is included in the final page. Take a look
+between the <code class="highlighter-rouge"><wicket:extend></code> tags is included in the final page. Take a look
at the following markup which is the final markup when you would use this in
a Wicket application.</p>
<figure class="highlight"><pre><code class="language-html" data-lang="html"><span class="nt"><html></span>
@@ -111,8 +111,8 @@ a Wicket application.</p>
This is in the super markup.<span class="nt"><br></span>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
-<p>Here you can see that the <code><wicket:child /></code> tag has been expanded, and its
-contents filled with exactly the markup between the <code><wicket:extend></code> tags.
+<p>Here you can see that the <code class="highlighter-rouge"><wicket:child /></code> tag has been expanded, and its
+contents filled with exactly the markup between the <code class="highlighter-rouge"><wicket:extend></code> tags.
If you want to get rid of the special Wicket tags, you can disable that on
the markup settings
(see <a href="https://ci.apache.org/projects/wicket/apidocs/6.x/org/apache/wicket/settings/IMarkupSettings.html">IMarkupSettings</a> for Wikcet6
@@ -152,17 +152,17 @@ practise. Now let’s take a look at the markup for the BasePage</p>
<p>In this markup file you see the specific basic layout: we have 3 div
elements:</p>
<ol>
- <li><code><div id="header">...</div></code></li>
- <li><code><div id="body">...</div></code></li>
- <li><code><div id="footer">...</div></code></li>
+ <li><code class="highlighter-rouge"><div id="header">...</div></code></li>
+ <li><code class="highlighter-rouge"><div id="body">...</div></code></li>
+ <li><code class="highlighter-rouge"><div id="footer">...</div></code></li>
</ol>
<p>Note that these aren’t Wicket components, just plain markup. We could have
-made them components, such as a <code>Panel</code> but for brevity we keep it this way.
-Now that we have the <code>BasePage</code> finished, we can implement the two subclasses
+made them components, such as a <code class="highlighter-rouge">Panel</code> but for brevity we keep it this way.
+Now that we have the <code class="highlighter-rouge">BasePage</code> finished, we can implement the two subclasses
to finish this example.</p>
<h2 id="implementing-the-sub-pages">Implementing the sub pages</h2>
-<p>We need to build two pages: <code>Page1</code> and <code>Page2</code>. Each page needs its own
-markup file and Java class. Let’s first implement <code>Page1</code>.</p>
+<p>We need to build two pages: <code class="highlighter-rouge">Page1</code> and <code class="highlighter-rouge">Page2</code>. Each page needs its own
+markup file and Java class. Let’s first implement <code class="highlighter-rouge">Page1</code>.</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">package</span> <span class="n">wicket</span><span class="o">.</span><span class="na">quickstart</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">wicket.markup.html.basic.Label</span><span class="o">;</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">Page1</span> <span class="kd">extends</span> <span class="n">BasePage</span> <span class="o">{</span>
@@ -171,9 +171,9 @@ markup file and Java class. Let’s first implement <code>Page1</code>.</p>
<span class="o">}</span>
<span class="o">}</span></code></pre></figure>
<p>In this example you see that we add a new label component to the page:
-<code>label1</code>. This component is only available for <code>Page1</code>, as such <code>Page2</code> can
+<code class="highlighter-rouge">label1</code>. This component is only available for <code class="highlighter-rouge">Page1</code>, as such <code class="highlighter-rouge">Page2</code> can
define its own component hierarchy. Let’s take a look at the markup for
-<code>Page1</code>:</p>
+<code class="highlighter-rouge">Page1</code>:</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="o"><</span><span class="n">html</span><span class="o">></span>
<span class="o"><</span><span class="n">head</span><span class="o">></</span><span class="n">head</span><span class="o">></span>
<span class="o"><</span><span class="n">body</span><span class="o">></span>
@@ -183,10 +183,10 @@ define its own component hierarchy. Let’s take a look at the markup for
<span class="o"></</span><span class="nl">wicket:</span><span class="n">extend</span><span class="o">></span>
<span class="o"></</span><span class="n">body</span><span class="o">></span>
<span class="o"></</span><span class="n">html</span><span class="o">></span></code></pre></figure>
-<p>Here you see that we added the <code>Label</code> component in the markup between the
-<code><wicket:extend></code> tags. If we were to add the component outside those tags,
+<p>Here you see that we added the <code class="highlighter-rouge">Label</code> component in the markup between the
+<code class="highlighter-rouge"><wicket:extend></code> tags. If we were to add the component outside those tags,
Wicket will not be able to render the component in the final page.</p>
-<p>Now, let’s do the same for <code>Page2</code>.</p>
+<p>Now, let’s do the same for <code class="highlighter-rouge">Page2</code>.</p>
<figure class="highlight"><pre><code class="language-java" data-lang="java"><span class="kn">package</span> <span class="n">wicket</span><span class="o">.</span><span class="na">quickstart</span><span class="o">;</span>
<span class="kn">import</span> <span class="nn">wicket.markup.html.basic.Label</span><span class="o">;</span>
<span class="kd">public</span> <span class="kd">class</span> <span class="nc">Page2</span> <span class="kd">extends</span> <span class="n">BasePage</span> <span class="o">{</span>
@@ -203,10 +203,10 @@ Wicket will not be able to render the component in the final page.</p>
<span class="nt"></wicket:extend></span>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
-<p>In <code>Page2</code> you see that we have a different component structure (<code>label2</code>
-instead of <code>label1</code>), and as such that the pages are quite different.</p>
+<p>In <code class="highlighter-rouge">Page2</code> you see that we have a different component structure (<code class="highlighter-rouge">label2</code>
+instead of <code class="highlighter-rouge">label1</code>), and as such that the pages are quite different.</p>
<p>If you paste this code into a Wicket quickstart application, you can see it
-immediately working (don’t forget to set the homepage to <code>Page1</code> or <code>Page2</code>).</p>
+immediately working (don’t forget to set the homepage to <code class="highlighter-rouge">Page1</code> or <code class="highlighter-rouge">Page2</code>).</p>
<h2 id="conclusion">Conclusion</h2>
<p>With markup inheritance you can get a standard layout for your application
without too much hassle. It follows the natural inheritance strategy for Java
@@ -214,9 +214,9 @@ code and makes encapsulation of your component hierarchy possible.</p>
<p>In this example we haven’t touched on the other possible features of markup
inheritance:</p>
<ul>
- <li>contributing to the <code><head></code> section from your sub pages</li>
+ <li>contributing to the <code class="highlighter-rouge"><head></code> section from your sub pages</li>
<li>multiple layers of inheritance (this just works)</li>
- <li>markup inheritance used with <code>Panel</code> components</li>
+ <li>markup inheritance used with <code class="highlighter-rouge">Panel</code> components</li>
</ul>
<p>However, this example should get you up and running.</p>
</section>
http://git-wip-us.apache.org/repos/asf/wicket-site/blob/f39616cb/content/learn/examples/navomatic.html
----------------------------------------------------------------------
diff --git a/content/learn/examples/navomatic.html b/content/learn/examples/navomatic.html
index e228c1f..acad597 100644
--- a/content/learn/examples/navomatic.html
+++ b/content/learn/examples/navomatic.html
@@ -67,7 +67,7 @@ in italics. Also the message box shows that we are viewing Page2 instead of
Page1.</p>
<h2 id="navigation-component">Navigation component</h2>
<p>To create a reusable navigation component we are going to use a
-<code>org.apache.wicket.markup.html.border.Border</code> component. From the Border
+<code class="highlighter-rouge">org.apache.wicket.markup.html.border.Border</code> component. From the Border
Javadoc:</p>
<blockquote>
<p>A border component has associated markup which is drawn and determines
@@ -75,9 +75,9 @@ placement of any markup and/or components nested within the border
component.</p>
</blockquote>
<p>The portion of the border’s associated markup file which is to be used in
-rendering the border is denoted by a <code><wicket:border></code> tag. The children of the
+rendering the border is denoted by a <code class="highlighter-rouge"><wicket:border></code> tag. The children of the
border component instance are then inserted into this markup, replacing the
-first <code><wicket:body/></code> tag in the border’s associated markup.</p>
+first <code class="highlighter-rouge"><wicket:body/></code> tag in the border’s associated markup.</p>
<p>For example, here is markup for a simple Border subclass, a usage of that
border, and the markup which would be output on rendering:</p>
<h3 id="border-markup">Border markup</h3>
@@ -102,8 +102,8 @@ border, and the markup which would be output on rendering:</p>
First Middle Last
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
-<p>In other words, the markup around the <code><wicket:body/></code> tag in the border
-component is sort of “wrapped around” the body of the <code><span></code> tag where the
+<p>In other words, the markup around the <code class="highlighter-rouge"><wicket:body/></code> tag in the border
+component is sort of “wrapped around” the body of the <code class="highlighter-rouge"><span></code> tag where the
border is used. This seems simple in this example, but keep in mind that
nested components and even nested borders can appear anywhere in either markup
file. This can be used to create quite complex effects with relatively little
@@ -137,11 +137,11 @@ this case, we set Page1 to be our home page.</p>
<span class="nt"></span></span>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
-<p>Notice that the NavomaticBorder component is attached to the <code><span></code> tag
+<p>Notice that the NavomaticBorder component is attached to the <code class="highlighter-rouge"><span></code> tag
because the name of the component in the Java code is “navomaticBorder” and
-the <code><span></code> tag’s wicket:id attribute is set to “navomaticBorder”. Because the
+the <code class="highlighter-rouge"><span></code> tag’s wicket:id attribute is set to “navomaticBorder”. Because the
two names match, Wicket associates the NavomaticBorder Java component with the
-<code><span></code> tag.</p>
+<code class="highlighter-rouge"><span></code> tag.</p>
<h3 id="page2java">Page2.java</h3>
<p>The Page2 Java and HTML files look almost identical (and we’ll omit the
sources for Page3 altogether because it follows the same pattern):</p>
@@ -204,17 +204,17 @@ is in the NavomaticBorder markup.</p>
<span class="nt"></body></span>
<span class="nt"></html></span></code></pre></figure>
<p>Notice that the markup above encloses the entire contents of the markup file’s
-<code><body></code> with a <code><wicket:border></code> tag, as we described earlier. This lets the
+<code class="highlighter-rouge"><body></code> with a <code class="highlighter-rouge"><wicket:border></code> tag, as we described earlier. This lets the
NavomaticBorder know how much of its markup to use when it wraps itself around
the markup it finds in the context where it is used. Notice also the
-<code><wicket:body/></code> marker which designates where to put whatever is found inside
+<code class="highlighter-rouge"><wicket:body/></code> marker which designates where to put whatever is found inside
the tag at the use context.</p>
-<p>Next, notice that the navigation links and the border’s <code><wicket:body/></code> are
-both enclosed in <code><span></code> tags which have wicket:id attributes that associate
+<p>Next, notice that the navigation links and the border’s <code class="highlighter-rouge"><wicket:body/></code> are
+both enclosed in <code class="highlighter-rouge"><span></code> tags which have wicket:id attributes that associate
those tags with the BoxBorder components added in the NavomaticBorder
constructor. These nested border components will each draw a thin black line
around their contents.</p>
-<p>Finally, the <code><wicket:link></code> tag is used to mark the links in the navigation
+<p>Finally, the <code class="highlighter-rouge"><wicket:link></code> tag is used to mark the links in the navigation
as automatic links. Ordinarily, you would need to create link components and
attach them to your page manually, but anchor links that are marked as
automatic are parsed and hooked up to link components for you, as appropriate.