Up

Share your Content with the FDT Community

You want to join the FDT community? That’s easy, simply send us your news and be part of the FDT community page

[contact-form-7 id=”6383″ title=”Take Part”]

Linux builds have been tested on Ubuntu but should run on other distributions too.

With the download of FDT you accept our EULA

Featured

FDT Views/Editors follow Dark Theme

With this release FDT can easily switched to dark theme:Simply select the Dark theme and apply. The Dark theme is available since Eclipse 4.4 (Luna). Older versions of Eclipse (and FDT) does not support color themes of this form. The FDT views and editors will switch to their default dark color set: In case you […]

by FDT Team

FDT Newsletter

Subscribe to our FDT mailing list and get the latest news and vouchers! * indicates required Email Address * First Name Last Name

by FDT Team

FDT Milestone 10 – 10 years anniversary

We‘re happy to announce FDT Milestone 10! It‘s been 10 years since our first FDT release and a lot happened since last years Milestone 9. We went on to improve FDT and your IDE experience. Here is a list with our new key features: Ant Project Generator Dump launch configuration Library Project Template ActionScript refactorings […]

by FDT Team

Library Project Template

This new FDT release contains features to support a more fluent development of SWC libraries. The primary starting point to develop a library is the new Library Project Template for AIR or Web: This template creates an empty library project containing two source folders: All compilation units to include into the library should be placed […]

by FDT Team

Release 9.9 – Project groups

With this release the FDT Explorer can present projects in groups: Each Project Group is a set of workspace projects (i.e.: Working Set). Each project can be a member of one group and can not be shared among groups. Project Groups are logical structures shown inside FDT Explorer. Neither they represent nor they change the […]

by FDT Team

FDT & AIR 2.7

June 14, 2011 by Carlo Matic

Most Flash developers are waiting for an official release of the AIR 2.7 SDK. Now it is available since the last minutes and you can grab it through the official download site.

But there’s just one step necessary to get the SDK running on your machine. We will show you, how to merge the AIR 2.7 SDK with your Flex SDK and get it running in FDT.

Windows
On Windows it is pretty easy. Just extract the zip file with an unzipper tool of your choice in the Flex root directory and overwrite all files.

Mac OS X
On Mac you can use the Terminal to extract the files. Here’s a quick step by step tutorial:

  1. Copy the downloaded AdobeAIRSDK.tbz2 file into your Flex root directory
  2. Open the terminal, cd to your Flex SDK and type
    tar jxvf AdobeAIRSDK.tbz2 (enter your password if necessary)

After you’ve finally merged both SDKs you can add it in your FDT via the settings popup FDT > Installed SDKs.

Don’t forget to publish with -swf-version=12

FDT 3.1 RELEASED!!

September 2, 2008 by Carlo Matic

Hi folks,

we have fixed the few bugs, tested it a thousand times and now we have done it: we released the new 3.1 version of FDT!!!!

You can download the new installer now from our website. There are really some nice new features. Also we fixed a lot of things you reported, so thank you for that!! Here are the additional features of the new version:

  • Shipped Flex SDK 3.1
  • Default Source Folder is created with a new project
  • You can now define a “Standard Output Folder” per project, where generated SWF files from the launcher are generated by default
  • FDT Intro Contribution
  • FDT Cheat Sheets
  • AIR Debug Launcher as SWF Viewer
  • AIR Release Launcher
  • SWC Outline view
  • QuickTrace (Ctrl+0/Command+0)
  • Launchers can now be started by selecting an editor or a file and pressing “Run” or “Debug”
  • New Launch Shortcut for AS3 Libraries (Run Project as AS3 Library)
  • User Documentation is updated for FDT 3.1
  • Better sorting of the autocompletion proposals
  • Better autocompletion behaviour after “new”, “extends” and “implements”

Here you can find a complete buglist that we fixed in this version: buglist

Check it out and tell us what you think!!

Cheers,

Frank

FDT Standalone!! Version 3.1 in Beta Release

July 23, 2008 by Carlo Matic

Hi Folks,

today we released the new Beta Version of FDT, Version 3.1.0.0001. The following features are implemented in this version:

– Shipped Flex SDK (3.0.477)
– FDT Intro Contribution
– FDT Cheat Sheets
– AIR Debug Launcher as SWF Viewer
– AIR Release Launcher
– SWC Outline view
– QuickTrace (Ctrl+0/Command+0)

It is a free update for all our customers. For us, this is huge!! We are killing almost all difficulties that people had with the installation and setup-process and at the same time, are delivering a bigger AIR development support.

We are keen to get your feedback and hope this version will find your acknowledgment. Here you find your downloadable version:

Mac: http://fdt.powerflasher.com/update_beta/installer/FDTMacInstall.zip

Windows: http://fdt.powerflasher.com/update_beta/installer/FDTInstall.exe

so, tell us what you think,

best,

Frank
Product Manager FDT 3

Coding AIR with FDT

October 23, 2007 by FDT Team

Update:

Please note that developing AIR applications with FDT 3 is very easy now. Simply create a launcher for viewing and debugging your application and one launcher to release it as .air file. To create an AIR debug launch configuration select your Document Class in the Flash Explorer and then open the Run Dialog (Run > Open Run Dialog…). Double click “FDT AS3 Application “ to create a new launch configuration. After that select the “Start” tab and choose “AIR Debug Launcher” as viewer.
Press the “Run“ button to compile and launch your AIR application. FDT automatically generates a default application XML file into your output folder.
To release and package your AIR application open the Run Dialog and double click “FDT AIR Application Release” and configure the settings on the right-hand side.
see: http://fdt.powerflasher.com/blog/?p=94

Please note that developing AIR applications with FDT 3 is very easy now. Simply create a launcher for viewing and debugging your application and one launcher to release it as .air file. To create an AIR debug launch configuration select your Document Class in the Flash Explorer and then open the Run Dialog (Run > Open Run Dialog…). Double click “FDT AS3 Application “ to create a new launch configuration. After that select the “Start” tab and choose “AIR Debug Launcher” as viewer.

Press the “Run“ button to compile and launch your AIR application. FDT automatically generates a default application XML file into your output folder.
To release and package your AIR application open the Run Dialog and double click “FDT AIR Application Release” and configure the settings on the right-hand side. See new post: http://fdt.powerflasher.com/blog/?p=94

Previous Post:

On October 1, 2007 Adobe released the beta 2 version of AIR (Adobe Integrated Runtime), formerly known as Apollo.
As a cross-operating system runtime AIR provides developers with the possibility to deploy RIAs to the desktop. This is very promising regarding the users interaction with the web because it provides a faster access to related data by using native desktop applications. On top of this, AIR applications can have a great look and feel by using customized windows.
All you need to do if you want to build those cool things is to download the Runtime, which is required to run any Adobe AIR application and to also download the Flex 3 SDK. The latter includes as well the AIR SDK as the AIR compiler, the AIR debug launcher and the AIR packager. These tools can be used together with ANT to map the whole AIR workflow.
To distribute AIR applications means to pack the required files like swfs, assets and the application descriptor file. These packages are used by the runtime environment, which should be installed at first, to make sure that all AIR applications will work.
Nico Zimmerman promised that there will be an add-on for FDT to support the AIR workflow with which it will be much easier to develop AIR applications.
Now, let’s take a closer look at the current workflow and let’s build a “hello world” Air application step by step.
<!–[endif]–>

  1. Download and install the Runtime (http://labs.adobe.com/downloads/air.html).
  2. Download the Flex 3 SDK (http://labs.adobe.com/technologies/flex/sdk/flex3sdk.html).<!–[endif]–>
  3. Now you can start your eclipse in the FDT perspective and add a new AS3 core library.
    • Window -> Preferences -> FDT -> Core Libraries -> AS3 Core Libraries -> Add…
    • 2. Choose Flex 3 SDK with AIR as Type, type in “Flex3_AIR” as Name and choose a path variable by clicking the “Browse…” button. If there is no variable linking to the Flex 3 SDK, click “New…”, type in “Flex3SDK_AIR” as Name and add the Path to your Flex 3 SDK folder. Press a few times OK, to get back to eclipse.
      Setting the classpath to Flex3 SDK
  4. Now you’re prepared to start with your first AIR application in FDT: create a New Flash Project with the Name “Hello World”. Choose Action Script 3 with your new core library (“Flex3_AIR”) as the project language and press “Finish”.
    Creating a new flash project
  5. Downloading this zip-file and copying the content to your project folder is the easiest way to go on. The zip-file contains a settings folder within an assets folder. The settings folder contains the application descriptor file which is essential for running AIR applications. This file contains parameters as well for the AIR application as for the first window. You have to customize these parameters as explained in the comments in the file.
    Note that the content tag and all tags marked “required” are very important to run the AIR application! Rename the application descriptor file like shown in this example: “-app.xml” (e.g. “powerflasher-app.xml”).
    The application-descriptor-file
  6. Add the “src” folder to the classpath and double-click the “Build-Air”file. The most important properties which you have to customize are marked with comments and are located at the top of the file.
    • Clean -> Deletes the built directories.
    • Build directories -> Creates directories. “Debug” contains the compiled swf for debugging, “build” contains the compiled swf for publishing and “publish” contains the final AIR file.
    • Compile for debuging -> Uses the mxml compiler with a special air parameter to compile the AIR swf. Instead of that you can use the amxml compiler as normal as you use the mxml compiler.
    • Compile for publishing -> Does the same as “Compile for debuging”.
    • Test application -> Uses the AIR debug launcher (ADL) to start the AIR application without packaging and installation. The ADL uses the application descriptor file to set up the window.
    • Package application -> Uses the AIR development tool (ADT) to package all required files to an AIR package.
    • Create certificate -> Uses the ADT to create a certificate which is required to sign and build the AIR package.
  7. Now you are ready to create the ActionScript Classnamed “HelloWorld”. The code should look like this:
    package
    {
        import flash.display.Sprite;
        import flash.text.TextField;
        import flash.text.TextFieldAutoSize;
    
        /**
         * @author Stephan Partzsch
         */
        public class HelloWorld extends Sprite
        {
    
            public function HelloWorld()
            {
                var textField:TextField = new TextField();
                textField.autoSize = TextFieldAutoSize.CENTER;
    
                textField.text = "Hello world!";
    
                textField.x = (stage.stageWidth - textField.width) / 2;
                textField.y = (stage.stageHeight - textField.height) / 2;
    
                this.addChild(textField);
            }
    
        }
    }
  8. Open the ANT view. You can find it here: Window -> Show View -> Other -> ANT. Drag the “Build_Air” file to the ANT view and double-click number 4 to test your application. Create a certificate with number 7 and than double-click number 6 to package your first AIR application.
    The ANT view in eclipse
  9. Finally you find HelloWorld.air in your project directory in the publish folder. Double-click it to install it on your desktop.<!–[endif]–>

Of course, you can also download this sample project right here.
That’s it and I hope I could demonstrate the workflow of AIR so that you can go on with developing ultra-cool AIR applications. 🙂

Stephan

Get FDT5