I know I've been posting alot about Spry lately, but the more I use it, the more I love it!  Using the simple-to-implement tools which Spry provides, I am able to spend more time dealing with server-side processing, rather than fighting javascript to get a couple of cool effects.  

A few weeks ago, I blogged about using Spry to return confirmation or error messages for a registration form asychronously to alert users to possible errors in their form BEFORE submission.

Today's example is based on the same principle, although more of an "independant app."  A week ago, a co-worker and I were talking about the idea of placing a "feed reader" inside of a web page, so that users could not only display links to feeds that they follow, but also allow for the feed to be displayed directly in the page.  After our conversation, my thoughts immediately turned to Spry as I was sure a quick, easy solution would be possible.

I was right.

There is really nothing to this.  In classic Spry usability-friendliness, this can be accomplished in about two lines of code:

 

var dsFeeds = new Spry.Data.XMLDataSet("getfeeds.cfc?method=updateFeed", "feeds/feed", { useCache:false });var dsFeedContent = new Spry.Data.XMLDataSet("getfeeds.cfc?method=getFeeds&feedURL={dsFeeds::link}", "rss/channel/item");

The first line creates a Spry More >