One of the things I love about Flex is how extensible it can be. You are able to make composite components to do almost anything you want using out of the box components. However, if you really want to take advantage of its power, it helps to have a good or in depth knowing of the interfaces that come with it. The reason to proclaim the importance is that using these interfaces, you will be able to create extremely light weight components, but you will be able to make them do whatever you want (in a programming sense of the phrase).
There are, of course, quite a few different interfaces. I have looked through them and picked out five interfaces that I consider to be the more important ones. For each, I will give a brief explanation of why they are important and where you would normally use them.
Best Practices, Flex, Learn This
Love it or hate it, its hard to ignore Twitters recent explosion in popularity. Not only are they super popular to the masses, but they are nice enough to give us an API to use in order to create our own twitter applications. I don’t use it too much, but I figured it would be worth checking out at least from an API stand point.
Turns out, the API is actually just a series of webservice calls that just return a json or atom string, so it is extremely easy to use (and it explains the mass amount of twitter programs out there). I don’t feel it would be too beneficial to create a bunch of ‘This is how you search for people’, ‘This is how you do a post’, so I decided to turn this into a mashup between this and google maps.
What I decided to do an article on is how to take twitters geocoded search feature and place them on a map within google. This article will explain how to call Twitters search service, parse that and then using Googles Geocoder, plot where those users are twittering from.
Flex, Google Maps API, tutorial
In one of my previous articles, I spoke about how to use Fabrication, or at least one portion of Fabrication (respondTo and reactTo). Given that there are other really cool things about Fabricaiton, I felt it deserved some more attention. One thing Fabrication supports are interceptors. Interceptors allow you to stop the normal flow of your notification to your commands or mediators. You can stop the notification, alter them, even send a different notification in its place. In this article, I will be focusing on a few different uses for interceptors.
How many times have you hopped into Flex’s source code only to see the modifier “mx_internal”? No public, private or protected, just mx_internal. It is everywhere in there. But what is it? Turns out, according to Adobe, it is a namespace used to flag functions and properties within the framework that may change in future releases. Obviously, since they might change, Adobe, with all its motherly goodness, hides these properties and functions from us behind this namespace. This does not mean we cannot access them though. We just have to jump through a few small loops. This article will go over how and when to use mx_internal, but also what to be careful about when using them.
Best Practices, Flex, Opinion, Random Notes
It is hard to deny that the Google Maps API has a lot of built in functionality to it. I enjoyed writing the last article and I felt it was time to get into it a little more. In my last last article on the API, I focused primarily on how to add a marker to the map and also how to create a custom infoWindow. This article’s main topic will be on how to plot PolyLines on a map, how to get the distance between them, and using Markers to had a little bit more usability to your application.
Flex, Google Maps API, tutorial