AJAX holds a lot of promise for web usability, and the underlying technology has already delivered some stunning applications. But its no magic bullet. Careful design is always required, and it must be based specifically on the technology at hand. As AJAX emerges, were going to learn more about what sort of design works, and well need ways of documenting this information and talking about it. Fortunately, the evolution of this particular technology will take place at a time when design patterns are well-entrenched in the industry, and design patterns are an excellent means of knowledge representation. Thus, it makes sense to begin cataloguing AJAX design patterns. These are some thoughts based on current examples and demo systems
Software Theory and Practice for the Real World by Michael Mahemoff
Thursday, May 19, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- Using QCLRDTAQ to clear data queues in CL and RPG
- Creating an as400 Query
- Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)
- UDATE and *DATE in AS400 RPG
- AS400 Job Scheduler
- Using as400 QRCVDTAQ api to retrieve a message / entry from a dataqueue
- AS400 API - QCMDEXC - Execute Command
- Adobe Flex 2.0 Beta
- IBM WebSphere Developer Technical Journal: Maintain continuous availability while updating WebSphere Application Server enterprise applications
- EclipseZone - Use Embedded Tomcat in Eclipse for a Webapp
No comments:
Post a Comment