tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Hrg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-1281) Simplifications for lightweight Tapestry5 projects
Date Wed, 22 Sep 2010 20:26:33 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913761#action_12913761
] 

Davor Hrg commented on TAP5-1281:
---------------------------------

the example you mentioned
       <t:loop source="dbService.products.categories" value="category">
                ${category.name}
        </t:loop> 

would look like this with the new prefix:
       <t:loop source="dbService:products.categories" value="category">
                ${category.name}
        </t:loop> 

dot would change between dbService.products to colon dbService:products
...there are other issues to overcome if you choose to try this path....

... all is fine if you are trying to push the envelope with tapestry ...
but this proposal smells to me just like bad application design...

Having everything in a single class is BAD (with capital letters).
You are gaining nothing with it, and will have a huge complicated class.



> Simplifications for lightweight Tapestry5 projects
> --------------------------------------------------
>
>                 Key: TAP5-1281
>                 URL: https://issues.apache.org/jira/browse/TAP5-1281
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0.15
>            Reporter: Tobias Marx
>            Priority: Minor
>
> In order to simplify Tapestry5 even further i would like to suggest the following:
> - auto-creation of "empty" page and component classes if they don't exist at runtime
(to reduce number of lines of code, especially for small projects & demos)
> - being able to reference a "global" service by default from within the templates where
all database queries / persistence queries can be placed
> This way, you could create quite complex web applications with only a few files:
> - a layout templates
> -  x template files for all pages (instead of 2*x)
> -  y template files for all components (instead of 2*y)
> - one "global" service as an additional file that contains all hibernate/persistance
queries
> This would cater of all users that want to create lightweight websites with only as many
lines of code/files as really needed. 
> A lot of website can be implemented just by querying data  and displaying them in a template
(loop)
> The idea:
> - reduce the lines of code for small / medium projects
> - create even more convincing Tapestry demos (vs. RoR/PHP)
> - increase acceptance by more users checking Tapestry out for the first time

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


Mime
View raw message