Flex 4 Air 2 RSL（运行时共享库）
有没有人有过在 Flex 4 / Air 2 桌面应用程序中运行时加载 SWC / SWZ 的经验？
非常粗略的想法是拥有一个桌面 Air 应用程序，它能够“下载”附加模块（例如，代表表单的 SWZ/RSL）并在运行时加载这些模块？
假设该应用程序是使用通过网络获取的 XML 文件进行配置的。当有获取新模块（SWZ/RSL）的指令时，应用程序会将模块下载到其应用程序存储文件夹，并在运行时实例化它？
Flex手册似乎表明这是可能的，但谈论的是网络而不是桌面http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fd1.html
有人可以提供任何建议吗？有谁有任何经验，或者知道一些演练/代码示例？
谢谢，
亨利
Has anyone got any experience will loading SWC / SWZ's at runtime within a Flex 4 / Air 2 desktop application?
The very rough idea would be to have a desktop Air app, which is able to "download" additional modules (eg, a SWZ/RSL representing a form) and load these at runtime?
Imagine the App is configured using an XML file obtained over the net. When this has instruction to get a new module (SWZ/RSL), the app will download the module to its App Storage folder, and instanciate it at runtime?
The Flex Manual seems to indicate this is possible, but is talking web rather than desktop http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fd1.html
Can anyone offer any advise? Has anyone got any experience, or knows of some walkthroughs / code examples?
Thanks,
Henry
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可能需要为此使用 Flex 模块。这是一个旧博客，介绍如何在 AIR 应用程序中使用模块：
http://blogs.adobe.com/emalasky/2008/04/remote_plugins。 html
You will probably want to use Flex Modules for this. Here is an old blog that walks through using Modules in an AIR app:
http://blogs.adobe.com/emalasky/2008/04/remote_plugins.html
只是扩展 James 所写的内容 - 模块是实现这一点的方法。
而且，尽管模块的文档讨论了 Web 场景，但没有理由这不适用于 AIR。
您可能需要编写一些自定义代码来首先检查该模块是否已存在于本地存储中，如果不存在，则下载并存储它。然而，从那时起，你应该就可以开始了。
但是，请记住，通过这种方法，您将无法获得 AIR 开箱即用的本机更新程序行为。您需要推出自己的支持来检查先前缓存的模块的新版本是否可用。
Just expanding on what James wrote - Modules are the way to go here.
And, although the docs for modules talk about a web scenario, there's no reason this wouldn't work with AIR also.
You might need to write some custom code to first check to see if the module already exists in the local storage, and if not, download it and store it. However, from there, you should be good-to-go.
However, remember that this approach you won't get the native updater behaviour you get out-of-the-box with AIR. You'd need to roll-your-own support for checking to see if a newer version of a module thats been previously cached is available.