tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hls...@apache.org
Subject git commit: Minor updates to the 5.4 release notes
Date Wed, 26 Dec 2012 21:50:11 GMT
Updated Branches:
  refs/heads/master 3a7ac53ea -> dea2df879


Minor updates to the 5.4 release notes


Project: http://git-wip-us.apache.org/repos/asf/tapestry-5/repo
Commit: http://git-wip-us.apache.org/repos/asf/tapestry-5/commit/dea2df87
Tree: http://git-wip-us.apache.org/repos/asf/tapestry-5/tree/dea2df87
Diff: http://git-wip-us.apache.org/repos/asf/tapestry-5/diff/dea2df87

Branch: refs/heads/master
Commit: dea2df879241da824c25a0d678e8a12626081d3e
Parents: 3a7ac53
Author: Howard M. Lewis Ship <hlship@apache.org>
Authored: Wed Dec 26 13:50:07 2012 -0800
Committer: Howard M. Lewis Ship <hlship@apache.org>
Committed: Wed Dec 26 13:50:07 2012 -0800

----------------------------------------------------------------------
 54_RELEASE_NOTES.txt |   26 +++++++++++++++-----------
 1 files changed, 15 insertions(+), 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/tapestry-5/blob/dea2df87/54_RELEASE_NOTES.txt
----------------------------------------------------------------------
diff --git a/54_RELEASE_NOTES.txt b/54_RELEASE_NOTES.txt
index 47e4517..099155e 100644
--- a/54_RELEASE_NOTES.txt
+++ b/54_RELEASE_NOTES.txt
@@ -5,22 +5,24 @@ Scratch pad for changes destined for the 5.4 release notes page.
 A new DeprecationWarning service exists to write runtime warnings about deprecated component
parameters.
 
 There have been sweeping changes to the client-side support in JavaScript, including the
long-awaited abstraction layer.
-Tapestry is moving to the use of asynchronously-loaded modules, using the RequireJS library.
Virtually all ofTapestry's
+Tapestry is moving to the use of asynchronously-loaded modules, using the RequireJS library.
Virtually all of Tapestry's
 existing JavaScript libraries are being recoded as JavaScript modules; in 5.5, the remaining
JavaScript libraries will
 be removed.
 
-The abstraction layer is a set of wrappers that encapsulate most of the differences between
Prototype and jQuery (or
-other, more modern JavaScript foundation libraries). By coding to the abstraction layer,
it will be possible to swap
-out Prototype support for jQuery.  Prototype will no longer be bundled with Tapestry starting
in Tapestry 5.5.
+The abstraction layer, the `t5/core/dom` module, is a set of wrappers that encapsulate most
of the differences between
+Prototype and jQuery. By coding to the abstraction layer, it will be possible to swap
+out Prototype support for jQuery.  Prototype will no longer be bundled with Tapestry starting
in Tapestry 5.5. Ultimately
+it will be possible to efficiently support other foundation frameworks, such as MooTools
or ExtJS, by providing your
+own implementation of the abstraction layer.
 
-Prior releases of Tapestry would require several separate constructs to initialize client
behavior:
+Prior releases of Tapestry would require several separate constructs to initialize client-side
behavior:
 
 * A unique id, generated on the server, on a client-side element
 * A JavaScript library that extended T5.initializers with an initialization function
 * Creating a _spec_ to describe behavior, including URLs and the unique client element id
 * Many similar client-side event handlers on specific elements (created by the initialization
function)
 
-Although this was well-structured, it had pain points for developers, as well as some client-side
performance issues.
+Although this was well-structured, it had numerous pain points for developers, as well as
some client-side performance issues.
 For example, it means that components that occur many times on the page will include many
similar event handler
 functions.
 
@@ -75,7 +77,7 @@ removed with no replacement.
 ## Scriptaculous Deprecated
 
 Tapestry code no longer makes use of Scriptaculous. Instead, Tapestry will fire events on
elements, and user code may
-decide to animate them using whatever library is desired. The event names are defined in
the core/events module.
+decide to animate them using whatever library is desired. The event names are defined in
the `t5/core/events` module.
 
 ## Floating Console
 
@@ -94,13 +96,14 @@ identically to SUBMIT.
 
 ## Wait-for-page logic removed
 
-Tapestry 5.3 contained code that attempted to prevent Ajax requests until after the page
had loaded; this was based
-on the function `Tapestry.waitForPage()`.  Server components no longer make use of this function,
and the function
+Tapestry 5.3 contained client-side code that attempted to prevent Ajax requests until after
the page had loaded;
+this was based on the function `Tapestry.waitForPage()`.  Server components no longer make
use of this function, and the function
 itself now does nothing. A replacement approach to preventing the user from interacting with
links and forms before
 the page initialization has completed may be implemented in the future.
 
 However, once initial page initialization has occurred, the attribute `data-page-initialized`
on the root HTML element
-is set to "true".
+is set to "true". In many cases, automated tests should be updated to wait for this attribute
to be set after loading
+a new page.
 
 ## Twitter Bootstrap
 
@@ -135,7 +138,8 @@ still exists, but the methods do nothing, and the service and interface
will be
 In prior releases, adding _any_ JavaScript to the application would implicitly import the
`core` JavaScript stack.
 This no longer occurs; in most cases, the core stack is provided automatically by other components.
 
-You may want to consider adding `@Import(stack="core")` to your applications' main layout
component.
+You may want to consider adding `@Import(stack="core")` to your applications' main layout
component, especially
+if you want to leverage the built-in Twitter Bootstrap CSS, which is provided as part of
the core stack.
 
 ## Palette Component
 


Mime
View raw message