Author and FDT fan Sidney de Koning has just completed a new book titled ‘Automating ActionScript Projects With Eclipse and Ant‘. It’s a short and sweet book that gives a nice introduction for anyone interested in integrating Eclipse & Ant into their Flash workflow. In this book, you’ll find various powerful Ant scripts as well [...]
You asked for it and we built it. FDT 5 is now available as an Eclipse plugin. Many developers prefer to have FDT installed into an existing Eclipse setup. Starting today, you can install FDT as a plugin and it will function as FDT Free until you enter a license key. To install FDT as a plugin: [...]
We’d like to call attention to a great free Flashevent on Dec. 4, 2011: Flashtent is a livestreaming event hosted by John Barrett (HFUG) and Ben Fhala (EverythingFlash) and will cover Mobile, 3D, AIR, Gaming, and HTML5. Speakers include Dee Sadler, David Gamez, Chris Griffith, James Wagstaff, as well as FDT’s Alan Klement. Alan will [...]
The waiting comes to an end, you can now upgrade your FDT to a whole new dimension. FDT has just become the perfect toolkit for Flash-/Flex-, haXe- (HTML5, JS, PHP, WebGL …) and mobile development. New Features: haXe support Extract Method Extract Constant Extract Local Variable Convert Local Variable to Field ASDoc View Fat SWC [...]
As announced last week, FDT 5 will not only gain features but improve in many ways. Last Monday we told you about the new Freemium model. Today we will show you the new prices.
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?