Edit In-Place Ajax Scripts

• tEditable – In place editing for tables using the jQuery Framework. It works by allowing you to that edit cells in a table and posted to a server using Ajax.

• Ajax.InPlaceSelect – This script allows you to change the certain text with a drop down list. It is written with the scriptaculous framework and is very similar to Ajax.In Place Editor.

• Ajax.In Place Editor – Allows you to edit text either in a single line or multi line format. It is written with the scriptaculous framework.

• Flicker-Like edit in place – This script removes the use of outdated form interfaces. It will allow you to edit the date in place in real time. It is written with no framework just Ajax. Since its name is Flicker-like you can image that it is very similar to flicker.

• Jeditable – Edit In Place Plugin For jQuery. This is different from tEditable because it works by allowing you to edit a block of text.

• inlineEdit2 – Is a lightweight, easy solution at 2KB uncompressed. It is written with mooTools. It allows you to edit the text very easily just by clicking on the text and hit enter when done. This Script doesn’t show a text box when editing.

• Seamless inline text editing -Written for ASP.Net. It works like the rest of them by clicking on the text and it will become editable.

• Yahoo UI  Edit in Place – This edit in place uses the Yahoo UI Library.   The effect is very similar to Flicker.  But also allows you to edit lists.

• Edit in place – Is written without any framework and written by Tool-Man.org.  This script allows you to edit HTML on the page.  This script also allows you to sort, edit lists, and has a slide show sorter.

• EditInPlace.org – Is written with the Prototype Framework and allows you to edit text and even have an empty text field that you can edit and save.  It also has edit in place drop down list.

Limitations of AJAX

• Ajax enhances the user experience of a web browser but does have limitations. Ajax is primarily a client/server technology. Client nodes in the web do not typically run web servers that can respond to HTTP GET and POST requests. Since clients cannot directly communicate with each other, any distributed application developed using Ajax would require a central web server system to negotiate requests between clients. Client A could generate events/data for and respond to events/data from Client B however both would need to connect to a common web server to facilitate the communication.

• Another limitation of Ajax is slow or unreliable network connections. Traditional web applications that require a full round-trip to the server
  may behave slowly for end users but they would be predictable. End users would generally intuitively know they have performed an action, such as submitting a form or clicking a link, and must wait for a server to respond. With Ajax, users have less intuition about which type of events within a page may result in a need to wait for a server response. Instead of enhancing the end user experience, Ajax over slow or unreliable network connections may reduce usability if not carefully designed to accommodate both fast and slow network characteristics.

• Another consequence of slow and unreliable networks is the need to restrict Ajax payloads to small, efficient data transfers. Even on fast networks, returning large XML datasets or HTML fragments may create a noticeable delay within the end users web browser.