You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/03/13 16:59:09 UTC

[jira] Updated: (TAPESTRY-1276) If component should include an optional negate parameter

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

Howard M. Lewis Ship updated TAPESTRY-1276:
-------------------------------------------

    Fix Version/s:     (was: 5.0)
         Assignee: Howard M. Lewis Ship
      Description: It would be useful for the If component to take an optional negate parameter, much like the WOCondition component in WebObjects.  This would allow the component content to be rendered if the associated condition is FALSE instead of TRUE, therefore eliminating the need to write an additional Java method to perform this negate operation.  (was: It would be useful for the 'If' component to take an optional 'negate' parameter, much like the WOCondition component in WebObjects.  This would allow the component content to be rendered if the associated condition is FALSE instead of TRUE, therefore eliminating the need to write an additional Java method to perform this negate operation.)
          Summary: If component should include an optional negate parameter  (was: IF component should include an optional 'negate' parameter)

> If component should include an optional negate parameter
> --------------------------------------------------------
>
>                 Key: TAPESTRY-1276
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1276
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0
>         Environment: MacOS X 10.4.8, Eclipse 3.2.1
>            Reporter: Randy Leonard
>         Assigned To: Howard M. Lewis Ship
>            Priority: Minor
>
> It would be useful for the If component to take an optional negate parameter, much like the WOCondition component in WebObjects.  This would allow the component content to be rendered if the associated condition is FALSE instead of TRUE, therefore eliminating the need to write an additional Java method to perform this negate operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org