- Revision
- 202
- Author
- mauro
- Date
- 2007-06-30 06:52:54 -0500 (Sat, 30 Jun 2007)
Log Message
Changed link colour to 666699 - which is similar to 666d80 but is recognized by browser. Fixed typo and removed link from logo.
Modified Paths
Diff
Modified: trunk/distribution/src/site/content/why.html (201 => 202)
--- trunk/distribution/src/site/content/why.html 2007-06-30 11:16:48 UTC (rev 201) +++ trunk/distribution/src/site/content/why.html 2007-06-30 11:52:54 UTC (rev 202) @@ -1,12 +1,63 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> - <head> - <title>Why Waffle</title> - </head> - <body> - - - <h2>So why another new web framework?</h2><p>Waffle is built upon the following:</p><ul><li>Simplicity</li><li>Convention based approach (like Ruby on Rails)</li><li>Components following Dependency Injection (DI) pattern</li><li>No singletons</li><li>No mandatory dependency on XML (and NOT annotation heavy)</li><li>Java 5 and above</li><li>Pluggable design for Waffle itself</li><li>AJAX Ready</li></ul><h3>What is meant by "Convention based"?</h3><p>A convention based approach allows for a simpler design and less architectural overhead. As an example think about how unit tests are developed with JUnit. By convention any Class postfixed with "Test" or "TestCase" is considered a unit test. Each method within that test class prefixed with "test" will be executed.</p><p>So in the Waffle world, conventions are used for tying web forms and actions to methods in Java classes.</p></div><h3>What's so great about Dependency Injection (DI)?</h3><p>Developing application with a focus on componentization allows for very flexible and testable architectures. The problem is that the J2EE servlet specification does not allow applications to be easily architected with DI in mind. Hopefully you'll see that Waffle allows you to develop an application in a cleaner way while still being J2EE compliant.</p><p>To read more about DI - see <a href="" is wrong with XML?</h3><p>To quote Paul Hammant "angle brackets hurt my eyes". Honestly, XML is great and serves a purpose but who wants to spend their days dealing with it. Configuration XML files for most web frameworks have a tendency to be verbose and error prone. The only XML required by Waffle is the standard <b>web.xml</b>, and even that is cut to a minima.</p><p>There is nothing to stop a Waffle application from using its own XML for configuration, but Waffle itself is going to leave that to the application developer rather than force an implementaion on them.</p></div><h3>Why is it called Waffle?</h3><p>It stands for Web Application Framework For Lightweight Extendible Components. Yes, we know that WAFFLEC, so lets say you're supposed to say "Waffle Components". Yes, we know that sounds a bit contrived, but the truth is we had Waffle first, then we tried to fit something meaningful to it. We know waffle in British English means "long winded" or "overly chatty", but we're preferring to ignore that. No we won't rename it. Sorry, we're kinda fond of it now.</p></div> - </body> +<head> +<title>Why Waffle</title> +</head> +<body> + +<h2>So why another new web framework?</h2> +<p>Waffle is built upon the following:</p> +<ul> + <li>Simplicity</li> + <li>Convention based approach (like Ruby on Rails)</li> + <li>Components following Dependency Injection (DI) pattern</li> + <li>No singletons</li> + <li>No mandatory dependency on XML (and NOT annotation heavy)</li> + <li>Java 5 and above</li> + <li>Pluggable design for Waffle itself</li> + <li>AJAX Ready</li> +</ul> +<h3>What is meant by "Convention based"?</h3> +<p>A convention based approach allows for a simpler design and less +architectural overhead. As an example think about how unit tests are +developed with JUnit. By convention any Class postfixed with +"Test" or "TestCase" is considered a unit test. Each +method within that test class prefixed with "test" will be +executed.</p> +<p>So in the Waffle world, conventions are used for tying web forms +and actions to methods in Java classes.</p> +</div> +<h3>What's so great about Dependency Injection (DI)?</h3> +<p>Developing application with a focus on componentization allows +for very flexible and testable architectures. The problem is that the +J2EE servlet specification does not allow applications to be easily +architected with DI in mind. Hopefully you'll see that Waffle allows you +to develop an application in a cleaner way while still being J2EE +compliant.</p> +<p>To read more about DI - see <a + href="" +</div> +<h3>What is wrong with XML?</h3> +<p>To quote Paul Hammant "angle brackets hurt my eyes". +Honestly, XML is great and serves a purpose but who wants to spend their +days dealing with it. Configuration XML files for most web frameworks +have a tendency to be verbose and error prone. The only XML required by +Waffle is the standard <b>web.xml</b>, and even that is cut to a minima.</p> +<p>There is nothing to stop a Waffle application from using its own +XML for configuration, but Waffle itself is going to leave that to the +application developer rather than force an implementation on them.</p> +</div> +<h3>Why is it called Waffle?</h3> +<p>It stands for Web Application Framework For Lightweight +Extendible Components. Yes, we know that WAFFLEC, so lets say you're +supposed to say "Waffle Components". Yes, we know that sounds +a bit contrived, but the truth is we had Waffle first, then we tried to +fit something meaningful to it. We know waffle in British English means +"long winded" or "overly chatty", but we're +preferring to ignore that. No we won't rename it. Sorry, we're kinda +fond of it now.</p> +</div> +</body> + </html>
Modified: trunk/distribution/src/site/resources/style/waffle.css (201 => 202)
--- trunk/distribution/src/site/resources/style/waffle.css 2007-06-30 11:16:48 UTC (rev 201) +++ trunk/distribution/src/site/resources/style/waffle.css 2007-06-30 11:52:54 UTC (rev 202) @@ -24,7 +24,7 @@ font-size: 10pt; border-bottom: 1px solid #aaaaaa; padding-top: 12px; - color: #000; + color: #66665c; } #footer { @@ -89,11 +89,11 @@ } a:link { - color: #666d80; + color: #666699; } a:visited { - color: #66665c; + color: #666699; } a:active,a:hover {
Modified: trunk/distribution/src/site/templates/skin.html (201 => 202)
--- trunk/distribution/src/site/templates/skin.html 2007-06-30 11:16:48 UTC (rev 201) +++ trunk/distribution/src/site/templates/skin.html 2007-06-30 11:52:54 UTC (rev 202) @@ -30,13 +30,13 @@ <body class="composite"> <div id="banner"> - <img src="" alt="Waffle" src="" + <img src="" alt="Waffle" /> <div class="clear"> <hr/> </div> </div> <div id="breadcrumbs"> - <div class="left"> Last Published: 06/21/2007 </div> + <div class="left"> Last Published: 01/07/2007 </div> <div class="clear"> <hr/> </div>
To unsubscribe from this list please visit:
