I actually took this from production code!

I’ve had it with events in ActionScript 3! They are annoying to structure, annoying to extend, annoying to dispatch but most importantly annoying to consume – and I consume events a lot more than write or dispatch my own.

But! The idea of listening for stuff I really do like. I have some ideas about how this could be done a lot easier. Oh, and please stick around until the very end of this post.

Background

For those who can’t remember exactly, events in AS3 are consumed by listening for certain events and passing a function, that will be called when this event occurs. The function will always be invoked with the event type, that you listen for – and only that argument will be given to the callback. You cannot define extra arguments in any way or not accept the event argument. Let’s for example listen for when the use clicks a button – which is the MouseEvent.CLICK event (of type MouseEvent of course):

public function init():void {
  var myButton:Sprite = new Sprite();
  ...
  myButton.addEventListener(MouseEvent.CLICK, buttonPressed);
  ...
}
private function buttonPressed(me:MouseEvent):void {
  trace("the button has been pressed, hurray");
}

We abidingly accept the me:MouseEvent argument even though we don’t intend to use it.

The event object has information about the event, about who sent it, information related to the bubbling nature of events (that very few people ever use in ActionScript 3) and additional specific attributes only relevant for specific events. For instance, if we have several buttons representing different related actions, we can examine the event.target

private var selectRed:ColorButton;
private var selectGreen:ColorButton ;
private var selectBlue:ColorButton;
public function init():void {
  ...
  selectRed.addEventListener(MouseEvent.CLICK, selectColor);
  selectGreen.addEventListener(MouseEvent.CLICK, selectColor);
  selectBlue.addEventListener(MouseEvent.CLICK, selectColor);
  ...
}
private function selectColor(me:MouseEvent):void {
  var color:ColorButton = me.target as ColorButton;
  if (!color) {
    throw new Error("color selected was not actually a color");
  }
  switch (color) {
    case selectRed: trace("you chose a red Papa Smurf"); break;
    case selectGreen: trace("you chose a green Papa Smurf"); break;
    case selectBlue: trace("you chose a blue Papa Smurf"); break;
  }
}

Here, we do use the MouseEvent-object, but we cast the target property to the type we expect it to have and then we need to check, if the cast went well. Because, technically we could have used the same function as a listener for something else somewhere else (even though we know we didn't) and thus target could have been something entirely different.

Personal experiences

I've just checked a recent, larger project with 185 (home-made) classes. In general I try to minimize my event usage, but a lot of things I have to use events for event though I don't really need them, so I ran a simple script counting how many times I had a function that took an event as an argument, and how many of these actually used the event object. The result was 121 functions accepting an event as argument (10 of those had default null values), and in only 4 of those I actually used the event argument (one of them a KeyboardEvent, the others were all the same home-made PageEvent). 83 of the events accepted were MouseEvents (which is no surprise), and never was the me:MouseEvent variable used in the function body.

Then, I tested an even earlier project from before I started minimizing event usage (almost maximized it back then). It consisted of 50 (home-made) classes. It had 113 functions (a lot more per class than the above) accepting event arguments (16 of those defaulting to null) and 74 of those were MouseEvents. And this time around, I used the event argument 25 times, but 18 of these usages were accessing event.target or event.data and casting it to the right class. Thus, yes I did use the event argument in some cases (22% of the time I accepted an argument), but in most of them I still had to do manual casting of the event.target (or event.data) attribute to get the type I knew I was accessing. This leaves only 7 "true" usages or about 6%. Please see the background section about why using the event object for casting only just moves the problem around and makes the code even more verbose.

Dream scenario

So, what would I like instead? Something intelligent, that allows me to accept the arguments I need when I need them. For instance, take this snippet here:

private var close:CloseButton;
public function init():void {
  close.addEventListener(MouseEvent.CLICK, closeDialog);
}
private function closeDialog():void {
  someDialog.fadeToOblivion();
}

It is simple, I do not need any argument, so I do not expect one.

A often used situation is when you have several instances of the same type and attach the same listener to all of these, then you use the event argument's target attribute for switching on which instance was invoked and handling the result correspondingly:

private var downloadLowRes:DownloadButton;
private var downloadMediumRes:DownloadButton;
private var downloadHighRes:DownloadButton;
public function init():void {
  downloadLowRes.addEventListener(MouseEvent.CLICK, download);
  downloadMediumRes.addEventListener(MouseEvent.CLICK, download);
  downloadHighRes.addEventListener(MouseEvent.CLICK, download);
}
private function download(db:DownloadButton):void {
  switch (db) {
    case downloadLowRes: open("file_360p.avi"); break;
    case downloadMediumRes: open("file_720p.avi"); break;
    case downloadHighRes: open("file_1080p.avi"); break;
  }
}

The function expects a reference to the button clicked - not to an event, who references the button clicked, because only the actual button reference is necessary.

Finally, a more elaborate example of different other component listeners expecting just what they need and nothing else:

public function init():void {
  // listen for selections in a dropdown
  countryDropdown.addEventListener(Event.SELECT, selectCountry);
 
  // listen for checkbox changes
  acceptTermsCheckbox.addEventListener(Event.CHANGE, acceptTerms);
 
  // listen for focus changes between password input fields
  passwordInput.addEventListener(FocusEvent.FOCUS_OUT, checkPasswords);
  passwordConfirmInput.addEventListener(FocusEvent.FOCUS_OUT, checkPasswords);
 
  // listen for three different radio buttons changing
  languageDanish.addEventListener(Event.SELECT, selectLanguage);
  languageSwedish.addEventListener(Event.SELECT, selectLanguage);
  languageNorwegian.addEventListener(Event.SELECT, selectLanguage);
 
  // listen for submit button presses
  submitButton.addEventListener(MouseEvent.CLICK, submit):
}
private function selectCountry(country:String):void {
  selectedCountry = country;
}
private function acceptTerms(accepted:Boolean):void {
  termsAccepted = accepted;
}
private function checkPassword(fe:FocusEvent):void {
  if (!(fe.relatedObject in [passwordInput, passwordConfirmInput])) {
    // focus moved away from either input field
    // show mismatch alert if texts are not the same
    passwordMismatchAlert.visible = passwordInput.text !== passwordConfirmInput.text;
  }
}
private function selectLanguage(language:LanguageRadioButton):void {
  switch (language) {
    case languageDanish: load("texts_da.xml"); break;
    case languageSwedish: load("texts_se.xml"); break;
    case languageNorwegian: load("texts_no.xml"); break;
  }
}
private function submit():void {
  sendForm(withParameters);
}

One notable example among the above is, that if an event is needed, you can always have it. I only dislike events, when I don't need them but have to accept them anyway. When I actually need it, they do come quite handy - like the FocusEvent.relatedObject used in the above example.

Announcement

Actually, I have made the above work! It is a dirty, dirty triple-hack, but it feels quite sweet to use on both ends. I need to clean it up a lot, need to come up with a good name for it and need to benchmark it to see, that it doesn't kill performance (too much).

So please, stay tuned. But do not fear commenting on the above ideas anyway.

Related posts:

1. Link sharing spam on Facebook

Anyone can add the new like functionality to their website – as I have in the right column just below the share options. And as you can see on the front page in the “recommendations” box, someone likes (mostly me for this purpose) different parts of my website. But what is the difference between the likes on my page and the likes of IMDb movies like The Godfather, which has 741 likes at current?

Well, one major difference is that I can “tag” The Godfather in my status, but not pages from my website (here trying to tag .

And it is not just a question of my website being very small and with few interactions, because if I create a like button for an external website such as the video Conservative Libertarian from The Daily Show:

Because, even though 25,069 people like this video alongside me (yes, it really has that many likes!), it still cannot be tagged:

Further more, Facebook just today launched, that pages are integrated much nicer on your user info tab including former and present employers, educational institutions, cities etc as well as organizing all the pages you like – internal and external. Some partner external pages you like are correctly displayed in the categories where they belong – e.g. movies and television series:

But other external pages that you like are now not displayed at all (they were yesterday) – including external partner pages like youtube videos or CNN articles. It does make sense though, as both these are temporary, but what if you have a website of movie recommendations, wouldn’t it be nice, that if a user liked one these individual posts, it would show up in the user’s “movies” info section?

So, is there any other difference between being a partner website and just a regular website other than the inability to tag the pages and not be able to have them shown on your info tab?

Related posts:

1. Link sharing spam on Facebook
2. Facebook Notes and Images for Competition Results – January 2010 Ideas
3. Vimeo highly vulnerable to CSRF attacks – now fixed

The famous large flat thing slightly more useful than a rock

Here at Konstellation, we just launched the PageGangster for mobile devices including iPad, iPhone, iPod touch and Android. I developed the clientside for this in JavaScript and we launched it with automatic user agent detection serverside. But this had some problems.

I read some info about this and conclude, that some iPad user agent strings include the word “iPhone” and some users of all types of devices fake their user agent strings.

But then I read on the above link, that no matter what, the navigator.platform attribute would always be set to the right type of device. So in the regular web version of the publication viewer we have now (which uses Flash), we have added a JavaScript detecting if the serverside script did not redirect the client properly:

if (navigator && navigator.platform && navigator.platform.match(/^(iPad|iPod|iPhone)$/)) {
	location.replace(location.href+"?force-mobile");
}

It seems simple, but solves the problem of some users seeing the dreaded blue box instead of their publication optimized for their device.

On another node, this experience of developing a web application for the iPad/iPhone was very rewarding and I gained many insights, which might spawn other posts. And if you have any questions about it in any way, feel free to ask here – but please do not submit bug reports about the PageGangster for mobile – do that via info@pagegangster.com instead.

Related posts:

1. The iPhone developer boycott in the works
2. Coordinate-Proxy – January 2010 Ideas
3. App Idea Store – January 2010 Ideas

As has been said over and over, allow-all cross-domain policy files should never be used on domains, where users log on. This leaves the site open for CSRF attacks from flash clients on different domains, that can load pages from the target domain utilizing the user’s automated log-in and thus the flash load’s the pages, like the user himself would. This not only allows the flash file to (without the user knowing it) load all his private information from the target site, but potentially also post data to the site, which could include updating the user’s password, email, profile or in worse circumstances add/remove content or even make purchases, if the target site has any feature like that.

This has been done against large sites like Facebook, MySpace, Adobe and Youtube – the latter was ironically documented via a video on Vimeo by Jeremiah Grossman.

In Vimeo’s case, you can “only” upload videos, but an attacker could actually perform any action on the user’s behalf, that the user himself could – including changing the user’s bio, add/remove videos, comment on/like other videos etc. I made a small, seemingly innocent page, that included a hidden flash element, which first loaded the user’s info from vimeo.com/settings/personal and then re-posted this info back to the same page adding an extra line to the bio – namely “You have been bwned”, as it can seen on my vimeo profile.

Someone at vimeo has clearly seen this demo, (Julia Quinn has indeed) and now the cross-domain policy only allows *.vimeo.com (the new file is served with a Last-Modified timestamp of Thu, 11 Feb 2010 23:32:05 GMT, so the change is only an hour old). The strange thing is, that if you go back via the Wayback Machine from archive.org, you can see, that they had much better security back in 2007 and 2008 (html render fails, but view source), so I have no idea how such a relaxed policy suddenly appeared on their site. Google’s cache still show the allow-all policy as it dates back to January 20th (again, view source to see contents).

I found this while playing around attempting to load videos from Vimeo directly in a custom FLV-player on a different host than vimeo.com and found that this was actually possible, as all videos from their site are hosted from av.vimeo.com and this has an allow-all cross-domain policy. And this makes sense, as this domain is only used for serving videos and nothing else – no cookies or authentication info shared to this domain.

I haven’t heard from Vimeo yet – neither stating that they are looking at the issue nor that it has been fixed. I only post this after now seeing, that it has been fixed.

Related posts:

1. Sys-Con once again attacks Aral Balkan with stupidity and ignorance
2. Link sharing spam on Facebook
3. Re-Youtube – January 2010 Ideas

Creating cool charts displaying the frequency of articles about Obama vs. McCain or comparing the articles about Obama in his first year vs. previous presidents NYT coverage in their first year are common and quite easy to do. But as previously explained about Twitter Trends, you cannot find what you don’t know you’re looking for. Let’s say we want to see how many articles are posted in NYT about Democrats vs. Republicans. Well, you could search for popular names from both parties, or you could hope that the writers have tagged their articles correctly.

But we can do better than that, as the Wikipedia category system will give us names of most politicians from both parties. Thus we can use these lists to create large queries about all Democrats vs. all Republicans and receive these numbers correctly.

Why?

This is a classic mashup displaying the power of combining commercial content (NYT articles) with crowd-sourced information (Wikipedia CatScanner) with generalized tools (charting API’s like Google Charts) with little effort for huge results. And this puts cretaing complicated charts back in the hands of everyone, not just the few who are good at both API’s and PhotoShop.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. Comment On Everything – January 2010 Ideas
2. Google Docs Application – January 2010 Ideas
3. Social Traffic Analyzer – January 2010 Ideas

There are of course a lot of legal issues, and such a service should probably obey robots.txt. And there should be a very clear opt-out possibility for websites that have been targeted in user-contributed additions – maybe even moderation before the services are publicly available. It should not be seen as an attack vector, as a proxy method for illegal purposes or anything like that, but simply as a way of “helping” free information to be used freely.

Why?

A lot of data on the web is hidden in the so-called “deep web” behind forms or in inaccessible parts of websites. With a service like the above-mentioned, this would suddenly not only become visible and indexable, but even queryable.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. Coordinate-Proxy – January 2010 Ideas
2. Open Data – January 2010 Ideas
3. Social Subway – January 2010 Ideas

The idea is to create a site enabling users to create infographics of the simplest kind initially, but then expand this to even more complex ones. For starters, it could allow users to create tables of data defining row and column labels and then selecting icons, colors and values for cells and having this displayed as larger and smaller icons according to the values – like this chart of the “deadliest drugs”. And allowing people to color-code maps of countries, cities or states according to some data would be quite simple to do as well – like this map of the origins and relationships of European languages.

But more important than simply creating cool visualizations, each infographic has an input page. This page can only be edited by the original creator of the infographic, but it includes direct links to sources of information used. The site should use a simple url structure (inspired by bit.ly), where the short-code would give the actual image, but with a + added (like http://bit.ly/365ideas+) it would be a link to the page describing all this background data.

And now comes the collaborative part: While only the creator can edit the data for the published infographic, anyone can copy the data to branch it as their own new infographic. These relationships will then also be displayed on the about page, as in “this is a spin-off of X and has Y spin-offs of its own”. Somewhat like the very nice ActionScript-programming website wonderfl. Here you can e.g. see that this creation of 250,000 particles is a spin-off from another simulation and has itself spun off into new simulations.

In time, this could be extended heavily and should of course have a public API for creating infographics easily and freely. New types of infographics could be added along with more complex editors allowing you to play around with the data as you see fit. It should be free to do and should not require complex knowledge of Illustrator or Photoshop.

This idea about letting others built on your own ideas could actually be implemented by many sites. The new Firefox 3.6 has “personas”, which is a very light theme engine – that most importantly does not require restart! But why didn’t the developers add a very fast and quick branching mechanism? If you found a cool persona, but didn’t like the color of the top-bar – just branch it, change the top-bar color and publish as a new persona (with credit where credit is due of course linking back to the original).

Why?

Simply: Infographics to the people! I’m not suggesting, that the creators of the coolest infographics aren’t brilliant. But they’re in the business because they both know how to find the data, how to present it and how to use the programs needed to create them. Let’s take the software knowledge part out of the equation and allow anyone with ideas and info to visualize it. And let’s do it openly and collaborate, not just publish a PNG and kill innovation.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. App Idea Store – January 2010 Ideas
2. Open Data – January 2010 Ideas
3. NYT Article Trend Charts – January 2010 Ideas

It is a very simple idea, but the idea is to use profile tagging in a new way to indicate relationships to the displayed information in a way, that the users actually feel related to this. The great thing about using tagging is, that it can be done without the user has to accept it and it will be auto-posted to his friends’ news feeds. But given that it can be done without asking the user, it should only be done if it is actually relevant for the user and not done just to get a viral effect and annoy users.

Why?

It is a new way to use the Facebook platform for viral effects. It’s quite simple and does not require a lot of programming as it uses simple, existing features.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. A Twitter Gaming Mechanic – January 2010 Ideas
2. Game Console Progress API for Social Connectivity – January 2010 Ideas
3. Game of Life – January 2010 Ideas

When you consider buying a car, you don’t make the decision instantly. You look at it on the web several times, you discuss it with friends and family etc. But imagine that the dealer website added a private comments box, that would initially be empty, but as soon as you started adding comments, you could share this version of the page, with your comments, to everyone else. A bit like the wish list concept from Amazon, but giving others the opportunity to weigh in on your decision if you gave them the link. Then all comments about whether or not to buy this car, pros and cons, other possibilities etc. would be in one place, and not spread around in emails discussing this potential requisition.

This could easily be used by e.g. Amazon, ebay or similar companies. It should just be clearly visible, that this is private comments, that neither the dealer nor the seller will ever see. It is only for your own benefit to keep the discussion in one place between you and friends and family.

Why?

If you control the discussion, it is more likely that the user returns to your site, to keep the discussion going. It is a facilitator of making educated requisitions, but it ensures that this discussion takes place on your website.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. Comment On Everything – January 2010 Ideas
2. Browser Snapshot Sharing – January 2010 Ideas
3. Game of Life – January 2010 Ideas

I for one bashed Waveboard, when it came out, because it was simply Apple Safari wrapped in a Mac OS X application. But, recently I tried it again, as it had added Growl support, which means I was easily alerted to when new info was available in any of my waves – this made it feel much more like a mail application, because it was its own program on my MacBook, that I could switch program to and be notified about even though using billions of tabs in my “regular” browsing experience.

So, my suggestion is simply to anyone out there (I reckon it might actually be infinitely simple): do this with Google Docs and if possible, add similar Growl integration as has been done with the Waveboard application, then Google Docs would actually start to seem like a “real” program in itself.

Why?

Because I need it. I might be alone, but I doubt it. And I am pretty sure this is very simple, but it would be really useful.

What’s next?

Do with this idea whatever you like – expand, implement, trash or forget. Just remember, that if you use it in anyway make sure to attribute me according to the Creative Commons Attribution 3.0 License, that all these 365 Social Ideas are published under.

Related posts:

1. Comment On Everything – January 2010 Ideas
2. Appcelerator – January 2010 Ideas
3. NYT Article Trend Charts – January 2010 Ideas