With Alex's help in http://forums.adobe.com/message/1887799
I can see that the properties in mx block is generated in relevant file, but properties included in mx script file doesn't appear.
Still hope somebody provide some technical explanation on this.
I don't think that this technics helps to you make code more clear.
If you want to split AS code and MXML code it is better to use the Code Behind techics. This is more suitable for OOP programming rather than making out AS code from view class.
See how to use it here http://livedocs.adobe.com/flex/3/html/help.html?content=ascomponents_6.html
Thanks for your reply which let me know something new.
However, it doesn't match my question very well.
What confuses me is why Flex Builder can't recognize the property defind at .as file?
And you are right. Writing method in a stand-alone file won't simply source code, I just want to make the layout tidy.
Thanks and regards,
When you use code behind - in MXML remains only layout. All logic (event handlers, services call, etc) stays in base class.
About you question: I guess when you call code completion (CTRL+SPACE) Flex Builder makes quick parsing of you code. It puts content of .as file into mxml file (i.e. merging it) and than searches for suggenstion. And may be in this manipulations doesn't inserst CDATA block. It is looks like a small bug of Flex Builder.