6. 11/01/10
Paper to W3C, 2004
We consider Web Applications to be an
important area that has not been adequately
served by existing technologies… There is a
rising threat of single-vendor solutions
addressing this problem before jointly-
developed specifications.
http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html
7. 11/01/10
Paper to W3C, 2004
●
1. Backwards compatibility, and a clear migration path.
●
2. Well-defined error handling.
●
3. Users should not be exposed to authoring errors.
●
4. Practical use: every feature that goes into the Web-
applications specifications must be justified by a
practical use case. The reverse is not necessarily true.
●
5. Scripting is here to stay (but should be avoided where
more convenient declarative mark-up can be used).
●
6. Avoid device-specific profiling.
●
7. Make the process open.
11. 11/01/10
Design Principles - Compatibility
• Support Existing Content
• Do not Reinvent the Wheel
• Pave the Cowpaths
• Evolution Not Revolution
www.w3.org/TR/html-design-principles/
12. 11/01/10
Design Principles - Utility
• Solve Real Problems
• Secure By Design
• Separation of Concerns
• DOM Consistency
26. 11/01/10
Top 20 class names
1. footer 11. button
2. menu 12. main
3. style1 13. style3
4. msonormal 14. small
5. text 15. nav
6. content 16. clear
7. title 17. search
8. style2 18. style4
9. header 19. logo
10. copyright 20. body
http://devfiles.myopera.com/articles/572/classlist-url.htm
27. 11/01/10
Top 20 id names
1. footer 11. search
2. content 12. nav
3. header 13. wrapper
4. logo 14. top
5. container 15. table2
6. main 16. layer2
7. table1 17. sidebar
8. menu 18. image1
9. layer1 19. banner
10. autonumber1 20. navigation
http://devfiles.myopera.com/articles/572/idlist-url.htm
28. Where does that highway go to?
●
Build an HTML5 page
●
See that HTML5 is real world – document what browsers do
now and extend that
●
Use some new structural elements and style them with CSS
●
Chuck in an intelligent form