You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/30 13:35:07 UTC

[jira] [Updated] (TAP5-1894) Rosetta Stone

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

Jochen Kemnade updated TAP5-1894:
---------------------------------


This issue has been last updated about 1.5 years ago and has no information about the versions that are affected. That makes it hard to determine whether it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most recent development preview of Tapestry (5.4-beta-6), both of which are available from Maven Central, please update it as soon as possible, adding the respective version(s) to the issue's "Affects Version/s".

> 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 was sent by Atlassian JIRA
(v6.2#6252)