When you first get started with FDT3 from PowerFlasher http://fdt.powerflasher.com / http://fdt.powerflasher.de you will probably get the message…
Not enough memory to run FDT - add the following line to your eclipse.ini
-Xmx512m
On a windows machine the eclipse.ini is easy to find, and should be in the same folder as eclipse.exe, editing the file in notepad and altering the line
-Xmx256m
to the value above, should be straightforward. If you struggle with opening and saving files in notepad, sadly this blog post isn’t going to give you the file editing 101 that you sorely need.
If you are cool with the file change, restarting Eclipse and opening the FDT perspective will solve the issue.
On a Mac OS X machine things are a tiny bit trickier, the eclipse.ini file is tucked away inside the Eclipse application package, which you probably have stored in your Applications folder.
The quickest way to get at the eclipse.ini file is to Ctrl + Click the Eclipse application and select the *Show Package Contents* option from the menu.
If you then navigate to Contents/MacOS/ inside the package you’ll see eclipse.ini edit it with TextEdit or whatever you like to use to edit text files (TextMate http://macromates.com/, Eclipse, BBEdit?) and change the line
-Xmx256m
to read
-Xmx512m
Save eclipse.ini and close the finder window, restart Eclipse and you should be good to go.
This information is probably in the FDT forum, but I just figured this out five minutes ago and decided to post here instead.
March 3rd, 2008
Thanks go out to Adobe this week, for opening up the AMF (Flash remoting message format) specifications.
A PDF is available from here…
December 22nd, 2007
Well, January 07 is almost done and this is my first post of the new year.
I'm now running the Flash Team over at Endemol Uk. The nice people who brought you Big Brother and Deal or No Deal. I'm very busy looking after things there, but I hope in the coming months of 2007 I'll have a good few things to talk about and report on.
One of the area's I'm particularly focusing on these days is production work flow, from project planning all the way to code standards and development methodologies. So no doubt I'll be writing about that a fair bit.
Also I'm really hoping to get some work done on Badgr, the little Flickr gizmo that could. This is going to be FlashPlayer9 and AS3.0 based which is going to be fun.
I hope everyone out there is having a great start to the new year.
January 21st, 2007
QLOD (Quit living on dreams) has posted a series of useful articles detailing some first steps with ActionSctript 3.0. Here's they are collected as a series for you..
QLOD's links...
A great little series of articles.
December 26th, 2006
Adobe and Mozilla announced that Adobe will contribute source code from the latest Adobe® ActionScript™ Virtual Machine (AVM2), the standards-based scripting language engine in Adobe Flash® Player 9, to a new open source project known as Tamarin that will be hosted by the Mozilla Foundation.
AVM2, as currently shipping in Adobe Flash Player 9, was built from the ground up to work with the next generation of ActionScript. The new virtual machine is designed to deliver the performance and features to support the needs of rich Internet application developers. Source code from AVM2 being contributed to the Tamarin project implements ECMAScript 4th edition language features such as namespaces, classes, and optional strongly typed variables, and includes a Just In Time (JIT) compiler that translates ActionScript bytecode to native machine code for maximum execution speed.
The Tamarin project will result in an ECMAScript 4th edition engine that Mozilla will use within the next-generation of SpiderMonkey, the core JavaScript engine embedded in Firefox®, Mozilla’s free Web browser, and other products based on Mozilla technology. The code will continue to be used by Adobe as part of the ActionScript Virtual Machine.
Read more, visit the Tamarin FAQ
November 8th, 2006
Previous Posts
Subscribe...