[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 […]
Continuing the series of featured video tutorials in order to make you familiar with our FDT video site, this time we want to recommend you the tutorial on Source Attachment for SWCs.
The whole elaborate tutorial can be found in the docs. Make sure to check the video site for more tutorials; we work hard to provide you an intense tutorial experience!
@Lennart
Do you mean auto attach the sources? Or to use a the sources instead of a .SWC?
For auto attach, we can’t guarantee the location of where the sources of a .SWC are located, or if a code base has been altered (e.g. Monkey patching the Flex SDK).
For using sources over a .SWC, .SWCs are always preferable over using source code directly. This is for 3 big reasons:
1) Faster compilation of projects
2) Less memory / faster performance of FDT (FDT doesn’t need to scan the source code in SWCs for errors)
3) Better for versioning. If you are using a few large libraries, you can easily add 100 of extra files for your versioning system to track.
And why not use the sources in the first place?