click-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sa...@apache.org
Subject svn commit: r978981 - in /click/trunk/click/documentation/docs: roadmap-changes.html upgrade-path.html
Date Sun, 25 Jul 2010 04:36:53 GMT
Author: sabob
Date: Sun Jul 25 04:36:53 2010
New Revision: 978981

URL: http://svn.apache.org/viewvc?rev=978981&view=rev
Log:
roadmap

Modified:
    click/trunk/click/documentation/docs/roadmap-changes.html
    click/trunk/click/documentation/docs/upgrade-path.html

Modified: click/trunk/click/documentation/docs/roadmap-changes.html
URL: http://svn.apache.org/viewvc/click/trunk/click/documentation/docs/roadmap-changes.html?rev=978981&r1=978980&r2=978981&view=diff
==============================================================================
--- click/trunk/click/documentation/docs/roadmap-changes.html (original)
+++ click/trunk/click/documentation/docs/roadmap-changes.html Sun Jul 25 04:36:53 2010
@@ -85,6 +85,39 @@ service.
       when upgrading from previous releases.
       </div>
       <div style="margin-left: -2em; margin-top: 1.5em; margin-bottom: 1em;">
+        <b>Deprecated:</b>
+      </div>
+      <ul style="padding: 0em; margin-left:0em;margin-bottom: 2em">
+        <li class="change">
+          Deprecated stateful page support: <a href="click-api/org/apache/click/Page.html#setStateful(boolean)">Page.setStateful()</a>.
+          <p/>
+          Stateful pages had the following issues:
+          <ul>
+            <li>
+            Stateful pages was introduced to make it easier to store page state across
+            multiple HTTP requests. However developing a stateful page is very different
+            from developing a stateless one and this lead to Click applications that are
+            inconsistent and harder to maintain.
+            </li>
+            <li>
+            In addition stateful page support has never been implemented consistently
+            across the framework and some components did not work correctly.
+            </li>
+            <li>
+            Stateful pages are very coarse grained, making it difficult to control
+            which objects are stored in the session.
+            </li>
+            <li>
+            Stateful pages have also introduced unnecessary complexity in the framework
+            itself, which can now be phased out.
+            </li>
+          </ul>
+          Unfortunately there is no direct upgrade path from a stateful page.
+          However the majority of use cases are catered for by the new stateful
+          controls: Table, Form, TabbedPanel, Field and AbstractLink.
+        </li>
+      </ul>
+      <div style="margin-left: -2em; margin-top: 1.5em; margin-bottom: 1em;">
       <b>New examples:</b>
       </div>
       <ul style="padding: 0em; margin-left:0em;margin-bottom: 2em">

Modified: click/trunk/click/documentation/docs/upgrade-path.html
URL: http://svn.apache.org/viewvc/click/trunk/click/documentation/docs/upgrade-path.html?rev=978981&r1=978980&r2=978981&view=diff
==============================================================================
--- click/trunk/click/documentation/docs/upgrade-path.html (original)
+++ click/trunk/click/documentation/docs/upgrade-path.html Sun Jul 25 04:36:53 2010
@@ -84,6 +84,34 @@ versions please email the Click user gro
   <dd>
     <ul style="padding: 0em; margin-left:0em;margin-bottom: 2em">
       <li class="change">
+          Deprecated stateful page support: <a href="click-api/org/apache/click/Page.html#setStateful(boolean)">Page.setStateful()</a>.
+          <p/>
+          Stateful pages had the following issues:
+          <ul>
+            <li>
+            Stateful pages was introduced to make it easier to store page state across
+            multiple HTTP requests. However developing a stateful page is very different
+            from developing a stateless one and this lead to Click applications that are
+            inconsistent and harder to maintain.
+            </li>
+            <li>
+            In addition stateful page support has never been implemented consistently
+            across the framework and some components did not work correctly.
+            </li>
+            <li>
+            Stateful pages are very coarse grained, making it difficult to control
+            which objects are stored in the session.
+            </li>
+            <li>
+            Stateful pages have also introduced unnecessary complexity in the framework
+            itself, which can now be phased out.
+            </li>
+          </ul>
+          Unfortunately there is no direct upgrade path from a stateful page.
+          However the majority of use cases are catered for by the new stateful
+          controls: Table, Form, TabbedPanel, Field and AbstractLink.
+      </li>
+      <li class="change">
         The DateField control now accepts month and day names spelled in the 
         locale of the browser or application (see 
         <a href="click-api/org/apache/click/Context.html#getLocale()">Context.getLocale()</a>).



Mime
View raw message