I'm sad about the announcement that Google is shutting down its Mashup Editor — one reason being that I had spent a fair amount of effort writing about it in Chapter 11 of my book. Oh well. The Google App Engine is touted as a suitable and more powerful alternative to the Mashup Editor — but I have to agree with that the comment that the simplicity of the Mashup Editor was a virtue.
-
Home
Pages
-
Categories
- AJAX
- Amazon
- Amazon EC2
- Amazon S3
- Apress
- BackgroundReading
- Chapter 01: Learning from Specific Mashups
- Chapter 02
- Chapter 03
- Chapter 04
- Chapter 05
- Chapter 06
- Chapter 07
- Chapter 08
- Chapter 09
- Chapter 10
- Chapter 11
- Chapter 13
- Chapter 14
- Chapter 15
- Chapter 16
- Chapter 17
- Chapter 18
- Chapter 19
- chickenfoot
- Creative Commons
- del.icio.us
- design patterns
- drafts
- Firefox
- Flickr
- geocoding
- Google AJAX Libraries API
- Google Earth
- Google Maps
- Google Reader
- Introduction
- ISBN
- javascript
- KML
- LibraryLookup
- maps
- mashup
- mashup camp
- Meta
- Microsoft
- Notelets
- office suites
- open content
- ProgrammableWeb
- Publishing
- remix
- research
- REST
- Riya
- RSS
- screen scraping
- search
- SOAP
- storage
- tagging
- teaching
- technorati
- Thunderbird
- Uncategorized
- web browser
- web services
- weblogging
- Wikipedia
- WordPress
- WSDL
- XML
- Yahoo
- Yahoo! Pipes
-
Tags
AJAX Amazon S3 blurb cover book chickenfoot CSS del.icio.us DocBook Google Google Mashup Editor interview javascript libraries Library of Congress LinkedIn API mashup camp name change OpenAjax OpenID pylinkedin Python QuarkXPress publishing reviews S3 S3Ajax SQLAlchemy WordPress XHTML XML Yahoo! Pipes Zotero
Blogroll
-
RSS Feeds
-
Meta
Post a Comment