You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by hl...@apache.org on 2006/06/22 00:31:33 UTC
svn commit: r416139 - in /tapestry/tapestry-site/trunk/src/site:
resources/images/2006_dukeschoice.jpg
resources/images/dukes_choice_2006_120x120.png xdoc/index.xml
Author: hlship
Date: Wed Jun 21 15:31:33 2006
New Revision: 416139
URL: http://svn.apache.org/viewvc?rev=416139&view=rev
Log:
Update verbage, add icon and link about Duke's Choice award
Added:
tapestry/tapestry-site/trunk/src/site/resources/images/dukes_choice_2006_120x120.png (with props)
Removed:
tapestry/tapestry-site/trunk/src/site/resources/images/2006_dukeschoice.jpg
Modified:
tapestry/tapestry-site/trunk/src/site/xdoc/index.xml
Added: tapestry/tapestry-site/trunk/src/site/resources/images/dukes_choice_2006_120x120.png
URL: http://svn.apache.org/viewvc/tapestry/tapestry-site/trunk/src/site/resources/images/dukes_choice_2006_120x120.png?rev=416139&view=auto
==============================================================================
Binary file - no diff available.
Propchange: tapestry/tapestry-site/trunk/src/site/resources/images/dukes_choice_2006_120x120.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: tapestry/tapestry-site/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/tapestry/tapestry-site/trunk/src/site/xdoc/index.xml?rev=416139&r1=416138&r2=416139&view=diff
==============================================================================
--- tapestry/tapestry-site/trunk/src/site/xdoc/index.xml (original)
+++ tapestry/tapestry-site/trunk/src/site/xdoc/index.xml Wed Jun 21 15:31:33 2006
@@ -6,17 +6,17 @@
</properties>
<body>
<section name="Welcome to Tapestry">
+ <a href="http://java.sun.com/javaone/sf/dukes_choice_awards.jsp"><img src="images/dukes_choice_2006_120x120.png"
+ alt="Duke's Choice Winner 2006"
+ style="float:right;"/></a>
+ <br/>
+
<div id="downloadbox">
<h5>Get Tapestry 4.0.2</h5>
<p>
<a href="download.html">
- <img valign="top" src="http://tapestry.apache.org/images/folder-open.gif"
- border="0" alt="" title="download" />
- Download
- </a>
- Tapestry 4.0.2
- </p>
-
+ <img valign="top" src="images/folder-open.gif" border="0" alt=""
+ title="download"/> Download </a> Tapestry 4.0.2 </p>
<!--
<ul>
<li>
@@ -37,48 +37,55 @@
</ul>
-->
</div>
- <p>
- Tapestry is an open-source framework for creating dynamic, robust, highly scalable
+ <p> Tapestry is an open-source framework for creating dynamic, robust, highly scalable
web applications in Java. Tapestry complements and builds upon the standard Java
- Servlet API, and so it works in any servlet container or application server.
- </p>
+ Servlet API, and so it works in any servlet container or application server. </p>
+ <p> Tapestry divides a web application into a set of pages, each constructed from
+ components. This provides a consistent structure, allowing the Tapestry framework to
+ assume responsibility for key concerns such as URL construction and dispatch,
+ persistent state storage on the client or on the server, user input validation,
+ localization/internationalization, and exception reporting. Developing Tapestry
+ applications involves creating HTML templates using plain HTML, and combining the
+ templates with small amounts of Java code using (optional) XML descriptor files. In
+ Tapestry, you create your application in terms of objects, and the methods and
+ properties of those objects -- and specifically not in terms of URLs and query
+ parameters. Tapestry brings true object oriented development to Java web
+ applications. </p>
+ <p> Tapestry is specifically designed to make creating new components very easy, as this
+ is a routine approach when building applications. The distribution includes over
+ fifty components, ranging from simple output components all the way up to complex
+ data grids and tree navigators. </p>
+ <p>Tapestry is architected to scale from tiny applications all the way up to massive
+ applications consisting of hundreds of individual pages, developed by large, diverse
+ teams. Tapestry easily integrates with any kind of backend, including J2EE, HiveMind
+ and Spring. </p>
+ <p> Tapestry is released under the Apache Software Licence 2.0.</p>
<p>
- <h4>How it works</h4>
+ <h4>Key Principles</h4>
</p>
<p>Tapestry is organized around four key principles:</p>
-
<ul>
<li><b>Simplicity</b> - web applications shouldn't be rocket science!</li>
<li>
- <b>Consistency</b> - what works in pages should work in components. What works in small
- applications should work in large applications. Different developers should find
- similar solutions to similar problems.
- </li>
+ <b>Consistency</b> - what works in pages should work in components. What works
+ in small applications should work in large applications. Different developers
+ should find similar solutions to similar problems. </li>
<li><b>Efficiency</b> - applications should be performant and scalable</li>
<li>
- <b>Feedback</b> - when things go wrong, the framework should not get in the way; in
- fact, it should provide useful diagnostics
- </li>
+ <b>Feedback</b> - when things go wrong, the framework should not get in the way;
+ in fact, it should provide useful diagnostics </li>
</ul>
- <p>
- <h4>Design</h4>
+ <p> These four principles drive the meta-principle: <em>The simplest choice should be
+ the correct choice.</em>
</p>
- <p>
- These four principles drive the meta-principle:
- <em>The simplest choice should be the correct choice.</em>
- </p>
- <br/><br/>
- <p>
- The decisions you make early in a project should not come back later to haunt you.
- </p>
-
- <p>
- We have found that a component approach to web development is the best way of
+ <br/>
+ <br/>
+ <p> The decisions you make early in a project should not come back later to haunt you. </p>
+ <p> We have found that a component approach to web development is the best way of
realizing these principles. Structuring the framework and your application around
components makes it possible to move all the boring plumbing code out of your
application and into the framework. You write less code, you write simpler code,
- sometimes you write <em>no</em> code. Tapestry picks up the slack.
- </p>
+ sometimes you write <em>no</em> code. Tapestry picks up the slack. </p>
</section>
</body>
</document>