You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Andy Blower (JIRA)" <ji...@apache.org> on 2009/04/16 20:38:15 UTC
[jira] Created: (TAP5-651) Documentation for if component needs
expanding
Documentation for if component needs expanding
----------------------------------------------
Key: TAP5-651
URL: https://issues.apache.org/jira/browse/TAP5-651
Project: Tapestry 5
Issue Type: Improvement
Components: documentation
Affects Versions: 5.1.0.4
Reporter: Andy Blower
Priority: Minor
Use of new <p:else> block in the example for the if component is confusing because there's nothing to draw an ex-5.0 developer to the addition in the container tag attributes for the parameter namespace definition. It would also be nice to explain the syntax for an else block without the new container tag attribute, if there actually is a way of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-651) If component documentation: identify the
use of the p: namespace
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-651:
--------------------------------------
Summary: If component documentation: identify the use of the p: namespace (was: Documentation for if component needs expanding)
A slippery slope ... should we add such a note everywhere? Well, If is a "workhorse" component: used early and often, so if we catch people's attention there, we probably won't have to repeat ourselves everywhere else in the documentation.
> If component documentation: identify the use of the p: namespace
> ----------------------------------------------------------------
>
> Key: TAP5-651
> URL: https://issues.apache.org/jira/browse/TAP5-651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 5.1.0.4
> Reporter: Andy Blower
> Priority: Minor
> Fix For: 5.1.0.5
>
>
> Use of new <p:else> block in the example for the if component is confusing because there's nothing to draw an ex-5.0 developer to the addition in the container tag attributes for the parameter namespace definition. It would also be nice to explain the syntax for an else block without the new container tag attribute, if there actually is a way of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-651) If component documentation: identify the
use of the p: namespace
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-651.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.5
> If component documentation: identify the use of the p: namespace
> ----------------------------------------------------------------
>
> Key: TAP5-651
> URL: https://issues.apache.org/jira/browse/TAP5-651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 5.1.0.4
> Reporter: Andy Blower
> Priority: Minor
> Fix For: 5.1.0.5
>
>
> Use of new <p:else> block in the example for the if component is confusing because there's nothing to draw an ex-5.0 developer to the addition in the container tag attributes for the parameter namespace definition. It would also be nice to explain the syntax for an else block without the new container tag attribute, if there actually is a way of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-651) If component documentation: identify the
use of the p: namespace
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-651:
--------------------------------------
Summary: If component documentation: identify the use of the p: namespace (was: Documentation for if component needs expanding)
A slippery slope ... should we add such a note everywhere? Well, If is a "workhorse" component: used early and often, so if we catch people's attention there, we probably won't have to repeat ourselves everywhere else in the documentation.
> If component documentation: identify the use of the p: namespace
> ----------------------------------------------------------------
>
> Key: TAP5-651
> URL: https://issues.apache.org/jira/browse/TAP5-651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 5.1.0.4
> Reporter: Andy Blower
> Priority: Minor
> Fix For: 5.1.0.5
>
>
> Use of new <p:else> block in the example for the if component is confusing because there's nothing to draw an ex-5.0 developer to the addition in the container tag attributes for the parameter namespace definition. It would also be nice to explain the syntax for an else block without the new container tag attribute, if there actually is a way of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-651) If component documentation: identify the
use of the p: namespace
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-651.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.5
> If component documentation: identify the use of the p: namespace
> ----------------------------------------------------------------
>
> Key: TAP5-651
> URL: https://issues.apache.org/jira/browse/TAP5-651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 5.1.0.4
> Reporter: Andy Blower
> Priority: Minor
> Fix For: 5.1.0.5
>
>
> Use of new <p:else> block in the example for the if component is confusing because there's nothing to draw an ex-5.0 developer to the addition in the container tag attributes for the parameter namespace definition. It would also be nice to explain the syntax for an else block without the new container tag attribute, if there actually is a way of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.