Ajax Specific Features

Thursday, March 18, 2010

Topics in This Section • Overview of Scriptaculous • Installation and documentation • Autocomplete textfields – Local version – Ajax version • In place Editor • In-place Editor – Free-text values – Values from combo box Values from combo box Overview • Foundation Bil fP – Built on top of Prototype • Ajax-specific features – Autocompletingtextfields Autocompleting textfields • Textfields with dropdown list of matching choices • Covered in first half of this section – In-place editors In-place editors • Clickable text that you can edit and send to server • Covered in second half of this section • General features • General features – Visual effects (fade in, fade out, highlighting) • Covered in next section – Drag and drop • Covered in later section 7 Downloading and Installation • Download – http://script.aculo.us/downloads • Unzip and grab .jsfiles out of “src” folder – Usually put in subdirectory of scripts since there are many files Usually put in subdirectory of scripts since there are many files • This tutorial corresponds to Scriptaculous1.8.1 • Online documentation – http://wiki.script.aculo.us/ • Online forum htt// l / /biliff – http: //groups.google.com/group/rubyonrails-spinoffs • Prerequisite Scriptaculous requires Prototype I amusing 16 – Scriptaculous requires Prototype. I am using 1.6. • So your HTML page needs to load both libraries • See separate lectures on Prototype…

Download Ajax Specific Features.Pdf

Ajax programming using Digi’s Advanced Web Server

Asynchronous JavaScript and XML (Ajax) is an new and exciting use of existing technologies that make web-based application act more like workstation-based applications. This white paper discussed the use of Ajax with Digi’s NET+OS-based Advanced Web Server (AWS). Example code can be found at this link: http://ftp1.digi.com/support/documentation/aws_and_ajax.zip 3.1 Problem Solved In the normal web-based, form-based application today, a user fills in a form. The problem is that the user must completely fill in the form before the data is sent to the device. In many circles today, this is considered slow and backwards. To give a web- based application a more workstation-based feel, developers want their applications to update fields as the data is entered by the user. Additionally they would like this to happen without the user really being aware that it is happening. This paper discusses how to do this in a NET+OS AWS-based environment. Additionally, up until now, there has been no documentation available to describe how to take advantage of this technology in an NET+OS AWS environment. This paper addresses this deficit. 3.2 Audience This document is intended for users with experience developing applications using either of Digi International’s NET+OS development environments. This includes the Green Hills IDE-based development environment, the gnu-based command line interface (CLI) development environment and the gnu-based ESP (GUI)-based development environments. In order to get the most out of this document, the user should have experience developing web-based NET+OS applications using the advanced web server (AWS) and its pbuilder utility. The user should also have some knowledge of HTML and JavaScript development. In addition, as part of JavaScript knowledge, the user should have some understanding of object oriented programming terms as they are used in the description of the JavaScript code examples. 3.3 Assumptions This document assumes that the user has access to a Digi International NET+OS-based development environment and an embedded development board for trying out the recommendations described in this document. You will be able to get some knowledge from reading this document only, but actually developing a test application and deploying that application to an embedded device will afford the reader a deeper understanding of the material presented herein…

Download Ajax programming using Digi’s Advanced Web Server.Pdf

Ajax Tutorial (Asynchronous Javascript And XML)

Ajax is only a name given to a set of tools that were previously existing. The main part is XMLHttpRequest, a server-side object usable in JavaScript , that was implemented into Internet Explorer since the 4.0 version. It is in Internet Explorer an ActiveX object that was first named XMLHTTP some times, before to be generalized on all browser under the name XMLHttpRequest, when the Ajax technologie becomes commonly used. The use of XMLHttpRequest in 2005 by Google, in Gmail and GoogleMaps has contributed to the success of this format. But this is the name Ajax itself that made the technology so popular. Why to use Ajax? Mainly to build a fast, dynamic website, but also to save resources. For improving sharing of resources, it is better to use the power of all the client computers rather than just an unique server and network. Ajax allows to perform processing on client computer (in JavaScript) with data taken from the server. The processing of web page formerly was only server-side, using web services or PHP scripts, before the whole page was sent within the network. But Ajax can selectively modify a part of a page displayed by the browser, and update it without the need to reload the whole document with all images, menus, etc… For example, fields of forms, choices of user, may be processed and the result displayed immediately into the same page. What is Ajax in depth? Ajax is a set of technologies, supported by a web browser, including these elements: ? HTML and CSS for presenting. ? JavaScript (ECMAScript) for local processing, and DOM (Document Object Model) to access data inside the page or to access elements of XML file read on the server (with the getElementByTagName method for example) ? The XMLHttpRequest class read or send data on the server asynchronously. optionally… ? The DomParser class may be used ? PHP or another scripting language may be used on the server…

Download Ajax Tutorial (Asynchronous Javascript And XML).Pdf

Ajax Tutorial: Drag & Drop

jax Tutorial. If you’re into Web Development, chances are you’ve used Ajax on a few occasions. For those of you who haven’t heard about this exciting and relatively new technology, let me give you a quick low down in this Ajax Tutorial. Ajax is all the rage in Web application Development. It is such an exciting technology that it’s already found use in Google’s most popular applications, such as Gmail and Google Maps. What’s Ajax Tutorial all about? To put it in simple terms: it’s mainly a combination of JavaScript, HTML, XML and Document Object Model (DOM)… with a twist. You see, with conventional JavaScript when you fetch and send information to the server, you need to wait for a response before the user can do anything on the Webpage. Once the browser receives this information, the webpage will blink a few times and refresh. Sounds tedious, awkward and slow? Well, fear not for Ajax takes it all away: no waiting for the server, no re-freshing and no re-loading. Ajax works “behind the scenes” doing all the “roundtrips” and interaction with the server. This enables the update of portions of the Web page without the need to reload or wait for a server response. This makes for a richer and faster browsing experience. To get a taste of Ajax, visit Google Maps and zoom in. Use your cursor to scroll up and down. See how everything happens almost instantly, with no waiting for the page to reload. That’s the magic of Ajax. Now that you’re familiar with what Ajax can achieve, let us put this new technology to some use and learn a few titbits about the language – or shall I say combination of languages from this Ajax Tutorial. This Ajax Tutorial will walk you through writing a simple Ajax program to drag and drop a box effortlessly anywhere in the Window. I will be explaining every portion of the code and what it does as we progress through the tutorial. This will give you a chance to digest the different elements involved in the Ajax language…

Download Ajax Tutorial: Drag & Drop.Pdf

Easy Ajax in symfony

Wednesday, March 17, 2010

Symfony has Ajax helpers that make programming an elaborate interface a piece of cake. This tutorial will show you step-by-step how to create an Ajax-powered symfony application in minutes. Introduction Real lazy folks that can’t stand reading long documentation are advised to watch the online screencast that demonstrates exactly what is written below. Adding items to a shopping cart in common e-commerce applications isn’t very close to the actual “add to cart” metaphor, since it requires clicking an “add to cart” button, watch a new page (the shopping cart), and then go back to the shop or checkout with buttons. Ajax allows to get closer to the cart metaphor, by enabling drag-and-drop interactions and giving immediate visual feedback, without leaving the shop. The target application of this tutorial will be a symfony ported version of the shopping cart demo published by script.aculo.us1 in Rails2. It uses the prototype3 JavaScript framework (bundled with symfony) and some script.aculo.us4 JavaScript that is the core of the JavaScript helpers. Ajax Application Setup First, create a sfdemo project, an app application and a cart module: $ cd /home/steve $ mkdir sfdemo $ cd sfdemo $ symfony init-project sfdemo $ symfony init-app app $ symfony init-module app cart…

Download Easy Ajax in symfony.Pdf

Ajax and Java Web Services

Ajax and Java Web Services preview: In this chapter, I examine how Java Web Services can be used to support Ajax clients. Ajax, or Asynchronous JavaScript and XML, is a programming technique that enables you to create user interfaces for a Web browser that behave more like a local, stand-alone application than a collection of HTML pages. Ajax is a good fit with Java Web Services. Using these two technologies together enables you to publish software components as services (via JAXWS) and create great browser-based user interfaces on top of them (via Ajax). The entire application can then be packaged as an EAR or WAR and deployed on a Java EE application server. To demonstrate this capability, I pick up here where I left off at the end of Chapter 9. In that chapter, I showed you how to build an online shopping application, SOAShopper, which can search across multiple Web-service-enabled sites (i.e., eBay, Yahoo! Shopping, and Amazon). In this chapter, I show how you can develop an Ajax front-end to SOAShopper. In particular, the code examined in this chapter demonstrates how to write an Ajax application that consumes RESTful Java Web Services endpoints. In the second half of this chapter, I review the JavaScript code that implements the SOAShopper Ajax front-end in quite a bit of detail. For those of you who are familiar with Web front-end coding and JavaScript, this detail may seem tedious. I include it because my assumption is that many readers of this book are server-side Java programmers who do not usually do a lot of JavaScript development and, therefore, might be interested in the detailed code explanation…

Download Ajax and Java Web Services.Pdf

Ajax Frameworks and Toolkits

Types of AJAX Toolkit and Framework Solutions of Today • Clients-side JavaScript Libraries (ex: Dojo toolkit) • RMI-like remoting via proxy (ex: DWR) • AJAX-enabled JSF components (ex: NetBeans VWP) • Dynamic Faces (DynaFaces) • Wrapper (ex: jMaki) • Java to JavaScript/HTML translator (ex: GWT) • Port lets and Ajax (ex: JSR 168 portlets) • MVC server-side scripting (ex: Phobos) • Web Application Frameworks with AJAX extension (ex: Shale or Echo2 or Wicket) Client Side Client Side JavaScript Libraries JavaScript Libraries 4 Client Side JavaScript Libraries Java Script, DOM Utilities HTMP, JSP Pages, JavaScript Event Handlers UI Widgets & Components Remoting Abstraction Layer XMLHttpRequest iF ram e 5 Characteristics of Client Side JavaScript Libraries • Server side technology agnostic > The server side technology can be Java EE, . Net, PHP, Ruby on Rails, etc. • You can use them in combination in a single app > You might want to use widgets and JavaScript utilities from multiple sources 6 Technical Reasons for using Client- side JavaScript Libraries • Handles remote asynch. communication (remoting) > Hides low-level XMLHttpRequest operation • Handles browser incompatibilities > No need to clutter your code with if/else’s • Handles graceful degradation > Uses IFrame if the browser does not support XMLHttpRequest • Provides page navigation hooks over Ajax > Back and forward buttons > Book marking 7 Technical Reasons for using Client- side JavaScript Libraries • Provides ready-to-use widgets > Tree, Calendar, Textfield, Button, Split panes, Fisheye, etc. • Provides easy-to-use DOM utility > Easier to use than original DOM APIs • Provides useful JavaScript utilities > Example: Table management, Timer, etc • Provides error handling hook > Easier to add error handler • Provides more flexible event handling > DOM node based, Function call based, AOP style…

Download Ajax Frameworks and Toolkits.Pdf