If you need some Pros and concrete RIAs examples, this article is very good : http://www.macromedia.com/devnet/logged_in/thale_rias.html
Have a look at all the examples and try to build them with plain HTML... for most of them, it is nearly impossible. Benoit Hediard www.benorama.com > -----Message d'origine----- > De : Adrocknaphobia Jones [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 7 mars 2003 20:15 > À : CF-Talk > Objet : Pros & Cons of RIAs > > > So, in all the responses I've gotten, I've seen "RIAs are not for you > then" "RIAs really don't make for good e-commerce". So my question is: > When is an RIA justified? When is there a benefit to create an RIA over > an HTML application? In the responses I've gotten, there has only been > one Pro, the optimization of bandwidth. I think the other is quite > obvious, although left unsaid, aesthetics. > > So far I my list of cons is: > - More expensive to develop > - Requires more developers > - No application consistency > - Requires a plug-in > - Initial Load Times Increased Dramatically > - Requirements for internet connection and computer speeds increased > - We rely on a sole company to continue and support the technology (MM) > rather than a consensus (WC3) *No one can buy the wc3 and discontinue > HTML > > My list of pros: > - After initial load bandwidth can be used more efficiently > - Aesthetics > > Do we have any case studies comparing RIAs to HTML applications? I've > heard the pitch numerous times from MM in the last year. I've been > hearing it for about 4 year (Generator). > > Seriously I'm not trying to trash MM or RIAs... I'm just trying to > develop a set of rules so I know when it _is_ justified to develop and > RIA. > > Let's please keep this out of the realms of business politics of MM and > how they treat developers and have a discussion solely on RIAs. > > Adam Wayne Lehman > Web Systems Developer > Johns Hopkins Bloomberg School of Public Health > Distance Education Division > > > -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Friday, March 07, 2003 11:34 AM > To: CF-Talk > Subject: RE: The New Macromedia Website > > > > However, to put things bluntly, HTML sucks. It sucks really > > > bad. It's the worst thing to happen to application interfaces > > > in the short history of computing, next to the QWERTY keyboard. > > > The success of HTML interfaces has been in spite of this > > > awful step backwards in interface design, not because of it. > > > > HTML doesn't suck. It's a beautifully simple means of presenting > > textual information. And with CSS, the potential is there for > > it to be presented just as elegantly as any print-based layout. > > However, HTML wasn't designed to function as an application > > user interface. Which then gets to everything else you said. > > Yes, I just assumed that people would understand that I was criticizing > HTML > as an interface for applications. It's fine for content. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
