Hi Thiago,
Yes, of course. I will share the solution, but I have one more withstanding
problem.
In my compiled CSS the image paths are wrong.
In my less file the images are referenced with relative path, like
@product: url(../images/product.svg);
and should be (in the compiled CSS) like:-
@product: url(/appContext/assets/ctx/6787fbc2/images/product.svg);
For compiling the less file to CSS I am doing the following things:-
LessResourceTransformer lessResourceTransformer = new
LessResourceTransformer();
return
lessResourceTransformer.transform(lessFile.getResource(),
new ResourceChangeTrackerImpl(new
ClasspathURLConverterImpl(),false));
}
The ResourceChangeTrackerImpl class is responsible for loading and tracking
the assets(images). In the normal flow, this class is injected much before
the Less Compiler is called.
I can figure out the problem that, in the tapestry way of compilation the
images are loaded as an assets and tapestry gives the assets the specific
URLs (as mentioned above) . Since in my case I am using the Less Compiler
directly, the compiled CSS instead points to the relative path url
(../images/product.svg).
Any suggestions for this?
Regards
Akshay
On Wed, Oct 1, 2014 at 4:24 PM, Thiago H de Paula Figueiredo <
[email protected]> wrote:
> On Wed, 01 Oct 2014 11:08:35 -0300, akshay <[email protected]>
> wrote:
>
> Hi Thiago,
>>
>
> Hello, Akshay!
>
> Your idea works.Great!!
>> Thanks a lot!!!
>>
>
> Yay! :)
>
> Is it possible for you to share the solution, so other people with similar
> needs can benefit from it?
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Cheers!!
Akshay