• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Best Practice Solutions for Frequest Ajax Use Cases With Prototype
 

Best Practice Solutions for Frequest Ajax Use Cases With Prototype

on

  • 4,151 views

These use cases drop in time and again: checkbox lists; live login validation; dynamic form rows; server-side processing progress indicators; list reordering using drag and drop; and more… As ...

These use cases drop in time and again: checkbox lists; live login validation; dynamic form rows; server-side processing progress indicators; list reordering using drag and drop; and more… As always, there are a lot of terrible ways to achieve those, several decent ones, and precious few really good takes. This session will review several such use cases and detail various ways to implement them, contrasting the ugly and the beautiful, showing useful reflexes and rules of thumb, with a special focus on performance and maintenance.

Statistics

Views

Total Views
4,151
Views on SlideShare
4,148
Embed Views
3

Actions

Likes
1
Downloads
47
Comments
0

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Best Practice Solutions for Frequest Ajax Use Cases With Prototype Best Practice Solutions for Frequest Ajax Use Cases With Prototype Presentation Transcript

    • Best-practice solutions for common Ajax use-cases with Prototype Christophe Porteneuve CTO, Ciblo + Prototype Core member
    • Hi • Christophe, 30, French, Paris-based • Day job = mostly Rails + Prototype/Scripty • Prototype Core since January 2007 • The Bungee Book
    • So what’s this about? • Prototype’s one of the most popular JS libraries out there • It’s know a few “growth spurts,” but people haven’t always taken the time to catch up • A lot of sub-par / suboptimal code out there, that should be rethought • A few well-honed patterns will get you far.