tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-397) Injector component, like FormInjector but for non-form related content
Date Tue, 27 May 2014 07:20:52 GMT

     [ https://issues.apache.org/jira/browse/TAP5-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jochen Kemnade updated TAP5-397:

    Labels: bulk-close-candidate  (was: tapestry5-review-for-closing)

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version
of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed
in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6,
which is available from Maven Central), please update it as soon as possible. In the case
of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org
mailing list first.

> Injector component, like FormInjector but for non-form related content
> ----------------------------------------------------------------------
>                 Key: TAP5-397
>                 URL: https://issues.apache.org/jira/browse/TAP5-397
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions:
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
> Usually we start with the general case and then add the Form-related variation; this
is the opposite.
> It would be nice to able to use content injection, much like FormInjector, but for arbitrary
parts of the page.  As with FormInjector, the triggered client-side logic would duplicate
an element, then trigger a server-side event to provide the new content ... or perhaps that
isn't quite the way, maybe collect the new content and insert it above or below the existing
element.  Anyway, this would be useful for things like "endless lists" where new content is
added as the end of the current set of data is scrolled into view, or many other use cases.

This message was sent by Atlassian JIRA

View raw message