[contact-form-7 id=”6383″ title=”Take Part”]
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 […]
With this new FDT Release build path entries could be marked as test resource.
A test resource is usually only included during compilation for a Flex Unit test run.
Any build path entry can be turned into a test resource:
Typically all Flex Unit libraries and the test source folder are marked as test resources.
The project compiler properties page contains a new option to include test resources:
By default this option is off since normal project launches usually do not require test resources.
Also the compiler arguments tab of launch configurations contains the option for test resource inclusion:
By default it is inactive.
Additionally the compiler arguments tab contains a further option to force inclusion of test resources which will override the project compiler properties:
Typically Flex Unit test launch configurations require the test resources to be included and so for them the option is active by default.
In other launch configurations this option is inactive by default:
Comments