I've been doing a lot of forms lately and that, as you most likely know, it's hard boring work. Always fighting your way through components and the woes of skins.
So I set out to find and easier of doing things and found it over at Keith Peters blog bit-101, it's best two features that will save you the hassle of always having to create component, addChild, set x position, set y position, you can do it all in one line. Components that fire events such as click or change, also take a fourth parameter of defaultHandler and that also saves the addEventListener.
So be sure to check them out at: bit-101 blog or download source here.
(or Programmatically Detecting Memory Leaks in AS3 via Unit Tests)
I've been writing unit tests for a class that deals with the loading/unloading of different types of media files. One of the tests I would like to have is a check for memory leaks. This is especially important now that we have automated our builds, so we can known instantly if a new change in the code doesn't break the behavior we're expecting.
Just saw the news about the new Flex Builder public Beta 3 and I must say I'm anxious to get my hands on it. I've been working with the previous beta 2 and suffering from the slow compile/refresh times that others have also observed. But since it was a Beta we couldn't really complain, could we?
This will be the last beta prior to the launch of Flex Builder 3 and Adobe promises an overall quality and performance improvement. The Matt Chotin's beta feature overview article is the place to go to read about what's new and I'm not saying anything else until I get my hands on this baby.
If you've been out of the loop or simply too busy to check it out, Flex Builder is basically a commercial programming environment for Actionscript programming that has been growing in both popularity and features.
Ted Patrick published on his blog two serials to give you an extension on the trial period of Flex 3. Word has it that it should be enough until the final version comes out.
Here they are:
MAC extension serial #: 1307-0059-4523-4261-9974-9828
WIN extension serial #: 1307-1052-9498-6822-0041-4602
Improving the work flow in the development of Flash applications is something that has been in my mind for some time now, specially after seeing some presentations on the subject at Max Barcelona.
Usually the applications are not big, and are developed by a single programmer in less than a month, so they are manageable, but when a big one come along chaos is installed.
Till recently I was using TortoiseSVN to do version control of my projects. I decided then I wanted to integrate SVN into Flex Builder and do all the svn commands from there directly. In the end it hasn't hard at all, I just followed the instructions from Ben Bishop's post.
Something me and others noticed here is that, since Flex Builder copies all the project root files and folders into "/bin", including the .svn directories, adding the "bin" directory to the repository will cause later problems.
A lot of people have posts about this and so nothing really new here but I wanted to write down what worked (and is working) for me.
A co-worker of mine needed an application that would make it easy for him to take snapshots of .flv files for a content management system, so i came up with the idea of having a go and doing it with air.
So as a follow up i'll make a little tutorial explaining how it works. As Usual you can have a look in the code for the intructions. And should you have any questions feel free to ask them.
+ Help the community
+ Explore the Flash platform
+ Create a better world
+ Research and play
Startups
We're looking for stories about startups using Flex/Flash technology. Drop us a quick e-mail or mention it to us via our Twitter account @dreaminginflash, thanks!
