So you start with two files:
style.css:
BODY { background: url(dizzydots.gif); }
These start in the same folder (perhaps src/main/webapp).
Now, these two files, under the scheme you propose, end up looking
with the following URLs:
/assets/25ea1900f125e2e136d4/style.css
/assets/0aa5f29fc5f8a0150e61/dizzydots.gif
You can see how the relative url gets broken; it would have to be
url(../0aa5f29fc5f8a0150e61/dizzydots.gif).
What we may see in a later release of Tapestry is some smarts that
knows how to parse .css files and rework relative URLs. Dan Adams has
done something like this at iFactory ... part of an internal extension
that allows for CSS aggregation (as well as JavaScript aggregation).
On Wed, Sep 8, 2010 at 12:30 PM, LLTYK <ll...@mailinator.com> wrote:
>
> Does putting it in the filename instead of the "directory" also have caveats?
> --
> View this message in context:
> http://tapestry-users.832.n2.nabble.com/Versioned-assets-tp5421811p5512040.html
> Sent from the Tapestry Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
