Flash或Flex更好地构建用户交互式订购“向导”网站？ [英] Is Flash or Flex better to build a user interactive ordering "wizard" website?
问题描述
所有这些都是通过一个自定义的订购流程来漫步一个用户，并捕获他们所有的选择，并显示他们所有的定制（最终将他们带到最终的订购屏幕）。
在这些网站的底层是什么，并建立在Flash或Flex？是人为你可能选择的每个组合创建一个单独的图像，或者是在这里发生的其他事情？
我仍然不知道如果Flex或Flash更好对于这样的事情。 （为什么Adobe会让这些看似基本的问题变得如此复杂）
有没有什么好的资源或者教程来试图在网站的Flash中创建这种类型的功能？解决方案
$ c> #Adobe FLEX | #Adobe Flash
#Programmer based | #Designer基于
+快速RIA（设计师的MXML）| +舞台&基于时间轴的
+轻松建立简单的东西（认为乐高）|从头开始
+ Skinning | - 不剥皮
- 大致剥皮| +易于设计的图形部分
- 包括几个部分（图形）| +易于设计的图形部分
- 文档阅读（一切）| - + Err ...裸函数
- 大量的（并解决它）| +基本功能可能做的不多，但是它们是无缺陷的
+内置许多特殊用户交互-Err ...自己编码
+高度模块化（文件明智）|不过（虽然动画片段可以说是模块化的）
.SWF的大小（包括flex框架） +最小的东西
+访问特殊的手机功能| -Neg
+ ADOBE AIR - >桌面应用程序功能| -Neg
- 动画电影几乎是不可能的+所以你在这里把它们导出到FLEX
$ h $ Long $
flash或flex的问题实际上是基于偏好的。就你而言，它几乎是可以互换的。因此，为了真正理解主要的差异，你需要了解他们的历史[有点...其实很长的列表]兄弟]：
通过#Macromedia创建Flash，用于基于矢量的动画/图形/应用程序的Web显示/分发。请注意，这是最初创建的拨号时代[是的！它的老]仍然是平常的地方。由于它的flashPlayer引擎，尽管其小的[.swf文件]大小很小，但它显示出令人惊叹的/令人惊叹的动画/网站/应用程序。 [记住飞溅的页面的时代？和闪光动画]。
最初有一个小的代码库[AS1 / 2]，最初是为交互式动画设计的。许多网页设计师很快就利用了时间线，在每一帧上都有不同的页面/内容[想想现代国度]，并通过电影剪辑拥有多个嵌套的时间线。这是粗糙的，但它的工作=）和闪光灯页面几乎到处都可见。
特别是因为它可以在任何计算机上工作，任何浏览器（踢苹果和随着闪存的增长，其代码库（AS1 - > AS2）的增长也是如此。直到它被购买其长期的竞争对手#Adobe。其中代码库完全从头开始重做，到今天看到的AS3。这给了它一个非常结构化的编码基础（与非计划的AS1 / 2相比），以及一系列其他功能（更好的加密，内存保护等）。
$ b $对于大多数Flash用户而言，在玩家的引擎盖下，未知的是，帧，时间线一直由代码模拟。而且AS3通过代码操纵时间线变得更加容易。然而，闪存对于RIA（富互联网应用程序）日益增长的时代已经有几个缩影，由于闪存/ JAVA而获得了增长动力。比如sever-client的数据连接（虽然有work around），更重要的是...
时间轴...
最初用于轻松操纵动画，Flex只是将整个系统踢出窗外。也有很好的理由。在许多情况下，在Flash中完成RIA，你将有movieclip跳转到各种帧，模拟当前的状态系统。实际上RIA的开发（尽管它被Frame标签缓解了），同时产生了巨大的不需要的开销。因为它本质上是模拟状态。因此，flex诞生了（ok -..-时间轴只是几个原因之一），带走了flash中动画的根源（和矢量绘图功能），重新创建一个IDE，这主要是面向程序员的（曾经认为奇怪的是作为一个程序员被动画时间线所迎接） - 时间轴已经出来了，状态正在进行中，并且作为一个额外的结冰蛋糕，MXML诞生了，作为快速原型设计和创建接口的手段，RAPID RIA的开发已经成为其主要卖点之一...
$ b
FLEX：允许您为任何平台/浏览器快速创建RIA（您的手机也是D）
从时间线的Flash到flex可能是困难的（对我来说这是一个近在咫尺的@@ $ $），flex在一天结束的时候被证明更适合于RIA的开发。 。
Flash Catalyst [乱伦之谜ld of the two]
保留Flash的时间轴（类似）和舞台等。它保留了flex的基于状态的属性。和presto。 Flash Catalyst诞生了。
通常意味着在将网站导出到FLEX / FLASH之前，为网站创建所需的外观/感觉。 （自动处理所有的解决方法）。
他们都在一个叫做ADOBE的同一个幸福的家庭之下：
（可能是市场营销计划的一部分）是所有这些产品都是互相连接的。他们支持相互链接的项目。例如，一个FLEX应用程序可以加载一个FLASH动画片段，这个动画片段可以基于时间轴的性质进行开发。同样的，Flash Catalyst可以将自己导出为flex。
哪个更好？答案是NONE !!! ：这是一个风格和偏好的问题。个人而言，复杂的动画，在闪光（时间轴 - >然后转换为AS3）完成。 RIA开发是在FLEX中完成的。而且他们的乱伦小孩对我来说是没有用的（它既不在这里，也不在那里，可悲的是）。
然而，如果你一直习惯于基于时间线的设计（艺术系学生？ ），Flex会杀死你。同样，如果你一直是JAVA或C ++的程序员，Flash会杀死你。 （确定，这可能是夸大其词）。
$ b
另外...
至于底层：很可能是AS3中的一个代码库，它产生了排列/组合。我高度怀疑每种可能的组合（蛋糕）都有一个图像，因为使用各种图像/图形（奶油作为集合A，蛋糕基底作为集合B，配料作为集合C）更容易。并将每个组合与给定的选项。和'生成'最后的形象。
而对于教程，在这些例子... ...
http：//active.tutsplus。 com / tutorials / flex / build-an-xml-driven-contact-list-using-flex-3 /
- >基本上你有一个自定义显示每个选项，并堆叠起来。虽然我建议在此之前阅读很多基本的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).
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?
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)
Are there any good resource or tutorials for try to build this type of functionality in flash on a website?
Flex VS Flash [Summary]
#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
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... its a really long list down]
Flash [The older brother]:
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 [Yes! its old] 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].
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.
Especially since it could work on any computer, any browser (a kick to both apple and windows)
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)
Flex [The smart-ass younger sister]:
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 draw backs 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...
The timeline...
Originally used to easily manipluate 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" jumpint 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.
Hence flex was born (ok -.-" 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: Allows you to rapidly create RIA for ANY platform / browser (your phone too =D )
Though the shift from timeline oriented flash to flex may be difficult (it was a near mind!@#$ for me), flex at the end of the day proved to be much more suited for RIA development. While making coding much much "sexier" then flash.
Flash Catalyst [The incest child of the two]
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 in the !@#$... So this love child was created.(Try creating a simple custom graphic button in flash vs flex).
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.
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).
And they are all under the same happy family called ADOBE:
(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.
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).
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).
Additionally...
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/
-> Basically you have a custom display for each option, and stack them up. Though i suggest reading up alot of the basic flex tutorials before this.
这篇关于Flash或Flex更好地构建用户交互式订购“向导”网站？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
