Custom Buttons² Firefox extension buttons can be written to do various tasks that the user may require. The buttons are coded in JavaScript. Many bookmarklets can easily be converted to buttons.
Extension developers will find this extension quite useful in the development cycle. JavaScript code can be prototyped in a custombutton, avoiding the reload chrome step till the code is proven. Then the code can be moved to the extension
From the IBM website:
The page-reload cycle presents one of the biggest usability obstacles in Web application development and is a serious challenge for Java™ developers. In this series, author Philip McCarthy introduces a groundbreaking approach to creating dynamic Web application experiences. Ajax (Asynchronous JavaScript and XML) is a programming technique that lets you combine Java technologies, XML, and JavaScript for Java-based Web applications that break the page-reload paradigm.
Plum is similar to Kaboodle and Stylehive in that it is a social bookmarking site that allows users to add a lot of metadata about bookmarks (including images). Bookmarked items can tagged and be added to a public, private or shared “collection” (there are a number of defaul collections and more can be added).
One key way that Plum is different than other bookmarking site is that it allows users to bookmark items on their computer, not just on the web. A file that is open in certain desktop applications (things like photos, power point presentations, iTunes playlists, address book entries, email, etc) can be added to Plum by clicking a button on the Plummer, a small downloadable application for Windows or Mac. See the last screen shot below for a look at the Plummer.
Gee...projects and local resource tagging! How are we to ever keep up?
Site with tutorials on xmlhttprequest, drag and drop, forms, uploaders, image gallery, live search, and tabbed pages.
A must page.
tagged ajax how_to javascript programming web2.0 by winkler4 ...on 17-MAR-06
Interesting discussion about making OPML dynamic like the RSS feeds that an OPML file aggregates. This would allow the distribution model of OPML to be changed to a subscription model. In TagIt, we've sort of got this without having to change the way feed readers work. Since a bibliography is capable of creating an RSS feed, they already can be read by the feed readers dynamically -- that is, the readers can get new content as the bibliography is updated. And since the bibliography topics themselves are simply posts, they can be consumed via RSS. The only things I'd need to do in the code is
- update the timestamp on the bibliography topic whenever a component is added or edited
- give access to an rss feed of just the bibliography topics (by user or by TagIt instance)


