Hi,
I write as a heavy liquibase user - we've got about 15 projects here that are
all using liquibase with the maven plugin.
One of the great things vs. flyaway is the abstraction provided by the xml
changesets - you are hiding away from the vendor specific SQL that always seems
to crop up a
I guess it is just a consistency thing. Convention dictates that CSS files are
served with the .css extension, why break that convention if we don't have to?
From: Howard Lewis Ship [hls...@gmail.com]
Sent: 12 October 2011 22:08
To: Tapestry users
Subject:
Wow! I'd certainly be interested to see what you've done
Thanks,
Toby.
On 06/10/2011 12:54, "Cezary Biernacki" wrote:
>Hi,
>I have implemented integration LessCSS and CoffeeScript compilers with
>Tapestry 5.2. Actually most of it was porting necessary features (i.e.
>support of ResourceTransfo
On 5 Oct 2011, at 14:55, "Jérôme BERNARD" wrote:
> On Wed, Oct 5, 2011 at 15:33, Toby O'Rourke wrote:
>
>> Hi,
>>
>> Some time ago there was talk of introducing support for WRO4J, SASS or
>> LessCSS
>>
>>
>> http://tapestry
Hi,
Some time ago there was talk of introducing support for WRO4J, SASS or LessCSS
http://tapestry.1045711.n5.nabble.com/Alternate-template-format-td4639774.html#a4641048
Has there been any progress on that yet? It is something that we've started
discussing at work, perhaps we could discuss the
Hi,
We have 4 teams of 6-8 people each working on a pretty large Tapestry
project. We've encountered quite a few of these problems along the way ;)
I have to agree with Peter, well separated, testable code will make your
life immeasurably easier - get this bit right and everything else should
flo
