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

Kalle Korhonen resolved TAP5-1987.
----------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.4
         Assignee: Kalle Korhonen

>From 5.4 ComponentParameterConstants:
     * @deprecated Deprecated in 5.4 with no replacement.
     */
    public static final String ZONE_SHOW_METHOD = 
"tapestry.components.zone_show_method";

    /**
     * The default name of a JS function attached to Tapestry.ElementEffect 
object to point out an
     * update on a {@link org.apache.tapestry5.corelib.components.Zone}.
     * Defaults to "highlight"
     *
     * @deprecated Deprecated in 5.4 with no replacement.
     */
    public static final String ZONE_UPDATE_METHOD = 
"tapestry.components.zone_update_method";

i.e. the comparable component specific effect symbols are deprecated in 5.4 
without replacements so putting this in would go against the grain. I'm not 
sure what Howard's thinking with deprecation was but to me, a symbol in 
principle seems like too heavyweight a mechanism to configure component 
defaults. Argue hard on the dev list if you want this reopened and committed.
                
> ProgressiveDisplay update parameter as a symbol
> -----------------------------------------------
>
>                 Key: TAP5-1987
>                 URL: https://issues.apache.org/jira/browse/TAP5-1987
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.3.4
>            Reporter: Dusko Jovanovski
>            Assignee: Kalle Korhonen
>            Priority: Minor
>             Fix For: 5.4
>
>         Attachments: 
> Added-Symbol-for-default-ProgressiveDisplay-zone-upd.patch
>
>
> ProgressiveDisplay update parameter as a symbol
> Could be a new symbol, or the same one used for the Zone component.

--
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

Reply via email to