了解 Assetic 捆绑包

发布于 2024-11-27 10:40:17 字数 819 浏览 0 评论 0原文

我无法理解 Assetic 捆绑包工作方式背后的原因，不幸的是官方文档并不太详细。

我只是看不出它处理静态路径和 url 的方式有什么好处。比如说，

{{ asset("bundles/mybundle/css/main.css") }}

被翻译成“/bundles/mybundle/css/main.css”。什么，只是在它前面加一个“/”？但我可以手动完成。我期望 Django 中至少有类似 STATIC_DIR 的东西，它指定所有静态文件所在的位置并用作静态根目录。

并

{% stylesheets '@MyBundle/Resources/public/css/main.css' %}
    <link rel="stylesheet" href="{{ asset_url }}" type="text/css" media="all" />
{% endstylesheets %}

变成类似的东西

<link rel="stylesheet" href="/app_dev.php/css/618ab99_main_1.css" type="text/css" media="all" />

，但它不会为您的布局添加任何灵活性 - 当静态文件名更改时，您仍然必须编辑布局文件。而且您仍然需要手动编写 HTML“链接”标签。

考虑到您可以使用 Sf2 控制台在 web/ 目录中创建指向捆绑包公共文件夹的符号链接，我发现 Assetic 的工作方式有些晦涩难懂。我确信我错过了一些东西，所以我希望有人能为我解决这个问题。谢谢。

原文

I'm having trouble understanding the reasons behind the way Assetic bundle works, and unfortunately the official documentation isn't too verbose.

I just fail to see any good in the way it deals with static paths and urls. Say,

{{ asset("bundles/mybundle/css/main.css") }}

gets translated into "/bundles/mybundle/css/main.css". What, just prepending it with a '/'? But I can do it manually. I expected at least something like STATIC_DIR in Django which specifies the place where all your static files live and serves as a static root directory.

And

{% stylesheets '@MyBundle/Resources/public/css/main.css' %}
    <link rel="stylesheet" href="{{ asset_url }}" type="text/css" media="all" />
{% endstylesheets %}

becomes something like

<link rel="stylesheet" href="/app_dev.php/css/618ab99_main_1.css" type="text/css" media="all" />

But it doesn't add any flexibility to your layouts - you still have to edit your layout file when the static's filename get changed. And you still have to write HTML "link" tag manually.

Considering the fact you can use Sf2 console to create in a web/ dir a symlink to your bundle's public folder, I find the way Assetic works somewhat obscure. I'm sure that I miss something, so I hope someone can clear that out for me. Thanks.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

清风挽心 2024-12-04 10:40:18

使用一个脚本不会产生太大的效果。资产管理还有其他好处：

但使用 Assetic，您可以随心所欲地操纵这些资产（或者
在提供服务之前从任何地方加载它们。这意味着您可以：
缩小并合并所有 CSS 和 JS 文件
通过某种编译器（例如 LESS、SASS 或 CoffeeScript）运行所有（或部分）CSS 或 JS 文件
对您的图像运行图像优化

还有更多，您可以将它们组合起来以减少请求、过滤它、控制 url、缓存等。

资源

我喜欢：p

Using one script won't have much of an effect. Assetic management holds other benefits:

But with Assetic, you can manipulate these assets however you want (or
load them from anywhere) before serving them. These means you can:
Minify and combine all of your CSS and JS files
Run all (or just some) of your CSS or JS files through some sort of compiler, such as LESS, SASS or CoffeeScript
Run image optimizations on your images

There's more as well, you can combine them for fewer requests, filter it, control the url, cache, etc.

Resource

I Like :p

回复收藏 0 原文

~没有更多了~