
We are thrilled to finally release FDT 5.5. Many of you have been using 5.5 beta and we received loads of fantastic feedback that helped us introduce you to the best FDT ever. FDT 5.5 is a free update for all FDT 5 customers. We added heaps of fantastic new features to this big release and we’re sure you’ll like them. The most awesome feature we integrated is the new community feature “SWF Bridge“. It allows you to write your own FDT plug-ins in ActionScript in no time. Nearly everything is possible, so go ahead and check out Alan’s blog post and get started with your first personal FDT Plug-In right away. We also created a microsite where we gathered all relevant information. Furthermore we worked hard on FDT’s Haxe support and implemented some improvements. And there’s a lot more to discover:
New Features
Improvements
- QuickFix for new code should take priority over Assist
- Profile & Debug without compiling
- Flexible SDK setups
- New Project Templates
- New Project Template Features
- Set default for Haxe Flash projects to AVM 2
- Captive runtime GUI support
- Change Exit Postion For ‘Create Field In Class…’
- Update Haxe SDK OSX, Linux & Win to 2.08
- Update Neko OSX, Linux & Win to 1.8.2
- See more in our JIRA and in our release notes.
Software Subscriptions
With FDT 5.5 we are introducing a whole new license management: FDT subscriptions. Software subscriptions aim at precisely matching your needs with respect to time. Subscribe to FDT when you need it and cancel it when you’re done. This allows you to react a lot more flexible to the quickly changing, dynamic environment. From now on, FDT will periodically check your license’s validity, enabling you to allocate your budget to those times when you need FDT the most. Please make sure that FDT is allowed to use Port 80 to communicate with our license server. For more details please check our blogpost. Some great examples and sample calculations to this long awaited novelty are presented in this blog post.
Download
To download FDT 5.5 either insert http://fdt.powerflasher.com/update/fdt5 under ”Help -> Software Updates -> Find and install…” in Eclipse or download the standalone version on http://fdt.powerflasher.com/buy-download.
Many thanks to all the beta testers, keep posting your feedback!
Happy coding!
@ Michael
You need to merge Flex SDk 4.6 with Air SDK.
http://fdt.powerflasher.com/2012/12/how-to-install-asc-2-0-in-fdt/
I downloaded the new fdt and I doesn’t show a mobile option when I go to File > New > New FDT Project. I did download Flex 4.6 SDK and use the search option to find and install it into FDT. I’m using the free package. It says it can do mobile. What do I do now? Help. Thanks
[...] FDT 5.5 now released [...]
@Dmitry,
We’re about to release an update to address a few issues such as what you’ve described. I’ll contact you to get more information on your system.
I downloaded FDT5, Linux build, but wasn’t able to detect Flex SDKs neither on Setup routines nor on Preferences – FDT – Installed SDKs.
hey.. anyone know where the “iOS SDK” field under Platform Sdk in the FDT Air Properties > iOS section of the project properties should link to? seems to compile with nothing in there, just curious
trying to run this on an AIR Mobile project..
gives the following error..
fdt.launch.Application does not support AIR Projects.
is there an alternative to this without running the launch config..
?
@dezza If it helps you: what I’m doing now is to generate the .launch file via Ant build script. I created a template for the launch file and Ant is parsing through it and replaces placeholder strings with build values that might be changed in the build files. It then copies the launch file to the .settings/launch folder and launches it with the new FDT 5.5 Ant task. Of course if Powerflasher decides to change something in their next release this method might break again. But this is a good workaround for when you need distributable Ant build files like me.
Olaf,
Could you file an issue in JIRA? This way we can look into it and see what the issue might be. So far, all of our tests worked fine. Are you on Linux or have you ‘hacked’ the Flex SDK at all? That might be part of it.
In the meantime you can get around it by choosing ‘Haxe’ as your platform and then try to add the SDKs via Prefs>FDT>SDKs
Wizzard does not work. Cannot complete upgrade because Flex SDK are not found. It renders FDT unusable because it won’t allow you to quit the step. I know the Sdk is installed because it worked all fine before. It actually comes at very bad time because urgently need it. Stay away from the upgrade for now.
@dezza
For you error, please post it into JIRA so we can track it.
http://bugs.powerflasher.com/jira/browse/FDT
Adobe’s AIR workflow is becoming increasingly more complicated and the old ANT tasks, which worked well when AIR was just desktop, don’t scale well when targets such as Blackberry (which has its own, self contained signing and certificate workflow) are added into it.
This means we’d have to create all new tasks, with options from scratch – we’d also have to always keep it in sync with the launchers- which is what 95% of our customers use exclusively.
The launch configurations are quite portable, they can be shared between projects by simple duplicating and set them to a different project.
Really wish I hadn’t taken this upgrade since my 5.0 AIR launch configs won’t run in the new version. I liked the old set up better; ANT scripts are more portable than FDT run configs.
After remaking all the launch configs, doing an air compile causes the following error:
An internal error occurred during: “Compile”.
java.lang.NullPointerException.
@G
You’re ok. In the blog post, it’s mentioned that you can be totally offline for 30 days (or 10 for subscription) and you’re license will not be moved from Max to Free.
See more here:
http://fdt.powerflasher.com/2012/05/fdt-license-server/
Could you please remove FDT calling home “feature”? very often i work without internet connection and this calling home “feature” is a real deal breaker. I am a loyal FDT user from version 1.5 (always paid for license, currently on FDT5 Max). If FDT will not be able to function without calling home i will be forced to move to other IDE.
Thank you.
@Alan I think you guys need to ask users first before removing features that breaks all kind of things. I was quite enraged about this yesterday. I found a workaround now by generating an on-the-fly .launch file which is used by the new ‘fdt.invoke.launchConfiguration’ task but I consider it to be a hack. The reason is that my project build setup doesn’t rely on the FDT launch capabilities. Instead Ant is used fully to build the project (the Ant files are quite elaborate). There are many custom settings (compile time constants, etc.) that go into the compile arguments which are taken from a build properties file. I do a search/replace on several placeholder strings in the .launch file to update the file with the current compile settings. It works now again but I had to spend half my weekend just to get the build process for my project up and running again. :/
@hexagon
Instead of forums, we use Stackoverflow:
http://stackoverflow.com/questions/tagged/fdt
We have a general contact page here:
http://fdt.powerflasher.com/contact/
We’re working on making it more conspicuous on the homepage – now it’s just that envelope in the corner.
For ANT, because of the new ANT workflow, the old AIR ant tasks wont work. Instead use ‘fdt.invoke.launchConfiguration’ which is a new ANT task we’ve added:
http://vimeo.com/41847484
Well this is not cool folks! Do you have any friggin support forum where I can get help??
Trying to use my Ant build files with 5.5 and I get fdt.launch.Application does not support AIR Projects -Error
How do I fix this ASAP? This worked fine in FDT 5.
Hey guys,
If you’re having issues with FDT, especially if they are not related to upgrading to 5.5 please send it over to JIRA: http://bugs.powerflasher.com/jira/browse/FDT
And / or Stackoverflow if you have a question on implementation:
http://stackoverflow.com/questions/tagged/fdt
I test FDT 5.5
I have a problem with FDT Font Library.
The compilation of a swf (Output format) with embed font doesn’t work.
Here the log error :
[output]
Compilateur Adobe Flex (mxmlc)
Version 4.6.0 build 23201
Copyright (c) 2004-2011 Adobe Systems, Inc. Tous droits réservés.
[done]
command line: Erreur: impossible d’intercaler des options entre les arguments par défaut
…
A very good version !
With the support of Adobe AIR on Android and iOS.
Thanks.
Just installed, I get to the scan for SDK’s part and it fails. I have Flex 4.6 SDK, but it doesn’t recognize it, I can’t progress further, only option is to quit FDT.
So now I have to choice but to re-install eclipse and re-install FDT 5.
Thanks. 4 hours wasted.
@dada
Here is some more info on what could be going on with your license connection (although it looks like you’ve already tried the URL)
http://fdt.powerflasher.com/docs/Subscriptions_%26_License_Management_FAQ
Here are older FDT installs you can use in the meantime:
http://fdt.powerflasher.com/docs/FAQ#How_do_I_Download_FDT_5.3F_.28Standalone.29
Please contact us so we can figure out what the issue is.
Hey,
At job, I can’t use the new online licence validator. It doesn’t seem to be blocked by proxy when I enter the URL (http://fckgw.powerflasher.com/) in Firefox, but in Eclipse there is no response.
Is there a way to validate it without the server ?
How can I update Eclipse to FDT 5.0 ? (any 5.0 standalone installer.exe or plugin update should be welcome).
I will resolve the licence validation later, for now I just need (and urgently) a working FDT 5.x on my job computor.
Usually, I update on another Eclipse installation, in case of problem, what a mistake to not do it this time…
Thanks for any help.