| Web 2.0: where civilization eats itself Taipei Times, Taiwan - By Michiko Kakutani Digital utopians have heralded the dawn of an era in which Web 2.0 - distinguished by a new generation of participatory sites like … |
| Web 2.0: where civilization eats itself Taipei Times, Taiwan - By Michiko Kakutani Digital utopians have heralded the dawn of an era in which Web 2.0 - distinguished by a new generation of participatory sites like … |
 Telegraph.co.uk |
This complacency will cost us lives Telegraph.co.uk, United Kingdom - Eight years later, while he was at Army Staff College, I commanded the field hospital at Ajax Bay, during the land battles of the Falklands campaign. … Falklands medic criticises military care |
| Legal Issues Get Trickier in a Web 2.0 World of User-Generated Content Social Computing Magazine, NY - "Identifying legal issues in a 'Web 2.0' world requires more than knowledge of applicable law from normally disparate legal disciplines," added Arne's … |
| Web 2.0 Learning and Knowledge Management Platform Launched Social Computing Magazine, NY - Earlier this year Instancy launched a Software-as-a-Subscription (SaaS) and Web 2.0-based platform for enterprise customers (corporations, … |
| Lotus aims to make the Web 2.0 Connection Techworld.com, UK - "For some, Web 2.0 is Notes generation 2.0 - we understood communities already. People see the sharing of information on the web, and that's something we've … |
I’ve written some notes on the Google Gadget API and how to write a gadget, targeted at developers who already know Ajax.
What’s a Gadget?
- The gadget is an XML file sitting on your server. In my case, http://ajaxify.com/run/widgets/google/diggroundup.xml. It will get cached, so effectively it must be a static file.
- The user adds your gadget to their igoogle portal, or codes it into their own website, by specifying this URL (it may be done indirectly - via the gadget registry. You’ll appear in the registry if you’ve submitted your gadget to igoogle.)
- The gadget is rendered as an iframe, so you have all the usual security constraints which stop you borking the portal and other gadgets. This also means you can’t communicate with other Gadgets other than via than remote calls to a common third-party server (or has anyone tried hooking them together using the iframe-fragment identifier hack? ).
It’s based on a Digg Roundup tool, where the gadget show Digg stories according to user preferences such as topic and whether to go for popular or upcoming stories.
Now we can get our hands on an iPhone, developers are testing out Safari to see what is actually available. How is the DOM? What events get fired? How does the keyboard send onkey* events? How is scrolling handled? How is the JavaScript support?
Abe Fettig has been jotting down his notes, which include:
Joe Hewitt isn’t too happy with his experiments:
My first task has been exploring the DOM events that you can handle. You do not get “mousedown” when you touch the screen. You get “mousedown” and “mouseup” at the same time when you release your finger. The “mousemove” event does not seem to fire at all. There is no way to handle double-clicking because that is the action for zooming, and calling event.preventDefault() doesn’t seem to override that.
If Safari is the current SDK, we need help as developers to build, and debug, applications.