For some reason I thought that Array.sort only worked for simple values, not objects. But reviewing the ASDocs it appears that is not the case. You can easily specify a compareFunction which should handle complex objects.

You’re right, I bet it would handle most cases.

For something really complicated then yes, I would probably create some sort of utility to change the Array. Unless I am dealing with this being on the view, where we both agree we’d go with an ArrayCollection

What would you do instead? Write your own quicksort algorithm?

For the quote at the top, it was meant to be an exaggeration as to how many early developers see Arrays vs ArrayCollection. Not that it is correct or even close to the entire story.

I agree that Arrays can be used as a point for data binding. The Flex compiler adds many arguments to the original array to be able to listen for changes from the array. Heck, in most components when you pass an Array in, the Array gets wrapped in an ArrayCollection so that the data binding can be used.

I agree also that you get sorting and filtering is in a collection, but I don’t think that you should use an ArrayCollection just to sort an array – yes I’ve seen this practice. Sorting and filtering can be something that is quickly done on the data model with a small function. Obviously the time to worry about these specific points is when you are really getting into performance tuning.

You’re right that I used the wrong words in the last example. The sorting is on the collection, but the two views are tied together using the sorting information. If you were to sort the actual Array source it would not be reflected back up the collection as the collection has it’s own virtual “view” of the data. However, if you were to filter or extract data from the original source Array, that will effect the final collection that is shared between views.

Again, sorry for an over simplification but I’m glad to see people pushing back and wanting to make sure the correct information is being shown.

You said:
“[A collection is] like an Array PLUS it has binding ”

There is no reason why Array’s can’t be used as the source for data binding. See the dayNames property of the DateChooser as one example.

You said:
Collections do have a collectionChange event, which list based classes will listen for and update display based on those changes. But, that isn’t the same as binding.

“There is nothing built into an ArrayCollection that isn’t already part of the Array.”

This is incomplete at best, wrong at worse. The sorting and filtering functionality of a Collection class are things you do not get with a simple Array. I have used the sorting functionality independent of any view components. The dayRenderers of the Flextras Calendar are sorted in order of their date before the collection is looped over and days are placed on the display.

You also say “sorting information is shared between Collections”.

This is a bit misleading. The example you use is that a collection is shared between two views. It is true that if you sort the collection the changes will be reflected in both views. But, sorting is never shared between two separate collections.

Although, I do agree that Collections are best suited for use in views.

[Bindable]
var array:Array;