- Revision
- 173
- Author
- mauro
- Date
- 2007-06-20 11:23:17 -0500 (Wed, 20 Jun 2007)
Log Message
Renamed non top-level index.html - as XSite overrides top-level one.
Modified Paths
Added Paths
- trunk/distribution/src/site/content/examples/examples.html
- trunk/distribution/src/site/content/taglib/taglib.html
Removed Paths
Diff
Copied: trunk/distribution/src/site/content/examples/examples.html (from rev 171, trunk/distribution/src/site/content/examples/index.html) (0 => 173)
--- trunk/distribution/src/site/content/examples/examples.html (rev 0) +++ trunk/distribution/src/site/content/examples/examples.html 2007-06-20 16:23:17 UTC (rev 173) @@ -0,0 +1,15 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html> + <head> + <title>Waffle Example Projects</title> + </head> + <body class="composite"> + <div id="bodyColumn"> + <div id="contentBox"> + <div class="section"><h2>We have three examples:</h2><div class="section"><h3>Simple</h3><p>Source: <a href="" example has four built in mini-apps:</p><p>People management (a list of people you can add to, view, edit etc) Ajax Automobile Calulator</p><p>Waffle, for this example, uses a 'pragma' style of method encoding (the way web methods are mapped to Java ones).</p></div><div class="section"><h3>Paranamer</h3><p>Source: <a href="" example has four built in mini-apps:</p><p>People management (a list of people you can add to, view, edit etc) Ajax Automobile Calulator</p><p>Waffle, for this example, uses a 'Paranamer' for method encoding, resulting in smaller URLs, and more 'convention-based' design</p></div><div class="section"><h3>Paranamer + FreeMarker + Sitemesh</h3><p>Source: <a href="" only contains the People app that the Paranamer example above had.</p><p>It renders the page with <a href="" rather than JSP.</p><p>This allows for us to edit the pages in Adobe's Dreamweaver without additional plugins in a WYSIWYG way.</p><p>It also decorates everything with <a href="" though (0 lines of additional Java)</p><p>This allows us to separate the site's styling and navigation from content.</p></div></div> + </div> + </div> + + </body> + +</html>
Deleted: trunk/distribution/src/site/content/examples/index.html (172 => 173)
--- trunk/distribution/src/site/content/examples/index.html 2007-06-20 16:03:54 UTC (rev 172) +++ trunk/distribution/src/site/content/examples/index.html 2007-06-20 16:23:17 UTC (rev 173) @@ -1,15 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> - <head> - <title>Waffle Example Projects</title> - </head> - <body class="composite"> - <div id="bodyColumn"> - <div id="contentBox"> - <div class="section"><h2>We have three examples:</h2><div class="section"><h3>Simple</h3><p>Source: <a href="" example has four built in mini-apps:</p><p>People management (a list of people you can add to, view, edit etc) Ajax Automobile Calulator</p><p>Waffle, for this example, uses a 'pragma' style of method encoding (the way web methods are mapped to Java ones).</p></div><div class="section"><h3>Paranamer</h3><p>Source: <a href="" example has four built in mini-apps:</p><p>People management (a list of people you can add to, view, edit etc) Ajax Automobile Calulator</p><p>Waffle, for this example, uses a 'Paranamer' for method encoding, resulting in smaller URLs, and more 'convention-based' design</p></div><div class="section"><h3>Paranamer + FreeMarker + Sitemesh</h3><p>Source: <a href="" only contains the People app that the Paranamer example above had.</p><p>It renders the page with <a href="" rather than JSP.</p><p>This allows for us to edit the pages in Adobe's Dreamweaver without additional plugins in a WYSIWYG way.</p><p>It also decorates everything with <a href="" though (0 lines of additional Java)</p><p>This allows us to separate the site's styling and navigation from content.</p></div></div> - </div> - </div> - - </body> - -</html>
Modified: trunk/distribution/src/site/content/index.html (172 => 173)
--- trunk/distribution/src/site/content/index.html 2007-06-20 16:03:54 UTC (rev 172) +++ trunk/distribution/src/site/content/index.html 2007-06-20 16:23:17 UTC (rev 173) @@ -8,7 +8,13 @@ <body class="composite"> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2>Waffle Web Framework</h2><p>Waffle is a Java web framework that makes the process of developing Java based web applications easier. It was built to support enterprise level web-based business applications.</p><img src="" /><p>Waffle is different than the multitude of web frameworks that exist today.</p><ul><li>it does <b>NOT</b> have any proprietary XML configuration files</li><li>it does <b>NOT</b> have a steep learning curve</li><li>it does <b>NOT</b> have a proprietary UI templating language</li><li>easily maps an http request directly to any Java classes method</li></ul><p>Application built upon Waffle only need to be aware of three things:</p><ol type="1"><li><b>Controllers</b> - an controller in Waffle does <b>not</b> need to extend or implement any specific class or interface because <b>a controller is simply a plain old Java object (Pojo)</b>.</li><li><b>ActionMethod</b> - in Waffle <b>an ActionMethod is simply a method defined in your Controller class</b>. Any method can be used regardless of its signature or return type. Waffle will react differently depending on what is returned from the ActionMethod so take a look at this section for further details.</li><li><b>Registrar</b> - the Registrar is where you go to register the <i>Controllers</i>, and other common components, your application is dependent on. Typically most web frameworks require your applications to create special XML file(s) for this, but <b>with Waffle you'll spend less time playing with XML and more time building business value.</b></li></ol><div class="section"><h3>Getting started</h3><p>The best way to get started is to look at the examples</p><ul><li><a href="" Hello World</a></li><li><a href="" Simple Calculator</a></li></ul></div></div> + <div class="section"><h2>Waffle Web Framework</h2> + +<p>Waffle is a Java web framework that makes the process of developing Java based web applications easier. It was built to support enterprise level web-based business applications.</p> + +<p>Waffle is different than the multitude of web frameworks that exist today.</p><ul><li>it does <b>NOT</b> have any proprietary XML configuration files</li><li>it does <b>NOT</b> have a steep learning curve</li><li>it does <b>NOT</b> have a proprietary UI templating language</li><li>easily maps an http request directly to any Java classes method</li></ul> + +<p>Application built upon Waffle only need to be aware of three things:</p><ol type="1"><li><b>Controllers</b> - an controller in Waffle does <b>not</b> need to extend or implement any specific class or interface because <b>a controller is simply a plain old Java object (Pojo)</b>.</li><li><b>ActionMethod</b> - in Waffle <b>an ActionMethod is simply a method defined in your Controller class</b>. Any method can be used regardless of its signature or return type. Waffle will react differently depending on what is returned from the ActionMethod so take a look at this section for further details.</li><li><b>Registrar</b> - the Registrar is where you go to register the <i>Controllers</i>, and other common components, your application is dependent on. Typically most web frameworks require your applications to create special XML file(s) for this, but <b>with Waffle you'll spend less time playing with XML and more time building business value.</b></li></ol><div class="section"><h3>Getting started</h3><p>The best way to get started is to look at the examples</p><ul><li><a href="" Hello World</a></li><li><a href="" Simple Calculator</a></li></ul></div></div> </div> </div> <div class="clear">
Modified: trunk/distribution/src/site/content/sitemap.xml (172 => 173)
--- trunk/distribution/src/site/content/sitemap.xml 2007-06-20 16:03:54 UTC (rev 172) +++ trunk/distribution/src/site/content/sitemap.xml 2007-06-20 16:23:17 UTC (rev 173) @@ -29,7 +29,7 @@ </section> <section> <name>Taglib</name> - <page>taglib/index.html</page> + <page>taglib/taglib.html</page> <page>taglib/button.html</page> <page>taglib/text.html</page> <page>taglib/submit.html</page> @@ -38,7 +38,7 @@ </section> <section> <name>Examples</name> - <page>examples/index.html</page> + <page>examples/examples.html</page> <page>examples/helloworld.html</page> <page>examples/simple-calculator.html</page> </section>
Deleted: trunk/distribution/src/site/content/taglib/index.html (172 => 173)
--- trunk/distribution/src/site/content/taglib/index.html 2007-06-20 16:03:54 UTC (rev 172) +++ trunk/distribution/src/site/content/taglib/index.html 2007-06-20 16:23:17 UTC (rev 173) @@ -1,32 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> - <head> - <title>Waffle Taglib</title> - </head> - <body class="composite"> - <div id="bodyColumn"> - <div id="contentBox"> - <div class="section"><h2>Introduction</h2><p>Waffle taglib is a sample library which aimed at making it easier to create custom forms using the JSP technology. The most important step it to declare the taglib itself in your jsp file:</p><div class="source"><pre><%@ taglib uri="http://waffle.codehaus.org" prefix="w" %></pre></div></div><div class="section"><h2>Basic usage</h2><p>The following example shows how to create a form inside a table, containing many different fields:</p><div class="source"><pre><w:form action="" type="table" id="sendForm"> - <w:hidden name="supplier.id"/> - <w:text name="supplier.code"/> - <w:text name="supplier.name"/> - <w:text name="supplier.phone"/> - <w:textarea name="supplier.details" cols="60" rows="7">${supplier.details}</w:textarea> - <w:submit value="send"/> -</w:form></pre></div><p>Due to internationalization issues, you should add the following items to your messages.properties file: <i>supplier.name</i>, <i>supplier.code</i>, <i>supplier.phone</i>, <i>supplier.details</i> and <i>send</i>.</p><div class="source"><pre>supplier.name = Name -supplier.code = Code -supplier.phone = Phone -supplier.details = Details -send = send</pre></div></div><div class="section"><h2>Login form example</h2><p>The following example shows a sample login form:</p><div class="source"><pre><w:form action="" type="table" id="login"> - <w:text name="username"/> - <w:password name="password"/> - <w:submit value="login"/> -</w:form></pre></div><p>Once again, due to internationalization issues, you should register add the following items to your messages.properties file: <i>username</i>, <i>password</i> and <i>login</i>.</p><div class="source"><pre>username = Username -password = Password -login = Login</pre></div></div> - </div> - </div> - - </body> - -</html>
Copied: trunk/distribution/src/site/content/taglib/taglib.html (from rev 171, trunk/distribution/src/site/content/taglib/index.html) (0 => 173)
--- trunk/distribution/src/site/content/taglib/taglib.html (rev 0) +++ trunk/distribution/src/site/content/taglib/taglib.html 2007-06-20 16:23:17 UTC (rev 173) @@ -0,0 +1,32 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html> + <head> + <title>Waffle Taglib</title> + </head> + <body class="composite"> + <div id="bodyColumn"> + <div id="contentBox"> + <div class="section"><h2>Introduction</h2><p>Waffle taglib is a sample library which aimed at making it easier to create custom forms using the JSP technology. The most important step it to declare the taglib itself in your jsp file:</p><div class="source"><pre><%@ taglib uri="http://waffle.codehaus.org" prefix="w" %></pre></div></div><div class="section"><h2>Basic usage</h2><p>The following example shows how to create a form inside a table, containing many different fields:</p><div class="source"><pre><w:form action="" type="table" id="sendForm"> + <w:hidden name="supplier.id"/> + <w:text name="supplier.code"/> + <w:text name="supplier.name"/> + <w:text name="supplier.phone"/> + <w:textarea name="supplier.details" cols="60" rows="7">${supplier.details}</w:textarea> + <w:submit value="send"/> +</w:form></pre></div><p>Due to internationalization issues, you should add the following items to your messages.properties file: <i>supplier.name</i>, <i>supplier.code</i>, <i>supplier.phone</i>, <i>supplier.details</i> and <i>send</i>.</p><div class="source"><pre>supplier.name = Name +supplier.code = Code +supplier.phone = Phone +supplier.details = Details +send = send</pre></div></div><div class="section"><h2>Login form example</h2><p>The following example shows a sample login form:</p><div class="source"><pre><w:form action="" type="table" id="login"> + <w:text name="username"/> + <w:password name="password"/> + <w:submit value="login"/> +</w:form></pre></div><p>Once again, due to internationalization issues, you should register add the following items to your messages.properties file: <i>username</i>, <i>password</i> and <i>login</i>.</p><div class="source"><pre>username = Username +password = Password +login = Login</pre></div></div> + </div> + </div> + + </body> + +</html>
To unsubscribe from this list please visit:
