On 13.10.2011 10:34, Toby O'Rourke wrote:
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?
Isn't this discussion about dynamic generated CSS?
For static web pages it is a convention for
t 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: Re: Compiled CSS
>
&
st 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: Tap
bject: Re: Compiled CSS
Why is this needed? The file extension is not very important, but the
MIME type will be correct either way, and that should be all the
browser cares about. They'll ask for a "foo.less" file and will be
sent a stream of CSS, with a matching content-type hea
Why is this needed? The file extension is not very important, but the
MIME type will be correct either way, and that should be all the
browser cares about. They'll ask for a "foo.less" file and will be
sent a stream of CSS, with a matching content-type header.
On Wed, Oct 12, 2011 at 1:50 PM, De
If I understand it correctly, right now resources accesses with
ResourceTransformer will have same url as the source.
It would be nice to have somekind of transform resources mapping, lets say we
want to transform less file or files to css:
virtualTransformResource("/css/bootstrap.css", "/less/
Just checked in some changes as discussed below; not in a preview release yet.
On Mon, Oct 10, 2011 at 2:01 PM, Thiago H. de Paula Figueiredo
wrote:
> On Mon, 10 Oct 2011 17:50:12 -0300, Cezary Biernacki
> wrote:
>
>> Hi,
>
> Hi!
>
>> I like that proposition. Is it possible to change ResourceTra
Hi,
I like that proposition. Is it possible to change ResourceTransformer and
include ResourceDependencies in Tapestry 5.3.* ?
Best regards,
Cezary
On Sat, Oct 8, 2011 at 12:35 AM, Howard Lewis Ship wrote:
> True; so we need the Resource passed in, but also another object to
> collect additio
True; so we need the Resource passed in, but also another object to
collect additional dependencies, to trigger reloads. Say:
public interface ResourceTransformer
{
/**
* Read the source input stream and provide a new input stream of
the transformed content.
*
* @param source
On Fri, Oct 7, 2011 at 5:17 PM, Howard Lewis Ship wrote:
> On Thu, Oct 6, 2011 at 11:23 AM, Cezary Biernacki
> wrote:
> > Hi,
> > OK. I need to get a permission as code is owned by my employer, hopefully
> I
> > should be able to get it next week. Anyway, it is easy to build such
> > integration
On Thu, Oct 6, 2011 at 11:23 AM, Cezary Biernacki wrote:
> Hi,
> OK. I need to get a permission as code is owned by my employer, hopefully I
> should be able to get it next week. Anyway, it is easy to build such
> integration with Tapestry 5.3 by implementing ResourceTransformer interface
> and co
Hi,
OK. I need to get a permission as code is owned by my employer, hopefully I
should be able to get it next week. Anyway, it is easy to build such
integration with Tapestry 5.3 by implementing ResourceTransformer interface
and contributing it StreamableResourceSource.
For both CoffeeScript and L
Me too! I just started playing with LessCSS tis week and it seems really
interesting.
Rado
On Thu, Oct 6, 2011 at 2:03 PM, Toby O'Rourke wrote:
> 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
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
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 ResourceTransformer-s) from 5.3 and the integration should be
compatible with Tapestry 5.3. I can open source it if there is enough
interest.
On 06.10.2011 00:58, Howard Lewis Ship wrote:
> No progress yet ... it was more important to get 5.3 out than to add
> this feature. I expect to add it in Tapestry 5.4.
I hope it will be an optional feature. The lesscss-site looks very ugly
with JavaScript disabled.
- Stephan
signature.asc
D
No progress yet ... it was more important to get 5.3 out than to add
this feature. I expect to add it in Tapestry 5.4.
On Wed, Oct 5, 2011 at 2:55 PM, Toby O'Rourke
wrote:
> 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,
>
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.1045711.n5.nabble.com/Alternate-template-format-td4639774.html#a46410
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.1045711.n5.nabble.com/Alternate-template-format-td4639774.html#a4641048
>
> Has there been any progress on that yet? It is something t
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
20 matches
Mail list logo
