tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-776) Tapestry.FormFragment (client side) should be refactored to be easier to modify
Date Thu, 25 Jul 2013 21:37:49 GMT

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

Howard M. Lewis Ship closed TAP5-776.
-------------------------------------

    Resolution: Invalid

I don't believe this makes sense anymore, in the context of Tapestry 5.4.
                
> Tapestry.FormFragment (client side) should be refactored to be easier to modify
> -------------------------------------------------------------------------------
>
>                 Key: TAP5-776
>                 URL: https://issues.apache.org/jira/browse/TAP5-776
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>              Labels: bulk-close-candidate
>
> It would be nice if:
> a) The DOM element has a property pointing to the Tapestry.FormInjector object.  I.e.
$T(div).formFragment.
> b) Tapestry.FormFragment had methods for adding new content (ala FormInjector) above
or below the existing FormFragment.
> c) implicit in above: mix and match of FormInjector and FormFragment, to allow easier
ability to build AjaxFormLoop with buttons to add new rows above or below existing rows.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message