Once you are fully set up the amount of laborious boiler plate code will be reduced considerably.

This is usually due to the xmlns reference at the top of the page including the same import. To solve the problem, remove the xmlns reference that uses the same import.

For example:

<?xml version="1.0" encoding="utf-8"?>

<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
			   xmlns:s="library://ns.adobe.com/flex/spark"
			   xmlns:mx="library://ns.adobe.com/flex/mx"
			   minWidth="955" minHeight="600" xmlns:view="view.*">

	<fx:Declarations>
		<view:TestView/>
	</fx:Declarations>

	<fx:Script>
		<![CDATA[
			import view.TestView;
			private var testView:TestView;
		]]>
	</fx:Script>

</s:Application>

Because the TestView component is referenced in both mxml and ActionScript, the AS version of the import will be prone to disappearing. To solve the problem stick to either AS or mxml (not both) when using the component and don’t forget to remove the “xmlns:” reference.

Incidentally, this problem may have been resolved in FlashBuilder 4. I haven’t noticed any disappearing Imports since upgrading.

Another possible cause is referenced here.

To successfully achieve a comfortable review friendly working practice will take effort from both reviewers and reviewees. Some practice is also required until the reviewing process is just right. If the reviewer is too soft there is a danger that poor quality code could make it into the codebase, whereas if they are too hard the coder could become unnecessarily defensive or upset.

When a “review before check in” process is first introduced there is usually some frustration from the coder because it seems like time is being wasted before they can complete their work. In the long run I have found the time spent on reviews to be worth every second as they often catch defects before the testing process and help to improve a coders knowledge.

To help resolve the personal issues that invariably arise from reviews you can adopt the Ten Commandments of Egoless Programming as a way of resolving any hurt feelings. It is vital that reviewers use language that does not express disappointment, blame or general negativity as this will create a negative attitude toward reviews.

Tools I have used for code review include Smart Bear Code Collaborator and Jupiter for Eclipse. I recommend Smart Bear if you are serious about reviews and have the budget, otherwise Jupiter may be sufficient. It’s worth noting that Smart Bear may offer a free licence if your project is free and open source.

It is not the critic who counts; Not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better.

The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; Who strives valiantly;

Who errs, and comes up short again and again, because there is no effort without error and shortcoming; But who does actually strive to do the deeds; Who knows the great enthusiasms, the great devotions; Who spends himself in a worthy cause;

Who at the best knows in the end the triumph of high achievement, and who at the worse, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who know neither victory nor defeat.

-Theodore Roosevelt

-vmargs -Xms256M -Xmx512M

Shortcut Example: "C:\Program Files\eclipse\eclipse.exe" -vmargs -Xms256M -Xmx512M

Alternatively, you can update your eclipse.ini file.

More information can be found on Ryan Phelan’s site.

These examples have been tested on a Windows XP PC with 2GB RAM.

The system cannot find the file specified.
svn: Can't create tunnel: The system cannot find the file specified.

Typically, you experience it when using a url with the following structure:

svn+ssh://myfancy.svnserver.com/repo

Thankfully there is a very simple fix. All you need to do is adjust one of the settings in the “Window->Preferences” menu.

Navigate the tree to “Team->SVN” and you will notice a section called “SVN Interface”. If the client is set to “JavaHL (JNI)” then change it to “SVNKit (Pure Java)”.

Thanks to Mark Phippard for this gem.

Alternatively, you can search for “Cosmic Corridors” on iTunes.