Tuesday, March 29, 2011
Communication with pop up window (callback & custom event)
Pop up windows are very handy components, especially for showing some important information to user. But this is only communication in one way, what if we want to get data back from user? We can put some controls to retrieve input from user in pop up window (TextArea for instance), but how this data could be transferred to main application?
Labels:
Code Snippet,
Components,
Events,
Flex
Monday, March 7, 2011
Switching Between Flash Players in Chrome Browser
When you have installed debug version of Flash Player in your browser (in this case - Google Chrome) you often have to deal with uncaught exception window. This is fine when you write your code and want to debug it, but when you just want to just surf in the web it could be very frustrating. So is there a good way to deal with that? Of course there is!
Labels:
Flash Player
Thursday, February 17, 2011
Links site
During my work with Flash Platform I gathered links to a bunch of sites containing many useful information. I put the most important of them in my Links page (LINK). If you're a beginner I recommend to see
Labels:
Websites
Tuesday, January 18, 2011
How to start with AMFPHP
AMFPHP is great piece of code made for connect Flash applications with its server side (coded in PHP in this matter) by using AMF protocol. It's way better in terms of efficiency and packet size than standard GET/POST calls.
Labels:
AMF,
Code Snippet
Wednesday, December 29, 2010
Skinning in Spark - how to get the default skin?
Flex 4 introduced Spark components skinning - very powerful but at the same time quite overwhelming capability. I think the best idea is to edit default component skin instead of creating your own from the scratch. The big question is - how can you get this default skin?
Labels:
Flex,
Spark Skinning
Thursday, December 23, 2010
Object Pooling in Flixel
When I started to write my first game called Infinite Shooter I didn't realise that when you destroy an object in Flixel engine (using kill() function) it doesn't really disappear - it just "hang in the nowhere", still existing in allocated memory. Because of that after a few minutes of gameplay, when many planes arrived on and left the screen, I had a huge memory leak. Solution for that is making an object pool, where you can reuse killed objects and make a new ones from them. How can you achieve that in Flixel engine?
Labels:
Code Snippet,
Flixel
Thursday, December 16, 2010
First Post & First Project
This is my first post so I would like to welcome every stranger who stumbled upon this blog!
My purpose is to write about programming in Actionscript 3.0. I started to code in it about 3 years ago. First I made some projects for my university studies, but now I write Flash applications in my current job. I will show you some code snippets and solutions to problems (or, better to say, challenges) that I spotted and will spot during my work as a Flash developer. I would like also to share some thoughts on Flash Platform and of course show you my finished projects!
My purpose is to write about programming in Actionscript 3.0. I started to code in it about 3 years ago. First I made some projects for my university studies, but now I write Flash applications in my current job. I will show you some code snippets and solutions to problems (or, better to say, challenges) that I spotted and will spot during my work as a Flash developer. I would like also to share some thoughts on Flash Platform and of course show you my finished projects!
Labels:
Flixel
Subscribe to:
Posts (Atom)