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文件]的大小，但由于其flashPlayer引擎而显示出惊人的"/令人惊叹的"动画/网站/应用程序，并因此引起了极大的欢迎.[还记得初始页面的时代吗?以及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]，最初是用于交互式动画的.许多Web设计人员很快就利用了时间轴，每个帧上都有不同的页面"/内容" [想想现代状态]，并通过电影剪辑具有多个嵌套的时间轴.它很粗糙，但是有效=)并且几乎在所有地方都可以看到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).
随着flash的增长，其代码库(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使得通过代码操纵时间轴变得更加容易.但是，Flash对于RIA(富互联网应用程序)的增长时代具有一些弊端，由于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只是将整个系统踢出了窗外.并且也有充分的理由.在很多情况下，RIA都是通过Flash进行的，您可能会电影剪辑"跳到各种帧，从而模拟当前状态系统.实际上，它对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)
尽管从面向时间轴的闪存过渡到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和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的基于状态的属性.和presto.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中完成的(时间轴->然后转换为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屋！
