I’ve signed up for 360|Flex Camp New Jersey, which will place at Montclair University, NJ, next Friday 9/26 and Saturday 9/27. This Flex Camp features one day of hands-on training and another packed with lectures by our favorite Flex luminaries. For more details, please visit http://www.360conferences.com/360flexcamp/.
If you would like to say “hi”, keep a look out for the person who resembles this avatar.
Today, while I was updating my passwords on a few of my social network profiles, I came across a serious security hole found in many of these services. During the course of the day, most of us are likely to rely on various devices such as mobile phones and desktop computers, to update our statuses on our social network profiles. When one uses a client such as Safari on the iPhone, or the web browser on a Blackberry, one’s login info is often cached on the browser. After I changed my Twitter password using the web browser on my Mac, I discovered that I was able to pull up my Twitter profile on my iPhone’s Safari browser and proceed to update my status successfully, all without being prompted to login again using my new password. (more…)
If you upgraded to the iPhone SDK 2.1 and found that the default SDK setting in the Project window is showing “Unknown SDK”, you can easily fix that by going to Menu->Project->Edit Project Settings. In the General tab of the Project Info Panel, set the Base SDK for All Configuration setting to “Simulator – iPhone OS 2.1″ or “Device iPhone OS 2.1″.
If you’re thinking of hosting your SWFs on a content delivery network to improve the performance of your Flash application, or attempting to load a third-party SWF hosted on another domain into your application, be aware that loading and scripting SWFs from another domain posts a whole set of security issues, namely that of Cross-Domain Scripting. Due to the Flash Player 9’s security sandbox, when you load a SWF from another domain into a SWF hosted on your domain, by default, you will not be able to operate on the child SWF without it specifically granting permission.
Before proceeding with this tutorial, I highly recommend that you to read the Adobe Flash Player 9 Security White Paper. This 51-page document, although thorough in many aspects, unfortunately left out crucial details that one would need in order to successfully perform cross-domain scripting. Another indispensable reference would be Colin Moock’s Essential ActionScript 3.0, in particular, Chapter 19 on Flash Player Security Restrictions and Chapter 28 on Loading External Display Assets.
Let’s get started!
At a recent FlashCodersNY meeting where the discussion centered around the subject of the MVC (Model-View-Controller) design pattern, it struck me that a lot of Flash developers, especially those coming from design backgrounds, did not see the value in using the MVC design pattern.
Well, I’m not here to make the case for using MVC but if you have spent enough time struggling with structuring an application so that it’s clearly represented by a set of well-defined relationships and responsibilities, you would’ve likely tried to implement some kind of MVC pattern. Now, some design pattern is certainly better none. Trouble is, every developer has his or her own approach to MVC. When a team of developers are working on the same project, things can get confusing pretty quickly if there are no common standards to adhere to.
