tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Long (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-73) JavaScript libraries should be automatically packed/minimalized
Date Mon, 08 Jun 2009 15:00:07 GMT

    [ https://issues.apache.org/jira/browse/TAP5-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717279#action_12717279

Joshua Long commented on TAP5-73:

You don't, in theory, need the minification after compression. The only case I can think of
otherwise are the few browsers that dont support gzip (I know JAWR mentions in its documentation
certain versions of IE6 as not supporting gzip, and thus requiring a separate non-gzipped
bundle thats made available.) 

And yes, combining/minifying CSS would be wonderful. My question is: how does Tapestry combine
and expose them as a URL? Is the URL constantly hashed? IE, if I use prototype and a calendar
javascript on 10 pages, is the url generated by Tapestry the same? What about if I use prototype,
a calendar javascript on 9 pages but on the 10th, I decide to also jQuery. Do I, on this page,
have to download prototype and the calendar widget again because the URL has changed for the
combined .js? This would defeat the purpose of the caching. In this case it would be ideal
to be able to force Tapestry to emit two script tags (yes, that implies two HTTP requests
for associated js scripts for the page, but at least the client isn't forced to download a
whole half megabyte of JavaScript per page...) 

> JavaScript libraries should be automatically packed/minimalized
> ---------------------------------------------------------------
>                 Key: TAP5-73
>                 URL: https://issues.apache.org/jira/browse/TAP5-73
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
> Tapestry should catch downloads of JavaScript libraries, and should "pack" the JavaScript
... remove comments and unecessary whitespace.  I believe Dojo has a library to do this, it
may even shorten variable names (!).
> A smart implementation of this would manage to cache the compressed JS, and notice when
the uncompressed version changed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message