Tuesday, December 12, 2006

Table of Contents

At least, as of right now. Suggestions? Comments? Complaints? Just know that some of these chapter sections mean more as notes to me than actual chapter sub-headings. Ask questions, though.

  1. Introductions1
    • Background Info
    • Intentions
    • Prerequisites
  2. Usability
    • Interface vs. Showcase
    • User Expectations
    • Feedback and Indications
    • Semantic markup
    • What CSS and JavaScript have in Common
  3. Accessibility
    • Section 508 and WCAG
    • Screenreaders Can Handle AJAX
    • Unobtrusive JavaScript
    • Assuming Nothing
    • Designing with Accessibility in Mind
  4. Client-side Application Architecture2
    • Objects and Event Triggering
    • Model-View-Controller Design Pattern
    • Event-driven Application Development
  5. Debugging Client-side Code
    • Validation, Validation, Validation
    • Code Profiling
    • Browser Tools and Plugins
    • Unit Testing
  6. Performance Optimization
    • Bandwidth vs. Latency
    • Server-side Cache
    • Client-side Cache
    • Content Negotiation
    • Memory Usage
  7. Scalable, Maintainable AJAX
    • General Practices
    • A Multitude of Simple Interfaces
    • Dense, Rich Interfaces
  8. Server-side Application Architecture
    • Designing Applications for Multiple Interfaces
    • Model-View-Controller Design Pattern
    • Using the Factory Pattern with your Template Engine
  9. Keeping a Web Application Secure
    • HTTPS
    • SQL Injection
    • XSS
    • XSRF
    • Don't Trust the User
    • Don't Trust the Server
  10. Documenting
    • Yes, You Need To
    • API Documentation
    • Internal Developer Documentation
    • 3rd Party Developer Documentation
  11. Game Development
    • Single Player
    • Turn-based Multiplayer
    • "Real-time" Multiplayer
  12. Conclusions
    • Remember the Users
    • Design for the Future
    • Develop for the Future
    • Final Thoughts
  • 1Done! Just need to run it through the publisher's template (since I edit in vim and manage in subversion) and send it on its way.
  • 2First draft done! At least, as I wrote it for the sample chapter. I need to do another once-over, getting its coherency in place, so it keeps in line with the rest of the book, then run through the publisher's template, but I have most of the content and code samples there.

Labels: ,

posted by Frozen O at 8:59 PM  

2 Comments:

anAKiN said...

It seems I now know who is in charge of a project named quite the same as AdvancedAJAX AJAX library which I wrote :). Good luck with the book!

2:53 AM  
Frozen O said...

"It seems I now know who is in charge of a project named quite the same as AdvancedAJAX AJAX library which I wrote :). Good luck with the book!"

Thanks for the wish of good luck!

As far as the working title goes, I definitely didn't do any searching for books (let alone code libraries) before hand. Basically it just came from my description of what type of Ajax book I wanted to write.

P.S. Very interesting take on an OO API to making Ajax calls.

5:09 PM  

Post a Comment

Links to this post:

Create a Link

<< Home