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 Thu, 23 Sep 2010 07:32:34 GMT

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

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

As Thiago has said it, this should move to the dev list.

You coud rethink the example to give more details on reasons for having this.
Please think also if there is way to accomplish it without changing the tapestry core.

we can then continue the discussion, some other ideas might come up.

As long as I am commenting this, there is a change happening in tapestry that might make,
even more doable: loop components could finally give access to the current row without
a binding so problem with having variables removed by having something like this:

       <t:loop t:id="loop1" source="dbService.products.categories">
                ${comp:loop1.row.name}
        </t:loop> 
.... anway .. do post this on dev mailing list ...

And please try to implement the idea so you can see what can already be done,
and what must be changed in T5. If you come up with a problem there, and request 
a change regarding this concept, some people might have ideas also how to do it
without changing the core.




> 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