Flex 准备好迎接黄金时段了吗？
我正在开发一个项目，目前用户数为零，但我们希望扩大到可能有数百人。 目前，我们正在 MySQL 数据库上运行，AMFPHP 与 Flex 进行交互。 我们使用 Flex 是因为它强大的图形功能（对这个项目很重要）并且因为最初的开发人员（不是我）已经了解 ActionScript。 我们目前正在使用 AIR，但可能会在某个时候切换到基于 Web 的 Flash。
我的问题是：
- 对于这样的项目来说，Flex 是一个好工具吗？
- 我们可能会遇到的 Flex 主要限制是什么？
- 我们可能还需要考虑哪些其他开发平台？
谢谢。 - 戴夫
I'm working on a project that currently has zero users but we would like to scale up to potentially hundreds. Currently we are running on a MySQL database with AMFPHP interacting with Flex. We used Flex because of its robust graphic features (important to this project) and because the initial developer (not me) already knew ActionScript. We are currently using AIR but might switch to web-based Flash at some point.
My questions are:
- Is Flex a good tool for a project like this?
- What are the main limitations of Flex that we might encounter?
- What are other development platforms we might want to consider?
Thanks.
- Dave
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
简短的回答是，是的。 已经有很多黄金时段的应用程序使用 Flex 作为其 UI 开发平台。 如果您访问 Adobe 网站，他们会展示很多内容。
就我个人而言，我选择 Flex 有两个原因，首先是，尽管您可能可以在 HTML 中或使用适当的工具包完成 Flex 所做的大部分工作，但 Flex 是为有吸引力和引人注目的用户体验而设计的，并且可以使用 Flash 的所有功能。 另外，开发环境和可用的小部件使编程变得简单而有趣。 我不想引发一场关于 HTML 与 Flex 的宗教战争，所以我将把它留在那里 - 它对我、我的应用程序和客户都有效。
其次，也是更重要的是，它更多地平衡了客户端的处理负载，这意味着我的服务器架构可以针对服务内容和保存数据进行优化。 我的大部分业务逻辑已经迁移到客户端。 在古典建筑领域工作了多年，我认为这是向前迈出的一大步，但我也可以对此提出不同意见。
我对 Flex 的警告来自于需要为您的客户端代码采用正确的架构。 如果你犯了错误，很容易用 Flex 创建一个巨大且性能不佳的应用程序。 让一切事件驱动并且显然是异步的，你应该没问题（“显然”是因为 Flash 播放器是单线程的）。 这就是缺点 1，单线程 Flash 播放器有时会导致问题。
缺点 2 可能更严重，那就是企业环境中的桌面被锁定。 很多时候，您的目标受众没有计算机的管理权限，并且使用的 Flash 播放器不正确，或者根本没有。 这在公共部门组织和军队中尤其如此，因此，如果您要去那里，我会仔细测试您的用户中是否存在 Flash。
除此之外，我衷心推荐 Flex。 把它写在你的简历上也是一件很棒的事情！
华泰
Short answer, Yes. There are already many prime-time Apps using Flex as their UI development platform. If you go to the Adobe site they showcase quite a few.
Speaking personally, I chose Flex for two reasons, first was that, although you probably can do much of what Flex does in HTML or with an appropriate toolkit, Flex is designed for attractive and compelling user experience and has available all of Flash. Plus the development environment and available widgets make it easy and fun to program. I don't want to spark a religious war about HTML vs. Flex, so I'll leave that there - it works for me and my application and customers.
Second, and more important, was that it balances the processing load more towards the client which means my server architecture can be optimised just for serving the content and persisting the data. Most of my business logic has migrated across to the client. Having spent many years in classical architectures I think this is a huge step forward, but I can already her a chorus of disagreement about that too.
My word of caution about Flex comes from needing to adopt the right architecture for your client code. It is pretty easy to create a huge and badly performing app with Flex if you get that wrong. Make everything event driven and apparently asynchronous and you should be OK ('apparently' because the Flash player is single threaded). And that is downside 1, the single threaded Flash player sometimes causes issues.
Downside 2 is perhaps more serious and that is locked down desktops in corporate environments. Quite often your target audience won't have administrative rights to their computer and will have either the wrong flash player or none at all. This is particularly true in public sector organisations and the military, so if you are heading there I would test carefully the presence of Flash amongst your users.
Other than that I heartily recommend Flex. It's also a great thing to have on your CV!
HTH
Flex 没有固有的可扩展性问题，但是如果您有图形密集型应用程序，这些资源的正确服务可能会成为问题，但这与 Flex 关系不大。
唯一值得注意且可能无法运行的平台是 iPhone（无闪存）和一些较旧的非闪存移动设备（尽管现在大多数支持 Flash-lite）
至于替代方案，如果您对图形处理很重视，并且不介意 iPhone，那么除了使用纯 HTML 技术之外，Flex 即使不是最好的跨平台解决方案，也是很好的，这里的技巧是单独的 HTML 可以完成 Flex 可以完成的 99% 的工作，但是如果您的应用程序需要缺失的 1%那么你就不走运了，Flex 还将减少跨平台和大多数浏览器兼容性问题。 所以它可能会让你的工作更有成效。
Flex has no inherent scalability problems, however if you have a graphic intensive application, proper serving of these resources might be a problem, but that has little to do with Flex.
The only note-worthy and likely platform you won't be able to run on is the iPhone (no flash) and some older non-flash mobile devices (although most support Flash-lite nowadays)
As for alternatives, if you are Graphics heavy, and don't mind the iPhone, then Flex is good if not best cross platform solution besides using pure HTML technologies, the trick here is HTML alone can do 99% of what Flex can do, but if your App requires the missing 1% then you're out of Luck, also Flex will reduce crossplatform and most browser compatibility issues. So it might make your work more productive.
Silverlight 2 是一个值得考虑的替代方案。 WPF，如果您正在寻找具有离线支持的东西。
Silverlight 2 is an alternative to consider. WPF if you're looking for something with offline support.
适合。
fits.
Flex + AIR 可能是与 Visual Basic 一样好的工具； 它可能是一个更好的工具，可以提供更灵活的编程语言和免费的开发工具，但请记住这些限制......
我在使用它时看到的主要限制是文档。 社区中似乎没有足够的文档、足够好的文档以及足够的高可见度工作。 （这是来自 .NET 多年的经验；我一直对 MSDN 对方法的描述很少感到不安，但通常能够通过查找最有用的博客文章来处理它。）
其他可能的开发平台将在很大程度上取决于具体情况项目的。 基于 Web 的平台陷入与数据集的深度、有状态的交互（即使使用优秀的 AJAX 库），而如果只是一些 CRUD 表单，则维护任何胖客户端程序（例如 Flex + AIR）的客户端安装可能会太过分。 。
Flex + AIR is probably as good a tool as Visual Basic was; it may be a better tool for having a much more flexible programming language and having free development tools, but keep the limitations in mind....
The main limitation I've seen from working with it is documentation. There seems to be not enough documentation, not good enough documentation, and not enough high-visibility work on it in the community. (This is coming from years in .NET; I've been constantly upset with how little MSDN says about methods but generally able to deal with it by finding the most useful blog posts.)
Other possible development platforms would depend very heavily on the specifics of the project. Web-based platforms bog down in deep, stateful interactions with data sets (even with nice AJAX libraries), whereas maintaining client-side installations of any thick client program (say, Flex + AIR) might be overkill if it's just a few CRUD forms.