age-
From: Geoff Callender [mailto:[EMAIL PROTECTED]
Sent: 19 June 2008 22:43
To: Tapestry users
Subject: Re: Putting templates together with the java
Yeah I assumed we're doing it for the web designers, too, which is a
good reason. But perhaps the better alternative is simply to filter
out the
#x27;s not very useful until this is fixed.
> -Original Message-
> From: Geoff Callender [mailto:[EMAIL PROTECTED]
> Sent: 19 June 2008 22:43
> To: Tapestry users
> Subject: Re: Putting templates together with the java
>
> Yeah I assumed we're doing it for the web desig
ctrl + shift + R and Loom are good workarounds, but I guess I'm asking
why we need workarounds at all?
The maven folder structure is good, tried and trusted for action-
oriented frameworks - it makes sense for them because the relationship
between the views and the action handlers is very mi
Yeah I assumed we're doing it for the web designers, too, which is a
good reason. But perhaps the better alternative is simply to filter
out the java files as we copy the project to them?
On 20/06/2008, at 12:27 AM, Blower, Andy wrote:
I've always assumed (apart from being more correct in s
Are you using eclipse? ctrl + shift + R is great (use * as wildcard)
Or you can use this plugin http://code.google.com/p/loom-t5/
Otherwise you can bundle your source anyhow you like, as long as your build
makes the war correctly at the end of the day. The maven folder structure is
only a (good, tr
I've always assumed (apart from being more correct in some vague way) that the
main practical reason is to keep the web designers away from Java code - so
they only see the templates, properties, javascript & css.
Pure assumption on my part though.
> -Original Message-
> From: Geoff Ca
