Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for 
change notification.

The following page has been changed by ErikVullings:
http://wiki.apache.org/tapestry/WishList

------------------------------------------------------------------------------
   * Add support for components that use XMLHttpRequest.  XMLHttpRequest (or 
something similar) is supported by Microsoft, Mozilla, Safari, and Opera.  
Basically, Javascript can request information from the server and update a 
portion of a page rather then refreshing the whole page.  An example of a 
component that could benefit from this would be a derivative of the DatePicker 
component that could be used for scheduling appointments.  As the user selects 
a month, the "already reserved slots" could be retrieved from the server to 
update the component.  While it is not strictly necessary for Tapestry to 
govern the conversation between the component and the server, there are many 
benefits in doing so.  For example, if the client's browser does not support 
XMLHttpRequest it will be necessary to refresh the entire page, and Tapestry 
would definitely handle that task.
  
-  * Add support for DHTML components.
   * How about a Tapestry Context? I've built one for our projects, it sets the 
Visit into ThreadLocal. This way, helper classes don't have to pass around the 
Visit. The extended BasePage implements IPageListener and sets (and unsets) the 
Visit. Classes that control web flow can grab it themselves. You could also put 
HttpRequest in it for implementing Portal support (this was mentioned in HLS's 
post as problematic). Probably all of a 30 minute job.
  
  HowardLewisShip: Interesting idea, been thinking in terms of how to have many 
different ''visit''s, with varying names, scopes, lifecycles, creation 
strategies, and have ways to ''inject'' them effeciently into Tapestry pages 
and components (and perhaps even into HiveMind services).

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to