<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
            <atom:link href="http://blog.classsoftware.com/rss.cfm?mode=full" rel="self" type="application/rss+xml" />
			<title>Class Software - ArrayCollection</title>
			<link>http://blog.classsoftware.com/index.cfm</link>
			<description>Web technologies and applications focusing on ColdFusion, Flex and Flash.</description>
			<image>
    			<title>Class Software</title>
    			<url>http://www.classsoftware.com/images/logosm.gif</url>
    			<link>http://blog.classsoftware.com/index.cfm</link>
			</image>			
			<language>en-us</language>
			<pubDate>Fri, 10 Sep 2010 00:08:29 +1000</pubDate>
			<lastBuildDate>Mon, 18 Jun 2007 18:59:00 +1000</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>justin@classsoftware.com (Justin Mclean)</managingEditor>
			<webMaster>justin@classsoftware.com (Justin Mclean)</webMaster>
				
			
			
			
			
			<item>
				<title>Flex Type Ahead List Boxes</title>
				<link>http://blog.classsoftware.com/index.cfm/2007/6/18/Flex-Type-Ahead-List-Boxes</link>
				<description>
				
				When a user types a character the default behaviour of a list box is to jump to the first item that starts with that character. This is fine for small lists but for a long list of items it&apos;s not very useful. A better solution would be if the list box remembered what the user typed and keep looking for matches on the second character, the third character, etc etc.
				 [More]
				</description>
						
				
				<category>ArrayCollection</category>				
				
				<category>Flex</category>				
				
				<category>List</category>				
				
				<pubDate>Mon, 18 Jun 2007 18:59:00 +1000</pubDate>
				<guid>http://blog.classsoftware.com/index.cfm/2007/6/18/Flex-Type-Ahead-List-Boxes</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Flex Filtering Long Lists</title>
				<link>http://blog.classsoftware.com/index.cfm/2007/6/14/Flex-Filtering-Long-Lists</link>
				<description>
				
				If you have a list box with a large number of items in it it can be hard for someone to find the item in the list that they need. One way around this is you add a filter on the list box.

Here&apos;s how it&apos;s done.
				 [More]
				</description>
						
				
				<category>ArrayCollection</category>				
				
				<category>Flex</category>				
				
				<category>List</category>				
				
				<pubDate>Thu, 14 Jun 2007 21:40:00 +1000</pubDate>
				<guid>http://blog.classsoftware.com/index.cfm/2007/6/14/Flex-Filtering-Long-Lists</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Flex Webservices XML and Array Conversion</title>
				<link>http://blog.classsoftware.com/index.cfm/2007/5/24/Flex-Webservices-XML-and-Array-Conversion</link>
				<description>
				
				I&apos;m currently working on a project involving simple webservices, the webservices return plain XML rather than using SOAP. Personally I prefer SOAP as you get a well defined interface but on this project it was felt that plain XML was less verbose, more efficient and easy to code server side.

Anyway one of the issues with returning XML via HTTPService calls is that when flex converts the XML to objects it treats it as array if there&apos;s more than one item of the same name but as a single item (ie not an array) if there&apos;s only one item of the same name.

This causes databinding to datagrids or lists to fail.

So how do you get around this issue?
				 [More]
				</description>
						
				
				<category>XML</category>				
				
				<category>DataBinding</category>				
				
				<category>Flex</category>				
				
				<category>ArrayCollection</category>				
				
				<pubDate>Thu, 24 May 2007 17:44:00 +1000</pubDate>
				<guid>http://blog.classsoftware.com/index.cfm/2007/5/24/Flex-Webservices-XML-and-Array-Conversion</guid>
				
			</item>
			
		 	
			</channel></rss>