DOCSLIB.ORG

Marsily-Msc2010

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Marsily-Msc2010 U C L L S M . Richer Web Applications On Trends, Techniques and Standards Supervisor: Prof. J. V Master esis: Partial Fulllment of the Requirements for the Degree of Master in Business Engineering Charles M 2323.05.00 INGE22MS/G [email protected] Academic Year 2009-2010 . Acknowledgment I would like to thank my supervisor Prof. Jean V for providing me a subject as interesting as rich web applications. Writing this document has redened how I use the Web today. e e e In addition, this work might not have been possible without my family’s continuous support. .. C C i L F iii I v Disclaimer.................................................................. vi Content & objectives........................................................ vi 1 U RIA 1 1.1 Denition and criteria ................................................. 1 ick vs. thin applications ................................................. 3 Client/server applications vs. web applications................................. 4 RIA features and characteristics ............................................. 5 Deployment alternatives ................................................... 6 1.2 Why RIAs are emerging? .............................................. 6 1.3 Limitations ........................................................... 8 1.4 Web applications vs. native apps: what to choose for the iPhone?. 9 1.5 RIAs as a part of a broader Web 2.0 era ................................. 11 1.6 RIAs for enterprises ................................................... 14 Customer-oriented applications ............................................. 14 Organizational-oriented applications ........................................ 16 2 T 17 2.1 Ajax-based applications ................................................ 18 jQuery ................................................................. 19 SproutCore ............................................................. 21 Google Web Toolkit ....................................................... 22 2.2 Adobe Flash & Flex ................................................... 24 i Development characteristics ................................................ 24 Deployment over Flash Player or AIR ........................................ 25 2.3 Curl .................................................................. 27 2.4 OpenLaszlo ........................................................... 27 e LZX language ....................................................... 28 Proxied & SOLO deployment .............................................. 29 2.5 JavaFX ................................................................ 31 Development tools ........................................................ 31 Deployment options....................................................... 31 2.6 Microsoft Silverlight ................................................... 32 2.7 Design patterns for rich web applications ............................... 33 Model-view-controller & SproutCore MVC+SDR ............................. 34 Model-view-presentation.................................................. 35 Model-view-viewmodel ................................................... 35 3-tier architecture ........................................................ 36 2.8 UI layouts, controls and other components .............................. 37 Screen layouts ........................................................... 38 Controls ................................................................ 38 Effects ................................................................. 39 2.9 Features selection & platforms comparison .............................. 39 2.10 A short discussion on web applications techniques ....................... 42 3 O S... 47 3.1 Why Web standards? .................................................. 47 3.2 Key Web standards in use today ........................................ 49 HTML ................................................................ 49 CSS ................................................................... 50 JavaScript .............................................................. 50 3.3 HTML5 .............................................................. 51 HTML5 explained ....................................................... 51 HTML5 features ........................................................ 52 Other specs related to HTML5.............................................. 54 What about Geolocation, SVG, MahML and XHR? ............................ 55 3.4 A short discussion on web applications standards ........................ 56 E 61 B 63 ii . .. L F 1.1 Rich internet applications in use ........................................... 3 1.2 ick vs. thin clients ...................................................... 4 1.3 A screenshot of Google Maps running in a SSB ............................ 7 1.4 A tag cloud illustrating topics associated to Web 2.0 ........................ 13 1.5 An overview of the Bivolino webstore ...................................... 15 1.6 An dashboard application built with Curl................................... 16 2.1 An overview of the Flash integrated platform ............................... 17 2.2 e Ajax application model: asynchronous communications . 20 2.3 A screenshot of the source code of jQuery.com .............................. 21 2.4 A full scale example of a web application using SproutCore . 23 2.5 A SWF le being deployed ................................................ 25 2.6 A SWF le embedded to HTML document................................ 26 2.7 e Curl platform ......................................................... 28 2.8 A typical workow in proxied mode with the OpenLaszlo Server . 30 2.9 An overview of the JavaFX tools ........................................... 32 2.10 An overview of the Microsoft Silverlight platform .......................... 33 2.11 e Model-View-Controller paradigm ..................................... 34 2.12 e common 3-tier model ................................................. 36 2.13 An example of the master/detail screen layout............................... 37 2.14 Illustration of some controls ............................................... 38 2.15 e jQuery UI effect ...................................................... 39 2.16 e market penetration into the browser of Flash, Silverlight and Java . 42 3.1 e Web among devices. .................................................. 48 3.2 e denition of the features among WHATWG and W3C documents . 52 3.3 deviantART Muro ........................................................ 57 3.4 HTML5-related features supported by modern browsers .................... 58 iii . .. I it comes to consumer applications, those can be classied nowadays into two W main categories: desktop applications and Web applications. On one hand, desk- top applications have to be completely installed on the host device, having the possibility to use Internet for further communications (to update the application or to access email services for example). On the other hand, Web applications run on Web servers, accessible in a specic environment which is commonly the Web browser. Web applications were at rst very primitive: an action from the user implied to refresh the page. Interaction was minimal and responsiveness was limited. e two having for direct consequence a poor user experience compared to native applications pre-installed on the computer. But as the Web extended its importance to the world, the need for dynamism, usability and responsiveness has rapidly grown. And richer Web applications are the answer to that need. And the term Rich Internet Application is the one used by platform vendors to describe the evolution of Web applications. e appellation has been coined in a Macromedia (acquired by Adobe Systems in 2005) White Paper in March 2002 [53], but the concept was not totally new at the time. Rich internet applications are usually seen as a mashup between desktop applications and traditional web applications. ey are as interactive and responsive as desktop apps, while being deployed over the Web. e mashup usually implies to transfer part or all the processing to the client, in contrast to Web apps that are running server-side, the browser taking only care of the rendering part. Web applications have nowadays become a day-to-day part of our lives. ey allow us to perform a large variety of tasks making our lives (on the Web or not) easier: banking transactions, social networking, entertainment and online shopping to name only a few. On one end, their availability to nearly any Web-connected devices make them even more v vi I appealing to the end-user. On the other end, it is a good opportunity for developers to deploy their apps over a unique platform: the Web. D is paper focuses on Web-related technologies. Consequently, it should be noted that technologies around the WWW and Internet are evolving rapidly. All the content present in the thesis is up to date till mid-August 2010, the assigned period to submit the nal version of this document. It can take only a couple of weeks for a technology to improve, and sometimes updates can occur on a daily basis. is is the case for the HTML5 specication for e.g. C e purpose of this document is to give an overview of what can be done today in terms of rich web applications, and how it can be done. e following questions are confronted throughout the thesis: • What is a rich web application? Where can we nd them on the Web? • How rich web clients are built? What is available out
Load more

Recommended publications
  • Rich Internet Applications
    Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight Master of Science Thesis in the Programme Software Engineering and Technology CARL-DAVID GRANBÄCK Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Göteborg, Sweden, October 2009 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Rich Internet Applications (RIAs) A Comparison Between Adobe Flex, JavaFX and Microsoft Silverlight CARL-DAVID GRANBÄCK © CARL-DAVID GRANBÄCK, October 2009. Examiner: BJÖRN VON SYDOW Department of Computer Science and Engineering Chalmers University of Technology SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Göteborg, Sweden, October 2009 Abstract This Master's thesis report describes and compares the three Rich Internet Application !RIA" frameworks Adobe Flex, JavaFX and Microsoft Silverlight.
    [Show full text]
  • THE FUTURE of SCREENS from James Stanton a Little Bit About Me
    THE FUTURE OF SCREENS From james stanton A little bit about me. Hi I am James (Mckenzie) Stanton Thinker / Designer / Engineer / Director / Executive / Artist / Human / Practitioner / Gardner / Builder / and much more... Born in Essex, United Kingdom and survived a few hair raising moments and learnt digital from the ground up. Ok enough of the pleasantries I have been working in the design field since 1999 from the Falmouth School of Art and onwards to the RCA, and many companies. Ok. less about me and more about what I have seen… Today we are going to cover - SCREENS CONCEPTS - DIGITAL TRANSFORMATION - WHY ASSETS LIBRARIES - CODE LIBRARIES - COST EFFECTIVE SOLUTION FOR IMPLEMENTATION I know, I know, I know. That's all good and well, but what does this all mean to a company like mine? We are about to see a massive change in consumer behavior so let's get ready. DIGITAL TRANSFORMATION AS A USP Getting this correct will change your company forever. DIGITAL TRANSFORMATION USP-01 Digital transformation (DT) – the use of technology to radically improve performance or reach of enterprises – is becoming a hot topic for companies across the globe. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-02 Companies face common pressures from customers, employees and competitors to begin or speed up their digital transformation. However they are transforming at different paces with different results. VERY DIGITAL CHANGING NOT VERY DIGITAL DIGITAL TRANSFORMATION USP-03 Successful digital transformation comes not from implementing new technologies but from transforming your organisation to take advantage of the possibilities that new technologies provide.
    [Show full text]
  • Open Source Web GUI Toolkits
    Open Source Web GUI Toolkits "A broad and probably far too shallow presentation on stuff that will probably change 180 degrees by the time you hear about it from me" Nathan Schlehlein [email protected] 1 Why Web Developers Drink... Can't get away with knowing one thing A Fairly Typical Web App... ➔ MySQL – Data storage ➔ PHP – Business logic ➔ Javascript - Interactivity ➔ HTML – Presentation stuff ➔ CSS – Presentation formatting stuff ➔ Images – They are... Purdy... ➔ httpd.conf, php.ini, etc. Problems are liable to pop up at any stage... 2 The Worst Thing. Ever. Browser Incompatibilities! Follow the rules, still lose Which is right? ➔ Who cares! You gotta make it work anyways! Solutions More work or less features? ➔ Use browser-specific stuff - Switch via Javascript ➔ Use a subset of HTML that most everyone agrees on 3 Web Application? Web sites are... OK, but... Boring... Bounce users from page to page Stuff gets messed up easily ➔ Bookmarks? Scary... ➔ Back button 4 Why A Web Toolkit? Pros: Let something else worry about difficult things ➔ Layout issues ➔ Session management ➔ Browser cross-compatibility ➔ Annoying RPC stuff 5 >INSERT BUZZWORD HERE< Neat web stuff has been happening lately... AJAX “Web 2.0” Google maps Desktop app characteristics on the web... 6 Problem With >BUZZWORDS< Nice, but... Lots of flux ➔ Technology ➔ Expectations of technology Communications can get tricky Yet another thing to program... ➔ (Correctly) 7 Why A Web Toolkit? Pros: Let something else worry about difficult things ➔ Communications management ➔ Tested Javascript code ➔ Toolkit deals with changes, not the programmer 8 My Criteria Bonuses For... A familiar programming language ➔ Javascript? Unit test capability ➔ Test early, test often, sleep at night Ability to incrementally introduce toolkit Compatibility with existing application Documentation Compelling Examples 9 Web Toolkits – Common Features ■ Widgets ■ Layouts ■ Manipulation of page elements DOM access, etc.
    [Show full text]
  • Protecting Online Video Distribution with Adobe Flash Media Technology
    White Paper Protecting Online Video Distribution with Adobe Flash Media Technology Table of contents Introduction 1 Introduction Online video is a growing phenomenon. Record numbers of people are going online to watch 1 Overview of Adobe video everything from user-generated videos and breaking news events to television programs and distribution solutions full-length movies. Gone are the days of waiting for a program to air; consumers can now choose 2 Best practices for effective content protection from a plethora of high-quality content, available on-demand. 2 Flash Media Server content From advertising-funded videos to subscriptions to pay-per-view, content providers are adapting protection features a variety of business models to monetize content in the online world. As an owner or distributor 3 Flash Media Server workflow of premium commercial content, such as films and TV shows, you must ensure that hackers do example 4 Persistent content protection with not bypass your business model or violate your copyrights. Flash Media Rights Management Content protection solutions help create and preserve revenue streams; maintain copyright; and Server preserve content integrity or privacy. For instance, hackers may attempt to bypass payment in a 5 Flash Media Rights Management Server content protection pay-per-view model. Others may try to rip your content for redistribution. Worse, someone features could try to make money from pirated content, or may introduce their own advertising or 5 Comparison between Flash Media branding but skip paying content licenses or bandwidth fees by piggybacking on your Rights Management Server and distribution platform. In an enterprise situation, a disgruntled employee may be tempted to post Flash Media Server valuable or private company information on public video sites.
    [Show full text]
  • Design of a Service-Oriented Dashboard
    DESIGN OF A SERVICE-ORIENTED DASHBOARD by GAYATHRI SUNDAR MURAT M. TANIK, COMMITTEE CHAIR DAVID G. GREEN GARY J. GRIMES JOHN L. HARTMAN IV A THESIS Submitted to the graduate faculty of The University of Alabama at Birmingham, in partial fulfillment of the requirements for the degree of Master of Science BIRMINGHAM, ALABAMA 2007 ii DESIGN OF A SERVICE-ORIENTED DASHBOARD GAYATHRI SUNDAR ELECTRICAL ENGINEERING ABSTRACT Service-Oriented Enterprises are currently focused on offering enhanced user ex- periences to customers, employees, and enterprise partners who use the enterprise’s soft- ware applications. A better user experience is delivered through the presentation of ser- vices and business processes to the user in a composite manner, and by facilitating a bet- ter user-application interaction for the user. Our experience with the bioinformatics do- main helped us to see that although existing models of enterprise portals offer an inte- grated environment to present applications and enterprise resources, they are not suffi- cient to address certain complex user-application interactions. In this thesis, we present a design for a Service-Oriented Dashboard to address this deficiency. The service-oriented dashboard leverages Service-Oriented Architecture to pre- sent an integrated environment to access and interact with the diverse and isolated soft- ware tools, applications, and resources of an enterprise. We address the design of the dashboard at three levels: the presentation layer, the task composition layer, and the ser- vices layer. We introduce in the thesis the notion of describing the user’s job function as a composition of tasks. Users, through this approach, will be able to compose applica- tions according to the user’s tasks.
    [Show full text]
  • Adobe® Media Server 5 Standard High Quality Video Playback Consistent Across Devices
    Adobe Media Server 5 Standard Datasheet Adobe® Media Server 5 Standard High quality video playback consistent across devices Step up from progressive download video delivery and deliver adaptive streams to the widest audience. Stream to iOS and Adobe Flash® Player with a single media source. Adobe Media Server 5 Standard is an economical solution that enables you to start streaming live and on demand content quickly and easily to a wide variety of platforms and devices. It provides all the features you need to stream and encrypt video and audio, providing a consistent playback across Apple iOS, Android, connected TVs, and the desktop—with a simplified workflow and better performance. New features in Adobe Media Server 5 Standard Adobe Media Server 5 Standard provides numerous video streaming innovations—over standard HTTP connections as well as RTMP delivery. • Simplified publishing workflows for HTTP streaming—Use the same source media and live streams to deliver full adaptive bitrate experiences to Adobe Flash, Android, and Apple devices. • Integration with Adobe Access 4—Enjoy protected RTMP support via a content license technology embedded in the server (Adobe Access 4 licensing server is a separate purchase). • 608/708 Closed Caption compliance—Support all avenues to increase your audience size with full support for closed caption transmission to Adobe Flash and Apple iOS devices such as the New iPad. EIA-608 (line 21) closed caption support meets FCC requirements • Reduced storage and infrastructure costs—A single MPEG-4 asset is required for each bitrate, and optional real time packaging eliminates the need to prepare content in advance.
    [Show full text]
  • Open Source Bridge Touchscreen Presentation
    Interactive kiosk display framework Peter Krenesky ([email protected]) Rob McGuire-Dale ([email protected]) http://trac.osuosl.org/touchscreen What is Touchscreen? Interactive kiosk display framework that is: Portable Plugin-based Simple and flexible API Open-source How can Touchscreen be used? Interactive information kiosks How can Touchscreen be used? Public information displays Touchscreen demonstration How we use Touchscreen at the Open Source Lab Technologies in Touchscreen How Touchscreen is built Languages in Touchscreen HTML & CSS JavaScript jQuery (sexy JavaScript library) Raphael (JavaScript SVG graphics library) Python Django (server-side web framework) Twisted (python networking engine) Why not Flash or OpenLaszlo? Original Touchscreen (v1.0) was OpenLaszlo (compiles to Flash) Pros Touchscreen 1.0 Fast Javascript support Could parse XML feeds Cons Niche language poor HTML integration OpenLaszlo has annoying syntax <include href="lib/lzx/screen.lzx" /> <!-- FTP User Map --> <dataset type="http" name="dset_ftpUserMap" src="http://ftp-osl.osuosl.org:8000/"> </dataset> <datapointer xpath="dset_ftpUserMap:/rss/channel" rerunxpath="true"> <method event="ondata"> var label = this.xpathQuery('item[1]/title/text()'); var lat = this.xpathQuery('item[2]/title/text()'); var lon = this.xpathQuery('item[3]/title/text()'); screen_osl_ftpusersmap.createPoint(lat,lon, label); label = null; lat = null; lon = null; </method> </datapointer> <include href="lib/lzx/circle.lzx"/> <resource name="ftpusermap" src="screens/ftpmap/map_1360nolabel.png"/> <include href="screens/ftpmap/ftpusersmap.lzx"/> Why SVG and not canvas? SVG objects can: can be styled with css be manipulated with jQuery receive javascript events Speed Differences SVG better for large objects Canvas better for many smaller objects Conclusion SVG for interactivity Canvas for many animated objects Raphaël: a javascript SVG library provides easy API on top of SVG.
    [Show full text]
  • Interfacing Openlaszlo Applications to Web Services
    1 Interfacing OpenLaszlo Applications to Web Services An Excerpt from “Laszlo in Action” By Norman Klein and Max Carlson with Glenn MacEwen Early Access Release: January 2007 Print Release: November 2007 | 500 pages ISBN: 1-932394-83-4 www.manning.com/laszloinaction For Source Code, Free Chapters, the Author Forum and more information about this title please go to www.manning.com/laszloinaction 1 2 Interfacing OpenLaszlo Applications to Web Services If you've been enviously eyeing the RIA capabilities of OpenLaszlo, but been daunted by its interface requirements, then you'll be glad to know that interfacing to OpenLaszlo is just like that old Talking Heads song "same as it ever was". In other words, OpenLaszlo uses the same HTTP standards that you're familiar with; allowing OpenLaszlo applications to co-exist with your HTML web applications to further leverage your server-side web services. All OpenLaszlo communications with the server are still based on sending and receiving HTTP requests and responses. OpenLaszlo operates just like Ajax by requiring HTTP responses to be composed of XML instead of HTML. The technical term for this is a ReST-based "XML-over-HTTP" service, but this is only a fancy way of describing the familiar operation of the web. So why does it use XML and not HTML? Since an RIA can provide a superior visual presentation, only the data is needed as the HTML presentation details are superfluous. OpenLaszlo's compliance to open standards allows it to interface to any HTTP web server; ranging from basic HTTP web servers such as Apache, Jetty or Microsoft's IIS to the different web frameworks such as Struts, Tapestry, Ruby on Rails, Microsoft .Net that work with servlet containers to provide enterprise class services.
    [Show full text]
  • Quaxe, Infinity and Beyond
    Quaxe, infinity and beyond Daniel Glazman — WWX 2015 /usr/bin/whoami Primary architect and developer of the leading Web and Ebook editors Nvu and BlueGriffon Former member of the Netscape CSS and Editor engineering teams Involved in Internet and Web Standards since 1990 Currently co-chair of CSS Working Group at W3C New-comer in the Haxe ecosystem Desktop Frameworks Visual Studio (Windows only) Xcode (OS X only) Qt wxWidgets XUL Adobe Air Mobile Frameworks Adobe PhoneGap/Air Xcode (iOS only) Qt Mobile AppCelerator Visual Studio Two solutions but many issues Fragmentation desktop/mobile Heavy runtimes Can’t easily reuse existing c++ libraries Complex to have native-like UI Qt/QtMobile still require c++ Qt’s QML is a weak and convoluted UI language Haxe 9 years success of Multiplatform OSS language Strong affinity to gaming Wide and vibrant community Some press recognition Dead code elimination Compiles to native on all But no native GUI… platforms through c++ and java Best of all worlds Haxe + Qt/QtMobile Multiplatform Native apps, native performance through c++/Java C++/Java lib reusability Introducing Quaxe Native apps w/o c++ complexity Highly dynamic applications on desktop and mobile Native-like UI through Qt HTML5-based UI, CSS-based styling Benefits from Haxe and Qt communities Going from HTML5 to native GUI completeness DOM dynamism in native UI var b: Element = document.getElementById("thirdButton"); var t: Element = document.createElement("input"); t.setAttribute("type", "text"); t.setAttribute("value", "a text field"); b.parentNode.insertBefore(t,
    [Show full text]
  • ADOBE AIR SDK RELEASE NOTES Version 33.1.1.190
    Public 1(21) ADOBE AIR SDK RELEASE NOTES Version 33.1.1.190 Adobe AIR SDK Release Notes Version 33.1.1.190 Date 10 July 2020 Document ID HCS19-000287 Owner Andrew Frost Copyright © 2020 HARMAN Connected Services Document Id: HCS19-000287 All rights reserved. Public 2(21) ADOBE AIR SDK RELEASE NOTES Version 33.1.1.190 Table of contents 1 Purpose of the Release ..................................................................... 3 2 Release Information .......................................................................... 4 2.1 Delivery Method ................................................................................... 4 2.2 The Content of the Release ................................................................. 4 2.3 AIR for Flex users ................................................................................ 5 3 Changes and Issues .......................................................................... 6 3.1 Changes in this Release ...................................................................... 6 3.2 Known Problems ................................................................................. 6 3.3 Previous Changes ............................................................................... 7 4 Updating tools/IDEs to support 64-bit ARM .................................. 12 4.1 AIR Developer Tool ........................................................................... 12 4.2 ADT Architecture Configuration ......................................................... 12 4.3 Flash Builder ....................................................................................
    [Show full text]
  • ADOBE AIR SDK RELEASE NOTES Version 33.0.2.338
    Public 1(15) ADOBE AIR SDK RELEASE NOTES Version 33.0.2.338 Adobe AIR SDK Release Notes Version 33.0.2.338 Date 6 December 2019 Document ID HCS19-000287 Owner Andrew Frost Copyright © 2019 HARMAN Connected Services Document Id: HCS19-000287 All rights reserved. Public 2(15) ADOBE AIR SDK RELEASE NOTES Version 33.0.2.338 Table of contents 1 Purpose of the Release ..................................................................... 3 2 Release Information .......................................................................... 4 2.1 Delivery Method .................................................................................. 4 2.2 The Content of the Release ................................................................. 4 2.3 AIR for Flex users ................................................................................ 4 3 Changes and Issues .......................................................................... 5 3.1 Changes in this Release ...................................................................... 5 3.2 Known Problems ................................................................................. 5 3.3 Previous Changes ............................................................................... 5 4 Updating tools/IDEs to support 64-bit ARM .................................... 9 4.1 AIR Developer Tool ............................................................................. 9 4.2 ADT Architecture Configuration ........................................................... 9 4.3 Flash Builder ......................................................................................
    [Show full text]
  • Developing Rich Internet Applications with Rails, Openlaszlo, and Eclipse Automate Quickly with Rails
    Developing rich Internet applications with Rails, OpenLaszlo, and Eclipse Automate quickly with Rails Skill Level: Intermediate Robi Sen ([email protected]) Freelance Writer Department13 12 May 2006 Explore at a high level how to develop a rich Internet application using OpenLaszlo, Ruby on Rails, MySQL, and Eclipse to provide a common IDE to not only develop your application but also to automate many of the steps in developing a Rails or OpenLaszlo application. This will further speed up and streamline the already fast development cycle of Rails applications. Section 1. Before you start Ruby on Rails has over the past year become one of the fastest growing and most popular open source Web application development frameworks. But because of the focus on building HTML applications, some have criticized Rails as being inflexible. Especially with the emergence of rich Internet applications (RIAs), applications using technologies such as Flash for user interface development and XML for data transport to replicate desktop application functionality, open source developers have wondered if there is some way to easily create RIAs that can exploit the pure object-oriented language of Ruby and the unique rapid application development features of Rails. About this tutorial This tutorial will expose you to two of the hottest platforms in Web development: Ruby on Rails, for fun and rapid Web application development; and OpenLaszlo, the open source RIA server. You will see that creating visually appealing desktop-like Developing rich Internet applications with Rails, OpenLaszlo, and Eclipse © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 28 developerWorks® ibm.com/developerWorks applications deployed and managed over the Web can be incredibly easy with these platforms.
    [Show full text]