Tapestry 5
  1. Tapestry 5
  2. TAP5-1570

Zone elements in the client should trigger events so that the application can react to changes

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0, 5.1, 5.0.16
    • Fix Version/s: 5.4
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      It seems that time and time again for each T5 project (6 out of 7 so far) I find I need to override tapesty.js methods to add additional support for zones. Currently there is only 1 event fired from a zone (Tapestry.ZONE_UPDATED_EVENT), I'd like to suggest/request there be at least 4 events total (3 new ones):

      1) ZONE_BEFORE_AJAX_REQUEST_EVENT: This would be fired before the ajax request is sent to the server. Listeners should be able to cancel the ajax request (similiar to the way tapestry allows a form submission to be canceled)

      2) ZONE_BEFORE_UPDATE_EVENT: This would be fired after the ajax request returns and just before the zone is updated via the processReply() method. Again, listeners should be able to cancel the update.

      3) ZONE_UPDATED_EVENT: already and is listed here for completeness.

      4) ZONE_AJAX_REQUEST_ERROR_EVENT: This would be fired if the ajax request errored out for the zone. (includes error data)

      references to mailing list: http://tapestry.1045711.n5.nabble.com/More-javscript-zone-events-please-td4401005.html

        Issue Links

          Activity

          Hide
          Robert Zeigler added a comment -

          This isn't really a bug. It's not that Tapestry isn't working correctly, it's that you'd like to see the existing functionality expanded, so this is an improvement.

          Show
          Robert Zeigler added a comment - This isn't really a bug. It's not that Tapestry isn't working correctly, it's that you'd like to see the existing functionality expanded, so this is an improvement.
          Hide
          Howard M. Lewis Ship added a comment -

          Tapestry 5.4 now defines a number of events to force a zone to update, or to be informed of its progress.

          Show
          Howard M. Lewis Ship added a comment - Tapestry 5.4 now defines a number of events to force a zone to update, or to be informed of its progress.

            People

            • Assignee:
              Howard M. Lewis Ship
              Reporter:
              Joe Klecko
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development