[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 […]
We just released a bugfix release (3.0.1 build 1002). Beside the bugfixes a few new features are included also. There are new error markers, you can use organize imports and the formatter at packages/folders (select them in the flash explorer and press CTRL+SHIFT+O / CTRL+SHIFT+F), can tell FDT to ignore files starting with a lower case letter and some other things. For a detailed list see the dialog that appears at the update.
The help content is more or less complete now but needs proof reading. Such it will take one or two more weeks before we can release the documentation. After this we will continue to close bugs for a short time and come then to big new features.
You can update OSX’s eclipse.ini file. Just select eclipse.app, right click and select “show package contents” and find it in the MacOS folder. Powerflasher didn’t write eclipse!
Sorry I couldn’t resist this funny typo: “… but needs prove [*proof*] reading.”
Updated to 3.0.1 build 1002. Now I get an alert upon starging Eclipse that asks me to increase the allocated memory to Eclipse (Something you can’t do in Mac OS X to my knowledge). And to add the line “-Xmx512m” to eclipse.ini. Is this a proper installation methodology? To ask the user to hand edit application init files?