I blogged this on the MXNA weblog yesterday, but just to make sure the word is out, I’ll make a quick post here, too. Yesterday, I installed a new version of the MXNA Flash Services with a lot of good improvements. The post on the MXNA weblog contains the details.
Anything else you want to see? Has anyone built a Flash Lite app yet? I know there must be some under development because I got a lot of good feedback on the first version of the Flash Servies, so hopefully this version has everything you need.
MXNA web services have been around for a long time, but they won’t work everywhere. For instance, Flash Lite applications can’t use web services. And sometimes web services can be overkill for small amounts of information that you want to retrieve, parse, and render very quickly. The answer is the new MXNA Flash Services.
Flash Services are very much in alpha, but they seem mature enough to start playing around with. Rather than using XML, Flash Services return data as query strings, or application/x-www-form-urlencoded which means they work perfectly with the Flash loadVariables function, and with the LoadVars object. Flash Services are primarily intended for Flash Lite applications, but can be used by any client preferring a more streamlined data service.
Check out the Flash Services documentation for more information, and let me know if you have any questions or comments. And keep in mind that I will be making changes to the APIs based on feedback, so anything you build could get temporarily broken.
Note: It looks like the What’s
New contest is over now, so I
can go ahead give away one of the answers. Mike and I will be announcing the winners
As a blogger in the Macromedia community, how do you know what kinds of posts
are more likely to get people’s attention? How do you know how your post on the
object oriented nature of ColdFusion components compares with your post examining
the merits of crunchy peanut butter versus smooth?
The new MXNA 2.0 Click Reports chart the popularity of your last 50 posts. Take
for instance. I can see that my post on Internet Explorer 7 was the most popular
It looks like I should clearly be spending more time blogging about web technologies
rather than new search engine features, or talking about PDAs. And apparently
only about 8 people care that I’ve returned from TODCON. Thanks a lot, everyone!
The blue bars on the chart indicate clicks (along the Y axis), the red line is
a moving average based on your last five posts, and the green line is your overall
average. To find your feed’s Click Report, go the the MXNA 2.0 list
of feeds, and click on the "Click
Report" link next to your feed’s name.
You might also want to check out the new views we’ve added to the "Most Popular"
pod. Now you can view the most popular posts of the last day, week, month, year,
and of all time (and get them in RSS).
As Mike Chambers recently
posted, we did a new MXNA 2.0 installation
last night with a few cool new features. If you can find them quickly, you can
win a nice Macromedia Timbuk2 bag. Check out Mike’s
post for details.
In case you haven’t noticed, the beta version of MXNA
being rolled out incrementally. Today’s increment: MXNA
Mike Chambers and I have been working on and off on the new MXNA 2.0 reports,
along with a general reporting framework, for a couple of weeks now, and I think
they turned out really well. We used Flex and the Flex charting components for
refreshing the page. The charts are
populated with data through the MXNA
2.0 web services, and can express that data
in a variety of ways as the user interacts with them. And when the user clicks
on certain parts of the chart, the relevant posts are rendered below using AJAX,
almost instantaneously. The whole experience allows for a great deal of interactivity
without a single page refresh, and with almost no waiting.
We feel that combining Flash and AJAX in this instance allows us to get the best
of both worlds, and really gives the user a unique and immediate user experience.
Flash/Flex were perfect for the charts, and really allowed us to focus on the data
and the presentation rather than the mechanics of the charts themselves. Using
AJAX to render the post data allowed us to reuse the exact same rendering code
that the rest of the application uses when displaying posts, and because it is
HTML, it allows for things like shift-clicking on links, and native browser scroll
We have several more reports in the pipeline, but we probably won’t be launching
any more this week since I’m in Las Vegas as TODCON.
If you have any ideas for specific reports that you would like to see, let
us know. We want to make sure we
are presenting the community with the most useful information we can.
If you’ve sent us any email regarding the MXNA
2.0 beta, or if you’ve submitted
your site recently, you have probably noticed that we haven’t gotten a chance to
respond. Don’t worry — we will get to every email and every submission very soon.
As you might imagine, we have been very busy for the last couple of days, but things
should be back to business as usual by the end of the week.
Anyone out there going to be in Vegas for TODCON next week? If so, drop me a line.
I arrive Sunday night.
Macromedia developer Deng Jie recently made
a post asking us to add language navigation to MXNA 2.0. In other words, he wanted
a list of languages along the right-hand side (just like categories and Smart Categories)
that you could easily click on to browse the most recent posts in that particular
language. Seemed like a good idea to us, so we added it. Check
I also added some additional RSS support in yesterday’s build. Now, whenever you
are looking at a set of data that is available as RSS (which is pretty much everything),
you’ll see a little "rss" link next to the page title. MXNA 2.0 also supports auto-discovery,
so if you’re using Firefox, you’ll notice the little RSS icon in the status bar.
For those of you who ping MXNA to let us know you have made a new post, you can
now update your ping URL to point to MXNA
2.0. Your old ping ID will work, so all
you need to do is change the host and domain from "www.markme.com" to "weblogs.macromedia.com".
(If you have any problems, let me know).
If you don’t know your ping ID, but would like to start pinging MXNA, you can send
email to email@example.com to find out
your ping ID. If you want to ping MXNA, but you can’t set up your blogging software
to ping automatically, you can use the MXNA
2.0 ping form to
do a manual ping. If you have no idea what a ping is, check out the MXNA
I want to thank everyone for all the feedback we’ve gotten on the MXNA 2.0 beta
so far. We had about 50 additional feed submissions, some great feature requests,
and even a few bug reports. MXNA 2.0 automatically emails errors to me as soon
as they occur, usually with enough information that I can get them fixed pretty
quickly, and you guys helped me uncover a couple good ones faster than any QA team
I installed a new build last night with the
- Added the Danish, Turkish, and Indonesian languages.
- Fixed a bug in mobile smart categories. If you’ve been trying to view smart
categories on your mobile device (I know you’re out there because I saw the bug
reports), they’re working now.
- Fixed a bug in the search term RSS. MXNA 2.0 lets you create
custom RSS feeds from aggregated data, including feeds based on search terms.
Yesterday search-based feeds were broken, today they are not.
- Added the number of feeds being aggregated in the header. Expect that number
to continue to rise, especially for non-English feeds.
- Removed the code that automatically focused the cursor in the search box so
you can now use the space bar or arrow keys to scroll down without having to
click on the page first.
- Fixed a bug that was causing the application to fail when rendering pages that
we can’t translate yet. Yesterday, I added our first Russian
weblog which threw
things off a bit since MXNA 2.0 does not support Russian translations yet.
Anyway, I fixed the bug on our end, and will add support for Russian translations
as soon as it’s supported by Google (our translation engine).
- Added about 50 new weblogs, most non-English. I’m really glad to be able to
include the rest of the world in MXNA 2.0.
- Worked out some kinks in the ping mechanism. After you make a new post, be sure
to ping MXNA 2.0 so
we can aggregate your work right away. You can configure
your blogging application to do the ping automatically, or you can easily do it manually just by typing
in your site’s URL.
I think that’s all. Anyway, on to today’s list of updates!
I’d like to invite you all to participate in the MXNA
2.0 beta. MXNA (Macromedia
XML News Aggregator) 2.0 is a complete rewrite of the original version of MXNA
with several new features including:
- Smart Categories.
- Support for non-English feeds.
- Localization support.
- Self-service site submission.
- Improved ping support.
- Ability to translate posts (using Google’s translation
- Ability to generate custom RSS feeds from MXNA 2.0.
- Improved search including
an advanced search option.
- Huge performance improvements.
- Improved (we think) interface.
- New design (thanks to Josh Dura).
- Much better web service API.
- More powerful mobile interface.
- Atom support.
- Pre-fetching and caching of top rated items.
You can find the new version of MXNA here:
If you are not already aggregated by MXNA, you can submit your feed
If your language is not listed, let
us know, and we’ll add it. All languages are
Keep in mind that this is a beta, which is fancy way of saying that there are
bugs to be fixed, and kinks to be worked out. Please email any issues you find
to firstname.lastname@example.org. Some additional
- The original version of MXNA will remain active for the time being, but eventually
all MXNA traffic will be redirected to MXNA 2.0. You might as well start
updating your bookmarks now.
- All new weblogs will be added to MXNA 2.0 only.
- The MXNA 1.0 web service API will be deprecated eventually in favor of the much
more comprehensive 2.0 API.
- If you have a ping URL, you will need to update it by replacing "www.markme.com"
with "weblogs.macromedia.com". Eventually pings will be redirected, but it’s
still best to start using the new URL.
- Some non-English feeds are not parsing correctly for some reason which I think
has to do with character encodings. The majority are working fine, but some are
not readable. If you have any insight into what the problem might be, let
me know. Otherwise, I’ll get it figured out and fixed during the beta period.
Thanks for helping us test, and let us know what you think.