Tag: adobe flex
I was working on a component for a client that uses search.twitter.com to find all relevant tweets based on a query string recently and I noticed there’s a lot of other samples out there that use some hefty XML parsing code to sift the data rather than make life easy with e4x. The Twitter search API uses XML namespaces in its results, and it seemed that many other posts out on the intertoobs (can I coin this term?) were implying that it caused problems within AS3. Not true. Since I didn’t find a lot on the Twitter search topic specifically, a new blog post was born. The following is a quick and easy sample of how to use e4x in your XML results by using the given XML namespaces.
For this client’s component, I didn’t need to authenticate users, but rather, search for all public streams via a query string. If you take a look at the Twitter search API docs you can see the process pretty straightforward, it’s just using URL query strings to retrieve data . Generally, you can search for tweets:
- containing a word
- from a user
- to a user
- referencing a user
- containing a hashtag
- or combining any of these options together
For whatever reason, my personal blog has much more traffic than PXL Blog. Maybe it’s the crazy YouTube videos? Or the shameless ramblings during the wee hours fixing bugs? Whatever the case may be, I figured I’d blog twice about Attest 3 being released today. If there’s anything I like more than writing a blog post about something cool, it’s writing two blog posts about said cool thing
You can read the full stats on Attest at the PXL Blog. Go and download Attest 3, get certified, make fun of your iPhone dev buddies when you’re pumping out AIR for Android apps 10 times faster, collect your million dollar yearly salary (alright maybe that’s a stretch?), rinse and repeat for Flex 5 we’ll leave the light on for you.
Enjoy! P.S. More fun to come later in the week I have to say, it was kind of cool that Attest leaked out a little earlier than planned – ha! I’ll show you why soon.