[
https://issues.apache.org/jira/browse/TAPESTRY-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563418#action_12563418
]
Adam Ayres commented on TAPESTRY-2098:
--------------------------------------
Please consider the following when evaluating this issue:
* [JS Libraries load slower when packed + gzip then just gzip
alone|http://jst.pbwiki.com/summary.php]
* [Packing JavaScript might be a security
thread|http://www.secureworks.com/research/threats/thepacker/]
My preference would be to see something native to Tapestry that had the ability
to combine and minify the JS assets (I believe this has been discussed in the
past). Combining can be tricky since there are JS assets that might be
considered "core" and included on every page (such as the third party libs or
common internal libs). Then there are page specific JS assets which would be
nice if they were combined separately from the "core" libs (for client caching
purposes). Having control over where the combined JS file is included is also
important (in the head vs right before the script block and closing body tag).
Just my two cents, keep up the great work Howard!
> Pack javascript (prototype, scriptaculo etc.)
> ---------------------------------------------
>
> Key: TAPESTRY-2098
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2098
> Project: Tapestry
> Issue Type: Wish
> Components: tapestry-core
> Affects Versions: 5.0.10
> Reporter: Alexey Pomogaev
> Fix For: 5.0.10
>
>
> Current JavaScript: prototype.js, sriptaculo.js etc. in tapestry resources
> not packed. Please pack this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
