events/2006-03-21-mix06-microformats

(Difference between revisions)

Jump to: navigation, search
(formatting changes)
Line 7: Line 7:
11am-12:15pm
11am-12:15pm
-
[[http://spaces.msn.com/siteexperts/}Scott Isaa]]
+
[http://spaces.msn.com/siteexperts/ Scott Isaacs]
Notes/Quotes:
Notes/Quotes:
Line 87: Line 87:
* Prioritize the loading of components
* Prioritize the loading of components
* Never expire static content (change the URL to break the cache)
* Never expire static content (change the URL to break the cache)
 +
 +
=== X-Browser Development ===
 +
* Minimize browser specific code in the business logic
 +
* Abstract and centralize API differences
 +
* We extend Firefox and Opera DOM to be compatible with IE
 +
* CSS Differences - Avoid Hacks
 +
* We classify and override via standard selectors
 +
* HTML class="Mozilla M1 D5 Windows"
 +
* Body {margin:10px}
 +
* .Mozilla Body {margin:5px} /* Override Mozilla */
 +
* (hmm... this is quite clever and much more readable)
 +
* ... missed slide ...
 +
* demo of Scott's blog
 +
=== Back Button And Addressability ===
 +
* Users expect the web to work (I love that line)
 +
* Demo: MSN Spaces, Windows Live
 +
* Travelog (History stack) is hard
 +
* Windows Live beta
 +
* back button works
 +
* you can change the hash of the URL [fragment identifier] without reloading the URL
 +
* and thus keep back button working
 +
=== Accessibiliy ===
 +
* Web Accessibility is challenging
 +
* "Use HTML semantics appropriately"
 +
* (wow how far semantic HTML awareness has come in the past four years)
 +
* HTML Accessibility
 +
* Always use structural semantics to establish "role"
 +
* E.g., Hn, Label, TH (table headers), lists, etc.
 +
* (rather than nested DIVs)
 +
 +
=== Building Web Applications ===
 +
...
 +
 +
=== Q&A ===
 +
 +
* Q: What kills JavaScript perf is memory leaks in the browser
 +
* IE6 has some leaks
 +
* if you create a circular reference between a document object and a javascript object then it won't go away
 +
 +
* Q: mashups with SSL
 +
* A: interesting challenge. the real question is how do we securely integrate in a way that is trusted by partners and customers? you have to go entirely HTTPS across the board
 +
 +
* Q: are you familiar with the DOJO toolkit? it solves a lot of the problems memory leaks, back button
 +
* A: haven't looked too deeply at DOJO.  we have a system where objects get created and destroyed all the time.  not sure if they do document level garbage collection or what.
 +
 +
* Q: about Atlas
 +
* A: ...
 +
 +
* Q: about using AJAX to build a 24fps videogame
 +
* A: (heh)
 +
 +
* Q: is there someway we could have a simple lean AJAX request?
 +
* ...
 +
 +
* Q: what is wrong with using iframes?
 +
* A: 1. themes won't work with the iframe ''this is ASP.NET-specific reference'' --[[DimitriGlazkov]]
 +
* A: 2. iframes consume a lot of memory (read: Trident instance) on the order of 20 megabytes of memory (YIKES!)
 +
* A: 3. security

Revision as of 20:29, 21 March 2006

Contents

Microformats discussions at Mix06

March 21st, 2006

Lessons from the Trenches

11am-12:15pm

Scott Isaacs

Notes/Quotes:

Lessons from the Trenches: Engineering Great AJAX Experiences

Modern Development Patterns

Live Clipboard Demo

XML Proxying And Scalability

Web Service Integration

efficiency

Optimizing the Network

...

Be Wary Of Security

Prioritizing Network Requests

Code/Resource Deveployment

X-Browser Development

Back Button And Addressability

Accessibiliy

Building Web Applications

...

Q&A

events/2006-03-21-mix06-microformats was last modified: Wednesday, December 31st, 1969

Views