You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Chris Mylonas (Created) (JIRA)" <ji...@apache.org> on 2012/04/03 16:40:23 UTC
[jira] [Created] (TAP5-1894) Rosetta Stone
Rosetta Stone
-------------
Key: TAP5-1894
URL: https://issues.apache.org/jira/browse/TAP5-1894
Project: Tapestry 5
Issue Type: New Feature
Components: documentation
Reporter: Chris Mylonas
Priority: Minor
There are equivalent ways for doing numerous things in Tapestry 5.
An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
For example:
1) @Property bindings within the template, or in the page's java class file.
2) contributeApplicationDefaults VS command line parameters / symbols
3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
Cheers
Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1894) Rosetta Stone
Posted by "Lance (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246172#comment-13246172 ]
Lance commented on TAP5-1894:
-----------------------------
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1894) Rosetta Stone
Posted by "Lance (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246172#comment-13246172 ]
Lance edited comment on TAP5-1894 at 4/4/12 11:13 AM:
------------------------------------------------------
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
8) Mixin vs extend component
was (Author: uklance):
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TAP5-1894) Rosetta Stone
Posted by "Lance (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246172#comment-13246172 ]
Lance edited comment on TAP5-1894 at 4/4/12 11:13 AM:
------------------------------------------------------
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
8) Mixin vs extend component
was (Author: uklance):
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1894) Rosetta Stone
Posted by "Chris Mylonas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261694#comment-13261694 ]
Chris Mylonas commented on TAP5-1894:
-------------------------------------
Component Parameters
@SupportInformalParameters on a component allows for a developer to add their own custom ones to a template for instance (class="top-layer").
A component prints the informal parameters during a render phase with resources.renderInformalParameters(writer).
A component (like Grid) can inherit parameters through the @Component annotation (it then doesn't use the renderInformalParameters() method).
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1894) Rosetta Stone
Posted by "Lance (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246172#comment-13246172 ]
Lance commented on TAP5-1894:
-----------------------------
A few more:
5) ActionLink vs EventLink
6) Annotations vs naming conventions
7) Constructor injection vs field injection
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1894) Rosetta Stone
Posted by "Chris Mylonas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261694#comment-13261694 ]
Chris Mylonas commented on TAP5-1894:
-------------------------------------
Component Parameters
@SupportInformalParameters on a component allows for a developer to add their own custom ones to a template for instance (class="top-layer").
A component prints the informal parameters during a render phase with resources.renderInformalParameters(writer).
A component (like Grid) can inherit parameters through the @Component annotation (it then doesn't use the renderInformalParameters() method).
> Rosetta Stone
> -------------
>
> Key: TAP5-1894
> URL: https://issues.apache.org/jira/browse/TAP5-1894
> Project: Tapestry 5
> Issue Type: New Feature
> Components: documentation
> Reporter: Chris Mylonas
> Priority: Minor
> Labels: documentation
>
> There are equivalent ways for doing numerous things in Tapestry 5.
> An equivalence table, or rosetta stone, or icon that links "tagged" features within the documentation would be a treat for new to intermediate developers. A double rainbow or double unicorn for giggles.
> For example:
> 1) @Property bindings within the template, or in the page's java class file.
> 2) contributeApplicationDefaults VS command line parameters / symbols
> 3) component templating (MarkupWriter element&end/writeRaw VS .tml VS streamResponse)
> 4) JS & CSS inclusions within .tml files or in java classes. Further, inclusion of contexts versus relative
> I've read the above 4 examples time and again over the last 12 months as I've part-timed my way through Tapestry deving, but it's just not that easy to find what I'm looking for in a quick enough time.
> Cheers
> Chris
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira