1. Programming by a Sample: Rapidly Creating Web Applications with d.mix
Björn Hartmann, Leslie Wu,
Kevin Collins, Scott R. Klemmer
Stanford HCI

2. Summary A site-to-service map original sites are used as samples
samples are visually specified
A server-side active wiki, for authoring and sharing of
user-sampled scripts
and site-to-service mappings

3. d.mix architecture Rewritten page with API annotations Original Page
Proxy Server
Site-to-Service Map
(hosted on d.mix wiki)

4. Prototype Site-to-Service Library
API
Supported Actions
Site-to-Service map code size
Get images from a user’s photo stream, with or without meta data
Get images from an image set
Get images from individual photo pages
Get images matching tags, global or per user, from tag clouds and photo pages
Get images by global image id
Get images from full-text search
355 lines
Single web search result
Web search result set
54 lines
Retrieve a user’s videos
Retrieve most recent videos
Single search result
Search result set
115 lines

5. Advocate Scrape at design-time (rather than run- time)
Search for examples in the solution domain, not the code domain
Browse-and-sample aids users in foraging for examples
Easy and rapid authoring, experimenting and sharing
Site-to-service mappings are maintained as active wiki pages to take advantage of the power of community

6. Criticize Mappings are hard to create and maintain
Complex wiki content: HTML + JS + Ruby + Wiki all in one?
Inconsistent model for sampling
D.mix documents other apis, but what documents d.mix?