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 […]
Subscribe to our FDT mailing list and get the latest news and vouchers! * indicates required Email Address * First Name Last Name
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 […]
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 […]
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 […]
FDT is community driven. We collect all your feedback and use it to make FDT fit the community’s needs. We’ve published upcoming builds of FDT in the past and now want to take it a step further and release our builds on a regular basis. We’ll be using this site to provide you with information on how FDT Beta works and how you can contribute.
The more feedback we get from users, the more we can enhance FDT!
We only deploy a stable, release version when we have used your feedback to create a high quality build. While Beta versions of FDT include the latest features and enchancments, they are considered unstable. Even though most users who use a Beta version of FDT will have not have any problems, it shouldn’t be used for any critical projects.
FDT Beta can be downloaded either as a standalone or via FDT’s update site. To ensure that you’re current workflow for ongoing projects isn’t disrupted, we suggest installing the standalone FDT Beta separately from your production version of FDT.
Learn more about installing FDT Beta as a standalone or via FDT’s update site.
We use a popular numbering system most of you are already familiar with:
[major].[minor].[maintenace].[build]
An important part of a FDT Beta release is the build number. This build number is how we keep track of For example, 4.1.0.2322 is a beta build for 4.1.0. When searching for or logging bugs in JIRA, pay particular attention to the build number you are working with.
Learn more about FDT’s versioning.
If you think you found a bug, first go to JIRA and see if it’s already been logged. If it hasn’t file a new one. When logging a bug with FDT Beta, it’s particularly important to include the build number.
Learn more about using JIRA and logging bugs.
FDT 4.1