Saturday, July 18th, 2009
Let’s burrow some in my FDT templates crate … how often do you have to add a child display object to another display object? If the answer is ‘very often’ then this small FDT template might save you some time.
${property} = new ${cursor};
addChild(${property});It’s very simple but effective. Usage: Let’s for example name this template “newDisplayObject” and after invoking it with CTRL+SPACE you start typing the name of the display object property that you defined as a class property before which then should be auto-completed, then you hit TAB and then CTRL+SPACE to quick-insert the type after the ‘new’ operator (FDT is finding the correct type for you) and Voila, you’re finished, no need to add that extra ‘addChild’ manually.
Filed under Dev, Random Picks | 1 Comment »
Sunday, April 12th, 2009
I’ve been using Eclipse and FDT for several years now to develop Flash (and Flex) applications but I never really managed to set up Eclipse to exactly fit my needs. Either some desired tools were missing or I installed plug-ins that slowed down Eclipse with a truck load of stuff that I never need.
So today I finally figured out how to install the plug-ins that I really need and nothing else (well … almost nothing else). The following guide describes how you can set up your own custom Eclipse tailored for Flash/Flex development which features FDT plus Subclipse, a HTML, CSS, JavaScript and XML Editor and then some. The CSS Editor becomes especially useful for Flex Stylesheets.
(more…)
Filed under Dev, Random Picks | 33 Comments »
Monday, October 15th, 2007
The guys at Powerflasher done a great job! Check out their new FDT 3 at fdt.powerflasher.com. Personally this has become once again my favorite coding tool (after an over one year break with FlexBuilder’s editor). FDT has many features that one would otherwise only find in superior tools like Eclipse’s own Java Development Tool … and these are top notch! FDT is now shipped in three different versions, Basic, Professional and soon an Enterprise version which will add a Debugger, MXML Parser and advanced Refactoring.
I’m especially looking forward to the MXML Parser since in it’s current state FDT only allows for pure ActionScript projects. The MXML Parser would make it possible to add Flex and Adobe AIR projects to the roll.
Filed under Dev | 1 Comment »
Monday, September 3rd, 2007
I’ve joined the closed beta of FDT 3.0 a couple of weeks ago and saw that there was steady progress in bug fixing with around 3-4 updates every week. Now the guys at Powerflasher started the Open Beta which everybody can join by visiting the FDT Forum.
FDT 3.0 is pure coding comfort indeed! After using it you’ll agree that the Flex ActionScript editor looks like a poor excuse compared to FDT! There are all the features for ActionScript 3.0 that also were in FDT 1 and a lot of new stuff. Luxurious syntax coloring and semantic syntax highlighting, code templates,my number one favorite feature Mark Occurences, code formatter, quick fixes, Flash IDE and Flex compiler support, limited refactoring and more.
Now all I wish for is that FDT works flawlessly together with Flex/AIR projects but that will probably come at a later date since getting a stable release is more important now. It kind of feels awkward if you have to go back to the Flex AS editor once you used FDT!
Filed under Dev | No Comments »
Wednesday, September 27th, 2006
It was about time! According to PowerFlasher a new (and free) update of FDT is due in October. But it will not support AS3/Flex, this will come in quartal 1/2007.
I still need to use AS2 very often for jobs so it’s good to see the Eclipse 3.2 incompatibility being fixed very soon. However I’m using Flex Builder (plug-in) more and more to get on with AS3 and Flex and it’s hard to miss all those great features from FDT there! Therefore it would be awesome if Adobe is providing an update for Flex Builder in between. Some very helpful features from FDT that I’d love to use for AS3 are templates (we all use them, they make coding a lot faster) and Mark Occurances (this might seem inferior but once you used it you know that it is the number one killer feature). Another thing that bothers me is that one needs automatic build active to have compile-time error reporting. It would be cool if the Flex Compiler would report errors on-the-fly like MTASC does it, so I can turn off automatic build and use Ant for building instead which I prefer.
Filed under Dev | 1 Comment »
