(source: An excellent presentation on Flex 3 components, page 32)

• Ctrl+space to open the hint anytime.
• Ctrl+Shift+C to comment the block of code.
• Alt+upArrow to move the selected code up.
• Alt+downArrow to move the selected code down.
• Ctrl+Alt+upArrow to copy the selected code up.
• Ctrl+Alt+downArrow to copy the selected code down.
• Ctrl+Shift+L for Key Assist (Help>KeyAssist).

I have been using SVN or CVS at work for a while now. On top of the ease with which code from different developers in the team, there is also the comfort of being able to go back some steps after some wilds experimentations. You know, the type of situation where in an attempt to fix a bug, you start to completely rewrite 3 functions... only to discover that you only needed to change one line of code to achieve the same result.

The bother or running SVN or CVS on my local machine for small sized projects and experimentation had always appeared too much. I gave it a go but never really sticked to it. Given that you see Git mentioned all over the place, I decided to give it a go. I clearly fulfil its promises. Less than 10 min. between file download and hitting the ground running. And this includes the time to read one or two tutorials on-line. Count me as another adopter.

Answer in this blog post, Input the Flex Builder 3 license key for compilation with ANT

Locale and edit the flex-config.xml file found under C:\flex_sdk\3.1.0\frameworks\
Towards the end of the file uncomment and edit the licenses element
<licenses>
<license>
<product>flexbuilder3</product>
<serial-number>xxxx-xxxx-xxxx-xxxx-xxxx-xxxx</serial-number>
</license>
</licenses>

Came across this one recently at work. All server connections work fine on all browsers BUT IE6. We get an error #2032 without much more information.

Here is what I gathered on the web.

For reference, there is bug filed at Adobe

When the error appears in IE6 but not in IE7, it may be due to a caching issue. This is particularly likely to happen in MSIE when SSL is used and XML document retrieved (which we do) or when the server sends gzipped data.

According to this technote by Adobe, the issue seems even more likely to occur with a self-signed certificate. They propose to try out to import the certificate manually.

source: What is your IP address? @kioskea

PC at the office... having to figure out some elementary things.

source: Converting html entities in AS3 @razorberry

Here I describe the way I have come to organize my unit tests run with flexUnit, putting together information found here and there.

First use the trick of source binding. Create a separate project called ProjectStemmer_unittest. Use source binding to have all the code available in your main framework also available in your unit-test project. This will allow you to add TestCases for each class you want to test (ideally each class) that live in the same package as the class you are gonna test, but without the test files being ever accessible from the main project (this way, you are sure you don't get to accidentally read test data rather than real ones in your official release project)

I have recently discovered it was possible to extend other components in the mxml. It can be put to great use with inspection, logging, or other debugging tools. Take the excellent KapInspect, for instance

To add inspection capability to a project without messing out the code to be distributed to the client or other sources, you can use this approach:

Imagine you have a file PorterStemmer.mxml in your main Flex project.

Create a second Flex project. Name it PorterStemmer_inspect.

In this second project, link to the source of the PorterStemmer's one. In the 'Flex Navigator' Panel of the Flex Builder, right click on the PorterStemmer_inspect project folder. Select Properties > Flex build Path > Source Path (tab) > Add Folder > browse to the path of the src folder in the PorterStemmer project. Click OK. A new folder "[source path] src" would have been added to your project that provides a linking alias to the 'src' folder.

Having a mac at home and a PC at work, I am confronted with the annoyance that bookmarks saved to the local file system in safari are in webloc format. A format that cannot be read on windows.

A few tips for manual conversion can be found on Mac OSX tips

Easy conversion of multiple Safari .webloc to PC .url files

Save Safari URLs as text clippings not weblocs

But they still present the inconvenience of requiring manual action. You notice that you forgot to convert your files when you are at work and there is not a single mac available around.

Tutorial on Working With the File System API in AIR (note that currentDirectory has changed to applicationDirectory in Flex3)