Flash 还是 Flex 更适合构建用户交互式订购“向导"?网站? [英] Is Flash or Flex better to build a user interactive ordering "wizard" website?
问题描述
我想看看这些是否构建了一个……"Flash 站点(以支持用户自定义订购流程)是使用常规 Flash 还是 Flex 完成的?
i want to see if these "build a . . ." flash sites (to support a user customized ordering process) are done using regular flash or Flex?
所有这些引导用户"完成定制的订购流程，捕获他们的所有选择并向他们展示他们的所有定制(并最终将他们带到最终订购屏幕).
All of these "walk a user" through a customized ordering process and capture all of their selection and showing them all of their customizations (and ultimately bring them to a final ordering screen).
这些网站的幕后情况是什么并且内置于 flash 或 flex 中?该人是为您可能选择的每个组合创建单独的图像还是此处发生其他事情?
What's going on under the hood on these sites and are built in flash or flex? Is the person creating a separate image for every combination that you could possibly select or is something else happening here?
我仍然无法弄清楚 Flex 或 Flash 是否更适合这样的事情.(为什么 adobe 把这些看似基本的问题搞得这么复杂)
I still can't figure out if Flex or Flash is better for something like this. (why does adobe make these seemingly basic questions so complicated)
是否有任何好的资源或教程可以尝试在网站上的 Flash 中构建此类功能?
Are there any good resource or tutorials for try to build this type of functionality in flash on a website?
推荐答案
Flex VS Flash [总结]
#Adobe FLEX | #Adobe Flash
#Programmer based | #Designer based
+Rapid RIA (MXML for designers) | +Stage & Timeline Based
+Easy to build up simple stuff (think LEGO) | -From scratch
+Skinning | -No skinning
-Problematic skinning | +Easy to design graphical parts
-Missing several parts (graphically) | +Easy to design graphical parts
-Lots of documentation reading (for everything) | +Err... bare functions?
-Bugs lots of it (And working around it) | +Base functions may do little, but they are bug free
+Many "special" user interactions built in | -Err... code it yourself
+Highly modular (file wise) | -Not so (though MovieClips are arguably modular)
-Size of .SWF (Including the flex framework) | +Bare minimal stuff
+Access to special Mobile phone features | -Neg
+ADOBE AIR -> Desktop application features | -Neg
-Animated movies are near impossible to make | +So you make them here and export them to FLEX
长版
Flash 还是 Flex 的问题实际上是基于偏好的.对于您的情况，它几乎可以互换.因此，要真正了解主要差异，您需要了解它们的历史 [有点，这是一个非常长的列表]
Long version
The question of Flash or Flex is really based on preference. For in your case, it is nearly interchangeable. Hence, to truely understand the major differences, you need to understand their history [sort of, it's a really long list down]
Flash 是由 Macromedia 为基于矢量的动画/图形/应用程序的 Web 显示/分发而创建的.请注意，这最初是在拨号仍然司空见惯的时代创建的.并因其 flashPlayer 引擎而大受欢迎，尽管 [.swf 文件] 尺寸很小，但仍能显示令人惊叹"/令人惊叹"的动画/网站/应用程序.[还记得启动页面的时代吗?和 Flash 动画].
Flash was created for the web display / distribution of vector based animation / graphics / application by Macromedia. Note that this was initially created in an era where Dial-Up is still common place. And drove to great popularity, due to its flashPlayer engine, displaying "stunning"/"wowing" animations / websites / applications despite its small small [.swf file] size. [Remember the era of splash pages?, and flash animations].
虽然最初有一个小的代码库 [AS1/2]，但它最初是用于交互式动画的.许多网页设计师很快就利用了时间线，在每一帧上都有不同的页面"/内容"[想想现代国家]，并通过影片剪辑有多个嵌套的时间线.它很粗糙，但有效 =) 几乎到处都可以看到 Flash 页面.
While initially having a small code base [AS1/2], that was originally meant for interactive animations. Many web designers, were quick to exploit the timeline, having different "pages"/"content" on each frame [think modern day states], and having multiple nested timelines via movieclips. It was crude, but it works =) And flash pages were seen almost everywhere.
特别是因为它可以在任何计算机、任何浏览器上运行(Apple 和 Windows 都可以使用).
Especially since it could work on any computer, any browser (a kick to both Apple and Windows).
随着闪存的增长，其代码库(AS1 -> AS2)也在增长.也就是说，直到它被长期的竞争对手#Adobe 收购.其中代码库从头开始完全重做，直到您今天看到的 AS3.这给了它一个非常结构化的编码基础(与 AS1/2 的计划外构建相比)，以及一套许多其他功能(更好的加密、内存保护等)
And with the growth of flash, so was the growth of its code base (AS1 -> AS2). That was, till it was purchased over by its long bitter rival #Adobe. In which the code base was completely redone from the ground up, to the AS3 you see today. Which gave it a much structured coding base (as compared to the unplanned built up of AS1/2), along with a suite of many other features (better encryption, memory protection / etc)
大多数 Flash 用户都不知道，在播放器的幕后，帧、时间线一直是由代码模拟"的.而 AS3 使通过代码操纵时间线变得更加容易.然而，对于 RIA(富互联网应用程序)的成长时代，Flash 有几个缺点，由于 Flash/Java 已经获得了动力.例如服务器-客户端数据连接(虽然有变通办法)，更重要的是...
Unknown to most users of Flash, under the hood of the player, frames, timelines have always been "simulated" by code. And AS3 makes it much easier to manipulate the timeline via code. However Flash, has several drawbacks for the growing era of RIA (Rich-internet applications), that has gain momentum due to Flash / Java. Such as sever-client data connection (though there are work arounds), and more importantly...
时间线...
最初用于轻松操作动画，Flex 只是将整个系统踢出窗口.也有充分的理由.在 Flash 中完成的 RIA 的许多情况下，您将有电影剪辑"跳转到模拟当前状态系统的各种帧.并且实际上对 RIA 开发适得其反(尽管它被 Frame 标签减轻了)，同时产生了巨大的不必要的开销.因为它本质上是在模拟状态.
Originally used to easily manipulate animations, Flex just kicks that whole system out of the window. And with good reason too. In many cases of RIA done in flash, you would have "movieclips" jumping to various frames, which simulates the current state system. And was actually counter productive to RIA development (Though it was mitigated by Frame labels), while producing huge un-needed overheads. As it was essentially simulating states.
因此 flex 诞生了(好吧，时间线只是几个原因之一)，它消除了 flash 中动画"的根源(以及矢量绘图功能).并重新创建一个IDE，这主要是面向程序员的.(有没有想过作为程序员受到动画时间线的欢迎很奇怪?).时间轴已过，状态已出现.作为锦上添花的额外糖衣"，MXML 诞生了.作为快速原型设计和创建界面的一种方式，用于 RAPID RIA 开发.这成为其主要卖点之一.
Hence flex was born (okay, timeline is only one of the several reasons), taking away the roots of "animation" in flash (and the vector drawing capabilities). And recreating an IDE, that is mainly programmers orientated. (ever thought its weird to be greeted by an animation timeline as a programmer?). Timeline is out, states are in. And as an additional "icing" to the cake, MXML was born. As a means of rapidly prototyping and creating interfaces, for RAPID RIA development. Which became one of its major selling points.
FLEX:允许您为任何平台/浏览器(您的手机)快速创建 RIA
FLEX: Allows you to rapidly create RIA for any platform / browser (your phone too)
虽然从面向时间的 flash 到 flex 的转变可能很困难(这对我来说很困难)，但最终证明 Flex 更适合 RIA 开发.同时使编码比 Flash 好得多.
Though the shift from timeline oriented flash to flex may be difficult (it was difficult for me), Flex at the end of the day proved to be much more suited for RIA development. While making coding much nicer then Flash.
FLEX 的副作用，你永远不能离开 Flash，如果你需要完成动画，那么 Flash 提供的简单舞台就消失了.不是提供的基于 XML 的嵌套阶段 FLEX.因此创建了爱子"Flash Catalyst.(虽然我怀疑它可能基于 WIX).作为快速设计 Flash 网站的一种手段.你看，一个主要的主要缺点是它没有舞台"闪光.并非所有网站都打算使用给定的 MXML 模板.如果你想强迫自己的方式(变通办法，如蒙皮)，这是一种痛苦.于是这个爱子就诞生了.(尝试在 flash vs flex 中创建一个简单的自定义图形按钮).
The side-effect of FLEX, you can never leave Flash, if you need animations done, and gone is the simple stage that flash provided. Not the heavily XML based nested stage FLEX provided. Hence the "love-child" Flash Catalyst was created. (Though I suspect it may be based of WIX). As a means of rapidly designing flash websites. You see, a major major draw back flex had, was that it lack the "stage" flash had. And not all websites is meant to use the MXML templates given. And if you wanted to force your way (workarounds such as skinning), it was a pain. So this love child was created. (Try creating a simple custom graphic button in flash vs flex).
同时保留时间线(有点)和舞台一样的 Flash 界面.它保留了 flex 基于状态的属性.而且很快.Flash Catalyst 诞生了.
While retaining the timeline (sort of) and stage like interface of flash. It retains the state based properties of flex. And presto. Flash Catalyst was born.
它通常意味着在将网站导出到 FLEX/FLASH 之前为网站创建"所需的外观/感觉.(自动处理所有变通方法).
It is generally meant as means to "create" the desired look / feel, for a website, before exporting it over to FLEX / FLASH. (Automatically, handling all the workarounds).
(可能是营销计划的一部分).是所有这些产品都是互连的.他们支持相互关联的项目.例如，一个 FLEX 应用程序可以加载一个 FLASH 影片剪辑，它可以在基于时间线的性质中开发.同样，Flash Catalyst 可以将自身导出为 flex.
(Possibly, part of the marketing scheme). Is that all these products ARE INTERCONNECTED. And they support projects linked to one another. For example, a FLEX application can load a FLASH movieclip, which can be develop in a timeline based nature. Similarly, Flash Catalyst can export itself to flex.
那么哪个更好?答案是否定的！: 这是风格和喜好的问题.就个人而言，复杂的动画，都是在 Flash 中完成的(timeline-> 然后转换为 AS3).RIA 开发是在 FLEX 中完成的.他们乱伦的孩子没有被我使用(它既不在这里也不在那里，可悲的是).
So which is better? The answer is NONE! : Its a matter for style and preference. Personally, complex animations, are done in Flash (timeline-> then convert to AS3). RIA development is done in FLEX. And their incest child is unused by me (Its neither here nor there, sadly for it).
但是，如果您一直习惯于基于时间线的设计(艺术专业的学生?)，Flex 会杀死您.同样，如果您一直是 JAVA 或 C++ 程序员，Flash 会杀死您.(好吧，可能有点夸张).
However if you have always been used to timeline based designs (art students?), Flex will kill you. Similarly, if you have always been a programmer in JAVA or C++, Flash will kill you. (OK, that may be exaggeration).
至于幕后:很可能是 AS3 中的代码库，用于生成排列/组合.我非常怀疑每种可能的组合(纸杯蛋糕)都有一个图像，因为使用各种图像/图形"(奶油作为 A 组，纸杯蛋糕底作为 B 组，浇头作为 C 组)要容易得多.并将每个集合与给定的选项联系起来.并生成"最终图像.
As for under the hood: Most likely a code base in AS3 that generates the permutation / combinations. I highly doubt that there is an image for every possible combination (cupcake), for it is much easier, to use various 'images/graphics' (cream as set A, cupcake base as set B, toppings as set C). And to tie each set to the given options. And 'generate' the final image.
对于教程，关于这些示例:
And for tutorial, on those examples:
http://active.tutsplus.com/tutorials/flex/build-an-xml-driven-contact-list-using-flex-3/
基本上每个选项都有一个自定义显示，并将它们堆叠起来.虽然我建议在此之前阅读大量基本的 Flex 教程.
Basically you have a custom display for each option, and stack them up. Though I suggest reading up a lot of the basic Flex tutorials before this.
这篇关于Flash 还是 Flex 更适合构建用户交互式订购“向导"?网站?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
