<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9" -->
<rss version="0.92">
<channel>
	<title>compactcode</title>
	<link>http://www.compactcode.com</link>
	<description>keeping software simple</description>
	<lastBuildDate>Fri, 30 Apr 2010 06:42:41 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Parallel processing and Google collections</title>
		<description><![CDATA[If you have been using google collections lately, chances are you will have been using one of the transform static methods available to you.

  List&#60;String&#62; source = Lists.newArrayList&#40;&#34;a&#34;, &#34;b&#34;, &#34;c&#34;&#41;; 	
  ...
  Iterables.transform&#40;source, Functions.toInt&#40;&#41;&#41;;

By default the above transform will execute your list transformations on the current thread. While this approach works well [...]]]></description>
		<link>http://www.compactcode.com/2010/04/parallel-processing-and-google-collections/</link>
			</item>
	<item>
		<title>Google collections and JavaBeans</title>
		<description><![CDATA[In this article I want to show you some useful techniques to simplify the process of using google collections with your JavaBeans. 
Examples will be based around the manipulation of the following customer data.

  public class Customer &#123;
    private String name;
    public Customer&#40;String name&#41; &#123;
    [...]]]></description>
		<link>http://www.compactcode.com/2010/04/google-collections-and-javabeans/</link>
			</item>
	<item>
		<title>Google collections made easier</title>
		<description><![CDATA[Due to legal/ethical objections around trademark violation the project presented here has been renamed to compacted-collections.
I spent a few hours over the last two weeks working on a little project that aims to make google collections even easier to use. I set out to make a thin wrapper that mimics the way the ruby programming [...]]]></description>
		<link>http://www.compactcode.com/2010/04/google-collections-made-easier/</link>
			</item>
	<item>
		<title>Introducing Compaction</title>
		<description><![CDATA[I've been very quiet on the blogging front for the past few weeks. Although I would like to tell you that I have been relaxing on the beach somewhere, sipping cocktails and working a tan, it would be a lie. I have actually been spending my spare time creating a new open source project that [...]]]></description>
		<link>http://www.compactcode.com/2009/09/introducing-compaction/</link>
			</item>
	<item>
		<title>Flex Validation – Future Directions</title>
		<description><![CDATA[I'm currently working on creating a small flex library with the goal of simplifying the task of implementing common user interface logic. One of the areas that is of particular interest to me is validation. Although the built in flex validators are useful they lack some important functionality needed to use them in any non [...]]]></description>
		<link>http://www.compactcode.com/2009/09/flex-validation-%e2%80%93-future-directions/</link>
			</item>
	<item>
		<title>Unit Testing Flex &#8211; Mocking</title>
		<description><![CDATA[If you have experimented with unit testing either recently or in the past you will be aware that sometimes it can get difficult. There are many challenges you might encounter including the following:

You need to ensure something happened, without going into detail.
You have to do too much to write a single test.
You need to test [...]]]></description>
		<link>http://www.compactcode.com/2009/08/unit-testing-flex-mocking/</link>
			</item>
	<item>
		<title>Unit Testing Flex &#8211; Alerts</title>
		<description><![CDATA[If you ever have a serious attempt at unit testing Flex code sooner or later you are going to need to test something that involves user confirmation. Lets take a simple example of deleting critical business information, the last thing we want is to have a user accidently click the wrong button and delete something [...]]]></description>
		<link>http://www.compactcode.com/2009/08/flex-unit-testing-alerts/</link>
			</item>
	<item>
		<title>Unit Testing Flex &#8211; States</title>
		<description><![CDATA[This is a quick post to share a solution to a problem I discovered while trying to unit some test some Flex code that involved states. 
FormWithStates.as

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
&#60;?xml version=&#34;1.0&#34; encoding=&#34;utf-8&#34;?&#62;
&#60;mx:HBox xmlns:mx=&#34;http://www.adobe.com/2006/mxml&#34;&#62;
  &#60;mx:states&#62;
    &#60;mx:State name=&#34;advanced&#34;&#62;
      &#60;mx:AddChild relativeTo=&#34;{nameItem}&#34; position=&#34;after&#34;&#62;
        &#60;mx:FormItem label=&#34;Age&#34;&#62;
  [...]]]></description>
		<link>http://www.compactcode.com/2009/08/unit-testing-flex-states/</link>
			</item>
	<item>
		<title>Flex Snippet &#8211; Automatic Dirty Checking</title>
		<description><![CDATA[In order to prepare for an upcoming tutorial on flex unit testing I need to present a couple of simple concepts that I can build upon to create some useful example code.
The first of these is the concept of automatic dirty checking. You can use dirty checking to determine if any properties on given object [...]]]></description>
		<link>http://www.compactcode.com/2009/08/flex-snippet-automatic-dirty-checking/</link>
			</item>
	<item>
		<title>Unit Testing Flex &#8211; More MXML</title>
		<description><![CDATA[This is a continuation of my previous post. Today I am going to show you three more simple techniques you can use to unit test your mxml:

Button Clicks
List Selection
DataGrid Rendering 

Button Clicks
ClickForm.mxml

1
2
3
4
5
6
7
8
9
10
&#60;?xml version=&#34;1.0&#34; encoding=&#34;utf-8&#34;?&#62;
&#60;mx:HBox 
    xmlns:mx=&#34;http://www.adobe.com/2006/mxml&#34; 
    xmlns:compact=&#34;com.compact.*&#34;&#62;
    &#60;compact:ClickModel id=&#34;model&#34; /&#62;
    &#60;mx:Button 
 [...]]]></description>
		<link>http://www.compactcode.com/2009/08/unit-testing-flex-more-mxml/</link>
			</item>
</channel>
</rss>
