Dareville library for Facebook Graph APIs
Github library
ASDocs

It takes 2 parameters: First is the speed in kbytes; Second is the port to throttle (I usually just use 80)

throttle()
{
	sudo ipfw pipe 1 config bw $1KByte/s &&
	sudo ipfw add 1 pipe 1 src-port $2
}

rmthrottle()
{
	sudo ipfw delete 1
}

Example terminal output:

...$ throttle 150 80
Password:
00001 pipe 1 ip from any 80 to any
...$ rmthrottle

/**
 * ------------------------------------------------------------
 * Copyright (c) 2010 Some Company.
 * This software is the proprietary information of Some Company
 * All Right Reserved.
 * ------------------------------------------------------------
 *
 * SVN revision information:
 * @version $Revision: 82 $:
 * @author	$Author: kris $:
 * @date	$Date: 2010-07-10 08:36:02 +0200 (Sat, 10 Jul 2010) $:
 */
package com.somecompany.common.somepackage
{
	import flash.display.MovieClip;

	/**
	 * SomeClass description
	 *
	 * @author krisrange
	 */
	public function SomeClass
		extends MovieClip
	{
		/**
		 * Constructor
		 */
		public function SomeClass()
		{
			super();
		}
	}
}

As you can see, the SVN revision version, last modified author and last modified date show up in our headers. This is really important as a developer can look at the header and quickly know who last modified the file and who to talk to in case the initial author of the file may not be the developer who last updated functionality.

I will be writing this from the perspective of working on MacOS but most of this information is transferrable directly to a Windows machine except a few things like directory structures.

We need to make sure that files are setup to have their properties changed. The best thing to do is to change this globally for new files/repositories and then go back into any previous projects you have worked on and recursively loop through and add this functionality.

Modifying the Global Setting:

On MacOS, go into your home directory and open the “Config” file that lives in the hidden folder “.subversion”. Once you have this text file opened, uncomment the “enable_auto_props” variable in the “[miscellany]” section and set it’s value to “yes”. Then add the file types you would like include in the “[auto-props]” section with the value of “svn:keywords=Date Revision Author Id”. See sample below where I’ve set auto_props to modify all *.as and *.mxml files:

[miscellany]
### Automatic properties are defined in the section 'auto-props'.
enable-auto-props = yes

### Section for configuring automatic properties.
[auto-props]
*.as = svn:keywords=Date Revision Author Id
*.mxml = svn:keywords=Date Revision Author Id

Modifying Previous Projects

In order for previous projects to gain access to this information, we need to set the properties on all the files we have already committed to set the properties on themselves when they are committed into our repositories. To do this, just type the following command for every file type that you want to have auto_props enabled for.

find * -type f -name '*.as' -exec svn propset svn:keywords "Date Revision Author Id" {}  \;

Getting the Values to Show Up

After that is all setup, just insert the values in your document based on the corresponding ID. So for example, if you wanted to insert the Last Modified Author, insert it like below and SVN will replace the content inbetween the word “Author” and “$:” with the actual value:

$Author: $:

For more information on what keywords/properties are available, there is good documentation from Subversion.

SpotifyUtil

Here is an example of how to use the method which will convert the link variable below to “spotify:user:user_name:playlist:3WbWswJtOPIdKBQmZs9pGr”:

var link : String = "http://open.spotify.com/user/user_name/playlist/3WbWswJtOPIdKBQmZs9pGr";

var validUrl : String = SpotifyUtil.validatePlaylist( link, SpotifyUtil.URL_FORMAT_SPOTIFY );

if( validUrl )
{
	trace( link );
}

What we wanted to do was to use the same build SWF targets but for both situations without having to modify our process. Our solution was a nifty trick that used JavaScript inside ANT. I had never seen this technique before but some searching for a solution led us in this direction.

As you can see below, we have two initial targets, one which builds for local file system and one which builds for network use. We can then run either target first, which sets a property in our ANT file and then run our normal SWF build targets as normal, with this property set to the “use-network” property. Really looking forward to exploring some more complexities with JavaScript integration (as well as other languages from what I’ve read).

<target name="compile_local">
	<script language="javascript">
	<![CDATA[
		presenter.setProperty( "use-network", "false" );
	]]>
	</script>
</target>
<target name="compile_network">
	<script language="javascript">
	<![CDATA[
		presenter.setProperty( "use-network", "true" );
	]]>
	</script>
</target>

SNOOP 4:20

Ok, lets get started! First, all of these instructions assumes you have a good knowledge in how ANT works. It also assumes you will be building an ActionScript or Flex project. In this case, we are going to be creating a custom ContextMenu but you can really do this for anything. This will allow anyone us to see the version numbers when they right click on our application.

Ok, so how is this done? Open up your build.properties file for the project and add the following lines:

project.major	  = 1
project.minor     = 0
project.revision  = 0
project.version   = ${project.major}.${project.minor}.${project.revision}

The projet will act as our properties for figuring out the project major, minor and revision. These could probably be automated in some way but for now I am ok with manually setting these values since I will know when these versions change. We will also need to include a build number into our build so just add the following before anything else into your build file. Also note that if this file does not exist, ANT will create it for you so no need to concern yourself with what the contents are. Let ANT do the dirty work!

<buildnumber file="${basedir}/build/build.number" />

Next, we are going to want to copy our classes to a temporary directory so that we can modify them without harming the source. As you can see I have some temp.outdir and classes.dir properties

<target name="copyClasses" description="Creates a temporary directory where the code will be duplicated so we can modify and build without harming the original files">
	<mkdir dir="${temp.outdir}" />
	<copy todir="${temp.outdir}">
		<fileset dir="${classes.dir}"/>
	</copy>
</target>

Now that our classes are copied, we need to do a search on them for particular strings that we will end up replacing with the project version. In my case, I have a ContextMenu class which has a string value defined as “[PROJECT_VERSION_NUMBER]” so I do a regular expression replace in ANT to find that value and replace it.

<target name="projectversion" description="">
	<replaceregexp match="[PROJECT_VERSION_NUMBER]" replace="${project.fullname} : ${project.version}.${build.number}" flags="gs">
		<fileset dir="${temp.outdir}" includes="**/*.as"/>
	</replaceregexp>
</target>

And that is it. Now we have our build number plus project version automatically showing up in our application.

In the meantime, please check out my updated portfolio section!