Appcasting RSS feeds

It’s not tomorrow but it’s within the same week. Last time I promised to disclose more about the RSS feeds consumed by the component explorer plugin into ADCD. Right after posting that entry, the primary developer of ADCD (Patrick Lau) let me know he had completed posting the entire specification for our appcasting namespace extension on the learning wiki.
Everything you ever wanted to know about the tags used in the feeds consumed by ADCD Component Explorer can be found here.
Patrick also created a page that details out the rational behind our use of appcasting and details out a complete feed here.
Well, that certainly saved me a bunch of typing. Please remember that you can create your own appcasting feeds for your own components. If you do, enter a comment here with your feed location and we’ll see about putting your feed on our server for ADCD to pick up. Yes, we’re looking at a web based solution to do exactly this but need to gauge the numbers of feeds being created for public consumption before embarking on that effort.
Next week I’ll deviate from ADCD news and talk about working in a shared technology group. It’s different than being on a product team and has a unique set of challenges.

Thanks for the feedback

First of all I want to thank the bloggers (Adobe and others) that have posted entries about the Adobe Developer Connection Desktop. The feedback has been universally positive in both the blogs and comments we’ve received through the feedback dialog in the application. We’re monitoring all channels. If you prefer to post feedback via one of the Adobe forums here is the correct forum
The URL for the Developer desktop has changed. Click on the link to find the application at its new location.
OK, enough with the administrative topics, let’s talk technology. Tomorrow I’ll put up a post about the RSS feed structure used by the Component Explorer plug in. We’ve defined a new extension to RSS 2.0 that contains the data items we need. These items are used to provide the detailed information, website, source code, documentation and a visual preview of the component. We’ve provided some sample feeds with ADCD for Flexbox and sample AIR apps. We’ve also worked with the Flex Exchange team here at Adobe. Now, when components are added to Flex Exchange the appcasting RSS feed automatically gets updated.
After I detail the internal structure of these feeds, anyone who posts components can also post a conforming feed.
More coming tomorrow.

It’s about time

My email account shows that this blog was created on October 4th at my request, yet this is my first entry. One of the problems working for a group aptly titled – Emerging Solutions – is that you have to wait for something to emerge before you can discuss it with the world. That wait is finally over. The release of AIR 1.0 allowed my subsection of Core Technology, Emerging Solutions to release generation 2.0 of the Adobe Developer Connection Desktop (ADCD).
I call this generation 2.0 instead of version 2.0 because the entire application has been rewritten in Flex (the previous version was ActionScript 2). You have to become a member (free) of the Adobe Developer Connection in order to download the software.
Over the next few days I’ll be posting entries on the various plug ins that make up ADCD 2.0. We’ll discuss some interesting ideas around using RSS feeds to aggregate and distribute components to developers by overloading the appcasting concept used by application vendors to distribute updates. We’ll also talk about how we built a plug in framework for an AIR application. This framework was used by an independent development firm (Human Xtensions) to build some of the plug ins used by ADCD.
As always I’m looking for feedback on improvements that can be made and bugs that need to be fixed. Right now I think you should sign up for the Developer Network, download ADCD and try it out.
Enjoy…..and I promise that it won’t be 5 months until my next post…