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)" <ta...@jakarta.apache.org> on 2007/03/01 16:24:50 UTC
[jira] Created: (TAPESTRY-1311) Identify type of component via tag
element name in templates
Identify type of component via tag element name in templates
------------------------------------------------------------
Key: TAPESTRY-1311
URL: https://issues.apache.org/jira/browse/TAPESTRY-1311
Project: Tapestry
Issue Type: New Feature
Components: Core
Reporter: Howard M. Lewis Ship
Assigned To: Howard M. Lewis Ship
Fix For: 5.0
Something I've been thinking about for a while;
Instead of:
<t:comp type="foo"> ... </t:comp>
we should support:
<t:foo> .... </t:foo>
This would be more consistent between invisible instrumentation and explicit; the only difference would be that you always put the id and mixins attributes into the t: namespace.
The remaining question is how to handle slashes in component types (i.e., a type of 'ajax/whizzbang'). I hate to say it, but we may need to allow periods in the name (i.e., <t:ajax.whizzbang> convert the periods to slashes to form the component type, then (in existing code) back to periods to form part of the qualified class name.
<span t:type="..."> (i.e., invisible instrumentation) wiil continue to be maintained.
<t:comp> should be removed; having more than two ways of doing things is not a good idea.
It's been observed that this approach would "align" Tapestry syntax more closely with other technologies, such as JSF and Cold Fusion.
--
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
[jira] Closed: (TAPESTRY-1311) Identify type of component via tag
element name in templates
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1311.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.3
... and I like it!
> Identify type of component via tag element name in templates
> ------------------------------------------------------------
>
> Key: TAPESTRY-1311
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1311
> Project: Tapestry
> Issue Type: New Feature
> Components: Core
> Affects Versions: 5.0.3
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Fix For: 5.0.3
>
>
> Something I've been thinking about for a while;
> Instead of:
> <t:comp type="foo"> ... </t:comp>
> we should support:
> <t:foo> .... </t:foo>
> This would be more consistent between invisible instrumentation and explicit; the only difference would be that you always put the id and mixins attributes into the t: namespace.
> The remaining question is how to handle slashes in component types (i.e., a type of 'ajax/whizzbang'). I hate to say it, but we may need to allow periods in the name (i.e., <t:ajax.whizzbang> convert the periods to slashes to form the component type, then (in existing code) back to periods to form part of the qualified class name.
> <span t:type="..."> (i.e., invisible instrumentation) wiil continue to be maintained.
> <t:comp> should be removed; having more than two ways of doing things is not a good idea.
> It's been observed that this approach would "align" Tapestry syntax more closely with other technologies, such as JSF and Cold Fusion.
--
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
[jira] Updated: (TAPESTRY-1311) Identify type of component via tag
element name in templates
Posted by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1311:
-------------------------------------------
Fix Version/s: (was: 5.0)
Affects Version/s: 5.0.3
> Identify type of component via tag element name in templates
> ------------------------------------------------------------
>
> Key: TAPESTRY-1311
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1311
> Project: Tapestry
> Issue Type: New Feature
> Components: Core
> Affects Versions: 5.0.3
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
>
> Something I've been thinking about for a while;
> Instead of:
> <t:comp type="foo"> ... </t:comp>
> we should support:
> <t:foo> .... </t:foo>
> This would be more consistent between invisible instrumentation and explicit; the only difference would be that you always put the id and mixins attributes into the t: namespace.
> The remaining question is how to handle slashes in component types (i.e., a type of 'ajax/whizzbang'). I hate to say it, but we may need to allow periods in the name (i.e., <t:ajax.whizzbang> convert the periods to slashes to form the component type, then (in existing code) back to periods to form part of the qualified class name.
> <span t:type="..."> (i.e., invisible instrumentation) wiil continue to be maintained.
> <t:comp> should be removed; having more than two ways of doing things is not a good idea.
> It's been observed that this approach would "align" Tapestry syntax more closely with other technologies, such as JSF and Cold Fusion.
--
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