网站完全写入（或显示）在Flash中。当这不是一个好主意？ [英] Website fully written ( or displayed ) in Flash. When this is NOT a good idea?

问题描述

从这个推特： http://twitter.com/azaaza/status/6508524118 我到达一个完全在Flash中制作的网站（至少是前端）。

这看起来太棒了，它可以用HTML + Ajax编写，但我猜（因为我不'我知道自己有很多闪光的东西），他们的网站所有者觉得Flash更舒服，并认为它会更容易（再次，我猜这是在你有数千个飞行小时的情况下才会发生的）

从状态栏来看，大部分图片和文字都是动态下载的（否则flash文件会太重了）

问题（一个或多个）：

什么类型的web应用程序应该考虑使用flash中的所有前端？

会更简单吗？是/否，只有当你吮吸HTML + Ajax，但你擅长在Flash？

是为所有人？

p> b
$ b

我猜，额外的好处是您没有IE + FF + Opera + Chrome + Safari的兼容性问题

这是Web应用程序前端的下一个编程模型吗？

解决方案

这里的大部分答案似乎都是人们声称他们讨厌100％的Flash网站（不仅仅是讨厌或者不推荐，只是讨厌像 flash sux lolz 那样的讨厌），然后提供一些非常弱（有时候只是不真实）参数的列表，作为其原因。尽管我已经在评论中提到了其中的一些，但是让我们在这里写一篇关于Flash网站的最大争论的回顾，以及我为什么不同意他们的看法：

- SEO和深层链接/书签问题 .com / swfaddress /rel =noreferrer> SWFAddress 。 Nuff说。它已经存在好几年了，但是人们仍然认为不可能深入链接或者收藏Flash内容，显然是因为他们从来没有费心去检查它，或者开发了一个Flash网站来面对这个问题（这个问题已经被解决了很多年了，比如我说过）。我觉得有趣的是，大多数人似乎建议/青睐Ajax / JavaScript + XHTML来建立动态网站...但是，Ajax内容也不能被深度链接，书签或谷歌索引，除非你使用解决方法...也适用于Flash内容！那么，为什么很多完整的Flash网站没有实现呢？我不知道，也许没有必要（比如游戏网站，广告网站......大多数 FWA
$ b

- 可访问性：

首先，Flash对于残障用户非常友好。您可以查看 Adob​​e Flash可访问性页面，但我会解释：Flash擅长呈现视觉和音频内容。为需要它的用户构建控件可以很容易地改变字体大小，页面的对比度等等。我不会像说自定义样式表一样容易实现，但它确实不是一个负担/麻烦...如果你需要你的站点可以访问，那么把你的想法付诸实践并且正确地实施（这是真的所有技术）。另外，残疾不仅意味着短视或色盲，例如在我的工作中，我们用手语提供视频，并且同步文本（不是字幕和文字墙），我真的不认为用其他技术来实施会更容易（并且记住，我不认为这是不可能的）。

- Mobile / Iphone：

为了说清楚，内容不会在移动设备上运行（这就是 flashlite 的用处，不是吗？） 。但是，至今为止，许多系统（包括iPhone）都不支持Flash。这是一个很大的问题吗？我不这么认为，请让我详细说明一下。如果我为1024x720构建了一个非常棒的XHTML网站，并且具有很好的javascript效果和漂亮的图片，那么我向你保证它将在移动设备上显得很糟糕（如果它确实如此的话）。我参加了一个移动网络会议，据说移动网站的大小不能超过20kb ...所以祝你好运。

最重要的网站只为移动版本实现了一个特殊的网站，显然是纯HTML格式，这与完整的Flash网站完全相同。至于iPhone上的Flash，当Flash CS5出来，突然Flash电影可以编译成iPhone应用程序，我真的没有理由苹果，以再次按住iPhone的Flash播放器。虽然它并不真正困扰我，正如我所说，因为我相信要走的路是一个特定于移动的版本的网络（甚至特定于iPhone）。

<总结：我发现大多数争论的闪光只是怨恨人们持有闪电，这是基于神话已经存在多年，但真的没有再保持真实许多论点对坏的XHTML / Ajax网站也同样适用，所以大多数时候，批评人士指的只是抱怨缺乏Flash的网站，所以懒惰/懒惰的Flash开发人员应该是责备的人，而不是技术（和事实上，有许多来自设计和/或没有编程背景的Flash开发人员根本没有帮助。）

我会现在从我的角度（Flash开发人员）回答提出的问题：

• 什么类型的webapps应该考虑做所有在
  闪存的前端
  

从我的头顶开始：

• 用于展示或宣传壮观产品的网站，如汽车，服装等。如果您想以超棒的视角和互动性来影响用户，最好的。
  

• 艺术家投资组合：为摄影师，音乐家等设计的网络，艺术家的作品必须融入到如果您是Flash开发人员/为Flash开发公司工作，那么构建一个完整的Flash组合网站是非常有意义的，不是吗？

？ ;）


• 一般而言，任何比用户体验更关心数据的网站。请参考bit101的大师Keith Peters： Flash，有什么好处？ a>




• 会更简单吗？是/否，仅当您使用HTML + Ajax，但在Flash中超过
  时
  

根据您的需要，Flash可能是唯一的工具。一些在Flash中构建起来并不复杂的东西，在XHTML中是一个噩梦。无论如何，如果你吮吸HTML + Ajax，你不应该开发Web应用程序，你应该吗？

• 每个人？

地狱没有。即使我同意，只有完整的Flash网站组成的网站将是一个恐怖的每个人（除了土坯，我猜）。

• 当它不应该被使用？

我会说，当你建立的网站是没有以上：P绝对不是当文字（信息）是网站的最重要的部分。

• 我想，额外好处是您没有
  IE + FF + Opera + Chrome + Safari
  兼容性问题

$ b $是的，这不仅是一个额外的好处，而且是一个巨大的好处。

• 成为webapps前端的下一个编程模型？
  

这是一个棘手的问题。我真的没有看到这是100％Flash / Flex vs 100％XHTML + Ajax网站之间的战争。 Flash / Flex不能代替HTML，但它是一个很好的补充。始终使用正确的工具进行工作，只要明智地使用它，就可以使用任何您需要的技术（或混合）。我发现在Flash中实现维基百科或者你的个人博客也同样愚蠢，因为使用XHTML + Ajax构建一些非常壮观的FWA风格的网站。 对不起巨大的文字，并感谢阅读！期待讨厌的评论;）

From this tweet: http://twitter.com/azaaza/status/6508524118 I reach a website which is made completely in Flash (at least the front end).

alt text http://img704.imageshack.us/img704/3116/screenshotvz.png

It looks fantastic and it could have been written with HTML + Ajax, but I guess ( because I don't know much flash my self ) they site owners felt more comfortable with Flash and thought it would be easier ( once again, I guess this happens when you have thousands of flight hours with flash )

Judging by the status bar, it seems that most of the images and text are downloaded dynamically ( otherwise the flash file would've been too heavy )

Question(s):

What type of webapps should consider do all the frontend in flash?

Would it be easier? Yes/No, only if you suck at HTML+Ajax but you excel at Flash?

Is that for everyone?

When it should not be used?

I guess that an extra benefit is that you don't have IE+FF+Opera+Chrome+Safari compatibility problems

Would this be the next programming model for webapps front end?

解决方案

Most of the answers here seem to be people stating that they "hate" 100% Flash sites (not only dislike or not recommend, just HATE like "omg flash sux lolz" kind of hate) and then providing a list of some really weak (and sometimes just untrue) arguments as reasons for that. Although I've addressed some of them in the comments, let me write here a recap of what seem to be here the biggest arguments against full Flash sites and why I don't agree at all with them:

- SEO and Deep linking/Bookmark Problem

SWFAddress. 'Nuff said. It has been around for years, but people still believe that it's impossible to deeplink or bookmark flash content, obviously because they have NEVER bothered to check it, or developed a Flash site and faced the problem (which has been solved for years, like I said). What I find funny is that most of the people seem to recommend/favor Ajax/javascript+XHTML to build dynamic websites... But Ajax content ALSO can't be deep linked, or bookmarked, or indexed by google, unless you use a workaround... which works for Flash content too!

Then, why many full flash sites out there don't implement it? I don't know, maybe is not necessary (like for a game site, an advertisment site... most of The FWA sites) or it could be just a lazy developer (see below).

- Accesibility:

First of all, Flash is very friendly to users with disabilities. You can check the adobe Flash accesibility page but I'll explain: Flash excels at presenting visual and audio content. It is really easy to build controls that change the font size, the contrast of the page, etc. for users that need it. I won't go as far as to say it's as easy to implement as applying custom stylesheets but it's really not a burden/hassle... if you need your site accesible, put your mind into it and implement things right (which is true for all technologies).

Also, disabilities don't only mean short-sighted or color-blindness, for example in my work we provide video on the web in sign language with syncronized text (not subtitles, a full wall-of-text) for deaf people and I really don't think it would be easier to implement using any other technology (and bear in mind I don't say it would be impossible).

- Mobile/Iphone:

To make things clear, it is just not true that Flash content does not run on mobile (that's what flashlite is there for, isn't it?). It is however true that, as for today, many systems (including the iphone) do not support Flash. Is this such a big problem? I don't think so, and please let me elaborate. If I build an awesome XHTML website optimized for 1024x720, with great javascript effects and pretty pictures, I assure you its going to show up horrible on a mobile device (if it even does). I attended a mobile web conference where it was said that the size of a website for mobile should never exceed 20kb... so good luck with that.

Most important websites implement an special site only for mobile, obviously in plain HTML... which is exactly the same you should do for a full Flash site. As for Flash on the iphone, when Flash CS5 comes out and suddenly Flash movies can be compiled into iphone applications, I really see no reason for apple to hold down the iphone flash player any longer. Although it doesn't really bother me, as I said, because I believe the way to go is a mobile-specific version of the web (or even iphone-specific).

To summarize: I find that most arguments aganist Flash are just grudges people hold aganist Flash, which are based on myths that have been around for years but really don't hold true anymore. Many of the arguments apply just the same to bad XHTML/Ajax sites, so most of the time, critics refer to just complains aganist poorly-built Flash sites, so sucky/lazy Flash developers are the ones to blame, not the technology (and the fact that there are many Flash developers out there that come from design and/or don't have a programming background doesn't help at all).

I'll now answer the proposed questions from my perspective (that of a Flash developer):

• What type of webapps should consider do all the frontend in flash?

From the top of my head:

• Sites to showcase or advertise a spectacular product, like a car, clothing etc. When you want to impact the user with awesome views and interactivity, Flash is by far the best.

• Artists porfolios: webs for photographers, musicians, etc. where the artist's work has to be integrated in the site.

• If you are a Flash developer/work for a Flash developing company, building a full Flash portfolio site makes a lot of sense doesn't it? ;)

• In general, any site that is more about user experience than data. Please refer to the master Keith Peters from bit101: Flash, what is it good for?

• Would it be easier? Yes/No, only if you suck at HTML+Ajax but you excel at Flash?

Depending on your needs, Flash very well could be the only tool. Some of the things that are not complicated to build in Flash would be a nightmare to develop in XHTML. Anyways, if you suck at HTML+Ajax, you shouldn't be developing web apps, should you?

• Is that for everyone?

Hell no. Even I agree that a web consisting of only full Flash sites would be a horror for everyone (except for adobe, I guess).

• When it should not be used?

I would say that when the site you're building is none of the above :P Absolutely not when text (information) is the most important part of the site.

• I guess that an extra benefit is that you don't have IE+FF+Opera+Chrome+Safari compatibility problems

Yes, it really is, not only an "extra" benefit but a really huge one.

• Would this be the next programming model for webapps front end?

This is a tricky question. I really don't see this is a war between 100% Flash/Flex vs 100% XHTML+Ajax sites. Flash/Flex is not there to substitute HTML, but it is a great complement to it. Always use the right tool for the job, and use any technology (or mix) you need as long as you use it wisely. I find it would be equally foolish to implement the wikipedia or your personal blog in Flash, as to build some really spectacular theFWA-style site using XHTML+Ajax.

Sorry for the huge text, and thanks for reading! Looking forward hate comments ;)

这篇关于网站完全写入（或显示）在Flash中。当这不是一个好主意？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！