Posts in Category "General"

Are you using Adobe’s ActionScript code examples?

Hey there ActionScript developers! As you may or may not know, we provide a lot of code examples in the ActionScript docs. However, these examples come in a variety of shapes and sizes, which sometimes makes it hard to get your bearings. So if you were having trouble running/using examples in the ActionScript 3.0 Developer’s Guide, we have revamped the How to use ActionScript Examples page. Please visit this page and let us know what you think, either by leaving a “Was this helpful?” rating or by posting a comment.

For more detail, see Erick Vera’s post on Tumblr.

-Randy

PS: We have a lot of great ActionScript usage documentation but Page View reports indicate that it is an underutilized resource. So this is just a heads-up that I’ll be blogging about ActionScript content in the coming weeks.

LiveDocs is dead; Long live LiveDocs

“That which we call a rose/ By any other word would smell as sweet…” William Shakespeare.

As most of you know by now, we are moving our comment-enabled HTML content from livedocs.adobe.com to help.adobe.com, but every once in a while, someone asks why we didn’t put anything under livedocs.adobe.com/coldfusion/9/*, so I’m going to post the URLs to the ColdFusion documentation one more time:

The ColdFusion Builder documentation, although technically still in Beta, is in really good shape and worthy of mention:

One of the most exciting developments is that Mallika Yelandur, one of the writers on the ColdFusion documentation team is maintaining a blog for CFDoc topics, and I advise everyone to check it out.

An interesting thing I see is that people still refer to the help.adobe.com-based content as “LiveDocs.” I find this unintended branding to be interesting (and as the developer of the original LiveDocs application, a little bit flattering), but I hope that people aren’t misled by this and are still able to find the most recent ColdFusion documentation.

Finally, Adobe begins its annual holiday shutdown on Thursday, so don’t be surprised that things are quiet until January 4, 2010.

Happy Holidays, everyone!
Randy Nielsen

Get involved! Adobe Cookbook – Recipe Requests

This is from our old friend, Ed Sullivan.

The Adobe Cookbooks application is your one-stop shop for finding and sharing community generated code samples.  One of the great new features of the recently re-designed Cookbooks application is the recipe request feature. This lets users who cannot locate their desired code sample put out a request to other community members. Additionally, fellow community members can vote for specific requests so you can determine at a glance which requests are the most popular.

You can see a list of recipe requests on the home page for each of the supported technologies, (Currently, the Flex Cookbook has the most unanswered recipe requests.) You can also easily stay current on the request queue by subscribing to the uber RSS feed, or you can be notified of requests for specific technologies like Flex.

And while answering a recipe request won’t bring you fame and fortune, it will give you:

  • The opportunity to have the request you addressed featured in the Adobe Developer Connection
  • That warm fuzzy feeling you get from assisting your fellow developers
  • The potential to have your recipe included in an upcoming version of the O’Reilly Flex Cookbook
  • Visibility on adobe.com via Adobe Cookbook contributor recognition features

And, for a limited time only, every person who addresses a recipe request will be sent a free copy of the Getting Started with Flex 3 Pocket Guide.  Just email Ed Sullivan with a link to the recipe request you plan on addressing and after you publish it, just sit back and wait for your book to arrive!

So if you know how to create a simple shopping cart with Flex 3, what are you waiting for?!

Simple Twitter client in Flex

There’s been an increase in talk about Twitter lately, so I decided to try my hand at building a simple client that displays Twitter messages in Flex. Turns out, it was even easier than I thought, so I’ll share it in a quick blog entry.

I used an HTTPService with the resultFormat set to e4x to get the status information. In the result handler, I set the result to an XML object. Twitter.com has some very comprehensive documentation that cover all the service call APIs and return types here:
http://apiwiki.twitter.com/REST+API+Documentation

To display the Twitter statuses, I used an inline item renderer inside a List control. Simple to do and it looks good for a minimum amount of effort.

You need a proxy page that requests data from Twitter, since Twitter.com does not have an open crossdomain.xml file. In this case, we have an ASP.NET server available with an open crossdomain file, so my proxy page (twit.aspx) is written in C# and put up on that server. I am more familiar with PHP server-side code, so it was a little tricky to get the C# syntax right.

My ASPX syntax uses the System.Net.WebClient.DownloadData() method to do the same thing that the file_get_contents() PHP function does.

If you have a PHP server, there’s already an example written in PHP that you can also look at:
http://www.blackcj.com/blog/tag/cross-domain-xml/

Twitter statuses are sent out every 60 seconds, so I used a timer that calls send() on the HTTPService every 60 seconds. This is configurable, too, but there’s no point in making the updates shorter than 60 seconds, according to the Twitter documentation.

This example is currently set up so you can use the twit.aspx page on aspexamples.adobe.com as a test page. You just pass a username to it with a GET request, setting the p parameter to the username you want to track. In my example, I hardwired my Twitter address so you can see it running, but you can put any username in there that you want when you build your own client. Please don’t use the service for production reasons, or we’ll have to lock it down.

Download the files mentioned in this article:
Download file (2K)

Enjoy!

Check out the Experience Design team’s re-launched site

Our Experience Design (XD) team just relaunched Inspire, their external site, http://xd.adobe.com. The XD team contains a bunch of terrific designers and developers, and is responsible for most of the look n’ feel in the latest Adobe products.

Honestly, I don’t always agree with everything coming out of XD, but I am always amazed at their creativity, visual sensibility, and app development chops. You won’t regret taking time to poke around this site.

New Community Help blog

There’s a new Community Help blog at Adobe. It’s a good place to get news about new Community Help features, as well as provide feedback about stuff you like, dislike, or absolutely despise.

You can see the blog here: http://blogs.adobe.com/communityhelp/

Seeking feedback on Labs

Some Adobe folks are asking for feedback to help drive improvements to Adobe Labs. Since Flex was one of the earliest releases on the Labs site, I figure some of the readers of this blog might want to participate in the discussion.

There’s an open-ended thread in the online forums:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=586&threadid=1384250&enterthread=y

We are trying to get as much feedback as possible by in late-August/early-September.

Draft Documentation for Flex and Flash Accessibility

Andrew Kirkpatrick has posted some draft documentation for the Flash Accessibility APIs. This is important information for anyone who builds components that need to be accessible, or is curious about how Flex implements all of its accessibility support.

Please make sure to post comments or bugs to Andrew’s post, to this post, or in JIRA.

Download the ZIP file from Adobe Share

Plugins for Ion search

If you use the http://community.adobe.com/ion/ search engine for finding Flex information fast, then you might find the following useful: A plugin for FireFox and a Google Toolbar custom button for IE that give you instant access to the search engine from within you browser.

FireFox plugin for Ion

  1. Download the ion.xml file.
  2. Save this as ion.xml in your {Mozilla}\searchplugins directory (for
    example, “c:\Program Files\Mozilla FireFox 3 Beta 5\searchplugins”)
    and it should show up in your list of search plugins.

Goole Toolbar custom button for IE

  1. Go to the Ion home page: http://community.adobe.com/ion.
  2. Select Flex from the product drop down list.
  3. Right-click on the text input in the Ion search and click “Generate
    Custom Search…”.

    The Google Toolbar Custom Button Generator dialog appears.

    You can replace “community.adobe” in the first text input with any
    name you want to appear in the toolbar. In the second text input, you
    can replace “Adobe Community Help – Search Results” with any
    description you want.

  4. Click the Replace button and click OK.

That’s it. You can now select “community.adobe” (or whatever string
you specified) from the toolbar, and then execute a search directly.

New “Community Help” features for Flex

The Adobe web team is rolling out new functionality to help Flex coders find the help resources they need.

Currently, the “Ion” project consists of a customized search engine that is populated with the best of the Flex-related resources on the web. You can access this new search feature directly at http://community.adobe.com/ion/. You can also search it by using the “Community-Powered Search” input on the Flex DevNet site.

Also part of Ion is the back end for commenting on Livedocs and DevNet articles. Prior to this, there was no commenting on DevNet articles, and the Livedocs commenting engine was much more restrictive.

This is just the beginning of the Ion project.