在哪里可以找到 Flex html 模板和输出文件夹结构的官方说明?

发布于 2024-07-10 10:04:25 字数 316 浏览 9 评论 0原文

我正在寻找一个 Adob​​e 官方页面,解释 Flex Builder 中使用的各个目录的详细信息,即 html-template、bin-debugbin-release

这些文件夹中发生了很多事情:创建和删除文件夹、自动复制或不复制文件,就像 AIR 应用程序的情况一样。 我正在寻找有关控制此行为的设置的具体信息、文件夹结构的记录意图等。简而言之,我试图了解 Flex 工作流程的一部分,该部分似乎以不可预测且完全未记录的方式工作。

我并不是在寻求组织项目资产的帮助,我更好奇半自动输出文件夹的工作原理以及如何影响其配置。

I'm looking for an official Adobe page explaining the ins and outs of the various directories used in Flex Builder, namely html-template, bin-debug and bin-release.

There's a lot happening in these folder: folders get created and deleted, files get copied around automatically, or not, as seems to be the case with AIR apps. I'm looking for specific information on settings that control this behaviour, documented intention of the folder structure etc. In short, I'm trying to understand a part of Flex workflow that seems to work in unpredictable and completely undocumented ways.

I'm not looking for help in organizing project assets, I'm more curious about how the semi-automatic output folders work, and how to affect their configuration.

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

扫码二维码加入Web技术交流群

发布评论

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

评论(3

十秒萌定你 2024-07-17 10:04:25

我敢说您不会找到此官方文档,因为 Adob​​e 认为这是他们的业务(字面意思)。 请阅读 2008 年 12 月的这篇文章“Flex 最佳实践 – 第 2 部分:开发实践”; 在“处理资产”部分中,您将看到以下建议:文件夹结构看起来非常接近我认为您正在寻找的内容......

I daresay you will not find this official documentation because Adobe considers this their buisiness—literally. Do read this December 2008 article “Flex best practices – Part 2: Development practices”; in the “Handling Assets” section you will see a recommendation for a folder structure that looks very close to what I think you are looking for...

任性一次 2024-07-17 10:04:25

我会在官方文档中查看这些页面:

Flex 应用程序结构 ,
构建概述

应用程序部署 -我的头顶答案是:

  • html-template 的名字很恰当,并且
    存储 HTML“包装器”或
    实际Flash的“容器”
    目的。 如果你需要做“标准”
    HTML/Javascript 设计/交互
    围绕您的 Flash/Flex 应用程序,
    您修改index.template.html
    html-template 内并添加
    外部 CSS、JS 等
    文件夹。
  • bin-debug 是为调试目的而编译的应用版本。 因此,它会获取 html-template 中的所有内容并将其复制到 bin-debug,同时编译构成应用程序的所有 SWF。
  • bin-releasebin-debug 非常相似,但通过 Flex Builder 发布过程进行填充,并提供“查看源代码”等附加选项。 实际上,我之前已经直接从 bin-debug 复制到演示服务器,没有遇到任何问题,但我确信这对于实际部署来说是一个坏主意。

我要补充的唯一一件事是 Flex Builder 尝试尽快创建调试版本,因此它只复制或编译它认为已更改的文件......有时它会错过一些文件。 Project->Clean... 将强制将所有文件重新复制/编译到 bin-debug 中。

I would check out these pages in the official documentation:

Flex Application Structure,
Building Overview,
and
Application Deployment

The short, off-the-top-of-my-head answer would be:

  • html-template is aptly named, and
    stores the HTML "wrapper" or
    "container" for the actual Flash
    object. If you need to do "standard"
    HTML/Javascript design/interactions
    around your Flash/Flex application,
    you modify index.template.html
    inside html-template and add
    external CSS, JS, etc, to that
    folder.
  • bin-debug is the version of your app compiled for debugging purposes. So it takes everything in html-template and copies it to bin-debug while compiling all the SWFs that comprise your application.
  • bin-release is very similar to bin-debug but is populated through the Flex Builder release process and provides additional options like "view source". I have actually just copied straight from bin-debug to a demo server without trouble before, but I'm sure that's a bad idea for actual deployments.

The only other thing I would add is that Flex Builder tries to create the debug builds as quickly as possible, and so it only copies or compiles the files it thinks have changed...and sometimes it misses some. A Project->Clean... will force all the files to be re-copied/compiled into bin-debug.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文