This number is Google Analytics Report of my site in 2009.

2009 Google Analytics Report

The 138 coutries is 70% of the world. I think this is good number. Don't you think so?

Also "93,814 visitors" is good number, or not, what do you think?

In 2010, I'm thinking about making some contents (e.g. useful know-how and some sample sources) charged. Have you ever bought know-how and sample sources? How much can you pay for it?

These lists shows only open bugs :)

SDK: Fixed Bugs in 3.5

Milestone : SDK Flex 3.5.0

* I mean there might be no internal reported bugs of Adobe.

If your project is not big, you better think of updating Flex SDK to 3.5. The code differences are not many. So you can check the code differences by some diff tool and see how different it is.

Strictly, this is the difference between 3.4.0.9271 and 3.5.0.12683. Of course, both versions are the released builds.


The list are here.
Class Properties in Flex3.5.0 but not in Flex3.4.0
Class Methods in Flex3.5.0 but not in Flex3.4.0
Class Methods parameters in Flex3.5.0 but not in Flex3.4.0


There is almost no difference. So, I listed the internal scopes of "private", "mx_internal" and "protected".

There is no new feature. However, the bugs which caused RTE are fixed. Some of fixed bugs were degraded bugs.

In SystemManager, FocusManager and FlexModuleFactory, there was a bug which caused RTE. Those are fixed at Flex 3.5.

The "internalCompare" function of ObjectUtil was fixed. But is that OK?? It's checking whether the class is dynamic by try{a["wootHackwoot"]}catch{}. It could be right logically, but is it best way as a product?

There are some bug-fix and tiny changes of specification in major components, such as TextInput, DataGrid, Tree, ComboBox, Menu, ListBase.

Also unbelievable bug "if (child as IAutomationObject);" were fixed too.

Some functions of ListCollectionView refer to localIndex at Flex 3.5.


Whether you better upgrade Flex SDK to 3.5 or not. It depends on the size and the situation of your project.

I reported about this at Flex 3.2.
To use and discard RemoteObject causes memory leak.

You know, it's deferred...

So, I tested this at Flex 4 (revision 13101).

It still causes memory leak !!

I guess "deferred" status has the risk called "forgot".

I reported this again.
To use and discard RemoteObject causes memory leak at Flex 4.

Please fix this, Adobe!!