Update: MediaTemple directed me to another blog post with additional details. This highlights another problem with this incident. The information has been spread all over the place. While this blog post does give some good details, it still does not provide cleanup instructions. It simply says that all malicious files have been removed. I’m sorry to say that they have not.
If you have websites hosted on a MediaTemple (gs) then you may have been a victim of this annoying redirect hack, unofficially known as the johnnyA hack. It was once thought to be an issue with WordPress, but in reality static sites are also affected by this. Essentially the attack works by including some encoded JavaScript onto your pages that tries to redirect you to a malicious website or file.
After much searching and with the help of this blog post, I have found the rootkit that is used to do the damage. If you have been hacked you will find some PHP files that were created by the attackers with a bunch of gzipped, base64-encoded source code. I converted that into the actual attack code which is listed below:
1It looks like the attackers simply visit this PHP page and pass in some request parameters to tailor the attack. It looks like there are a few different options such as generating files, executing shell code, etc. I’m no PHP wizard so let me know if you find something interesting.
So how do you find these PHP files? Just SSH into your root directory and run:
1This will list all files that have a string that is longer than 255 characters. This should help you locate these files.
My big question is for MediaTemple. What the hell are you guys doing? Why are we having to dig around for this information? Surely you have determined the same things so why are you not telling people how to clean it up? This official blog post from MediaTemple is vague and tells us nothing about how to actually clean our servers up. Do your job!
I just uploaded a new tutorial that shows you how to provide an HTML5 video fallback option for devices that do not support the Flash Player. The tutorial also shows you how to use the new Flash Media Playback component for quickly adding video to your websites. If getting your video out to the largest number of people is your goal, providing an HTML5 fallback is an absolute necessity.
I just uploaded a new tutorial that shows you how to create a mobile-optimized website using HTML and CSS. The tutorial also highlights the new multi-screen development features of Dreamweaver CS5. It is important to have a strong grasp on standard web technologies as only then can you make an informed decision about when to use Flash.
I recently uploaded a two-part tutorial that explains how to use the new NativeProcess API in Adobe AIR 2.0. With this API you can communicate with native code to get deeper access to the host operating system. In the first part, I create a command-line screenshot application using Visual Studio and C#. In part two, I create an AIR-based front-end for the C# application using the NativeProcess API.
There has been some talk on Twitter recently about the best way to write an event handler. This is all in good fun of course as there is no right way to do any kind of code. Flashers come from all walks of life. Some are from the design world and some from serious development backgrounds. Below are some of the suggested ways. What do you think?
1Tomorrow I will be appearing on the Android Atlas show on CNET Live. The topic will of course be Flash Player on Android. You can go and submit questions over on the CNET website. Ask about anything and everything related to Flash on Android.
On a related note, I found this nice video today from the Android and Me website showing off various Flash sites using a Nexus One. It’s nice to see an Android community video showing off the power of Flash on mobile.
In addition to being one of the pioneers of MMA, clothing company Tapout is also amazing at creating commercials. Below is a Flash version of the commercials that are currently running on Spike TV.
Now there are many community members not represented here but choices had to be made. It came down to who had cool photos of themselves on Flickr. If you don’t you should hang around with John Davey and Ralph Hauwert more often.
Photos from ArulPrasad, Alan_Ross, johnnybelmont, unitzeroone, chrisorwig, mike.chambers. I know I missed some so please let me know in the comments and I will add you.
Updates: I changed the name of the post as technically this is not a gesture API. It is a way to achieve gesture-like effects using touch data. Also the code below was missing an important line. You have to set the input mode to touch point in order for any of this to work.
As part of my multi-touch session at Flashbelt I introduced a new API for getting true multi-touch gestures in Flash. Windows 7 has a pretty big limitation when it comes to gestures as it is only capable of doing one at a time. Since Flash listens for these native events, we also get that limitation when doing multi-touch in Flash.
Tim Kukulski, who is a member of the Adobe XD team, has written a great set of classes that listens for raw touch events instead of the built-in gestures. The main class, called MultiDraggable, does all of the work for you and allows you to quickly add zoom, rotate, and drag gesture effects to any DisplayObject. See the video below for an example.
The code needed to implement the gesture effects is extremely simple. Below is a code snippet of how to do it. You simply add your DisplayObject to the display list of a MultiDraggable instance. Then add the MultiDraggable instance to the main display list.
1Big thanks to Tim for releasing this code. Photos and artwork in the video are from Ralph and Mario. Go ahead and download the files and have fun spawning multiple gestures!
Update: Just noticed that the player is still in prerelease, so let the team know if you find issues.
As part of the Open Source Media Framework, Adobe has released a new video player called the Strobe Media Playback component. This is a full-featured video player that is ready for easy deployment. It has all of the advanced features of OSMF built right in including things like HTTP streaming, content protection, and progressive, streaming, and live video delivery. Obviously many of you will want to create a custom video player, but for quick video deployment, this player will be the way to go. I have recently switched to using this player on gotoAndLearn().
Deploying the player is very easy and all the instructions are included in the download files. Here’s a tip though. Take the height of your source video and add 35 to get the height of the SWF when you embed.
I had heard through the grapevine that Apple would be posting a set of HTML5 demos today. To be honest I was kind of looking forward to seeing some cool stuff. Instead they have presented a set of basic demos that have very little to do with HTML5 or web standards. On top of that they have implemented a browser-detection scheme that is quite deceptive to say the least.
The image below was circulated on Twitter and it shows that on Apple’s demo page you are unable to view the examples using Google Chrome, Opera, Firefox or any other browser and are instead asked to download and install Safari in order to see the demos. That is quite odd seeing as though Chrome has much better support for the future HTML5 standard according to the site html5test.com.
In an ironic and funny side note, the browser sniffing was apparently blocking people from viewing the demos on their iPhone, although I can’t confirm that. The performance of the demos on the iPhone may have something to do with that, as most of the demos crawled on my 3GS.
If you go to the developer section of Apple’s website you can view the demos using Chrome and are not directed to download Safari. So on to the demos themselves. I made a joke on Twitter about how these were equivalent to things created in Flash 8, but to be honest that is being kind. A photo slideshow and 360° PNG sequence are more like Flash 5. The reality is that HTML5 is capable of much more than that so it is odd that they considered these to be a good showcase of what is possible. Apple should really consider hiring some Flash developers to create some badass HTML5 demos. Many in the community have been dabbling in it and have created much more impressive demos than these.
Other browser manufacturers have rightfully jumped up to dispute Apple’s questionable browser-sniffing policy. Opera’s Haavard Moen blogged that
“when the page doesn’t work in Opera or other browsers it isn’t because these browsers don’t support HTML5. It’s because Apple uses browser sniffing and vendor prefixes, and in addition to that they aren’t really testing a lot of HTML5 at all. Most of their demos seem to have got nothing to do with HTML5, as a matter of fact.”
Christopher Blizzard from Firefox was more direct saying
“Apple’s messaging is clearly meant to say ‘hey, we love the web’ but the actual demos they have and the fact that actively block other browsers from those demos don’t match their messaging. It’s not intellectually honest at all.”
A quick review of the source code shows that it is littered with WebKit-specific prefixes and extensions. The messaging surrounding the demos is also iffy at best. In the Light Table demo, which is actually pretty nice, the messaging states that
“Using CSS3 transforms and transitions, photos can be easily sorted, shuffled, or displayed in a slideshow with just a few lines of CSS and JavaScript.”
Of course I was curious as to the contents of those 3 lines as they must be the most powerful 3 lines of code ever written. In actual fact, the JavaScript file that drives the demo is 700 lines long.
Personally I look forward to the day when simple things like video playback and photo galleries can be handed off to browsers to handle. Flash has always been about pushing the envelope. So long as there are standards, there will always be technologies and developers who want to go beyond that.
Microsoft Surface has a cool simulation that allows you to drag your fingers across the table to create a water simulation. That got me to thinking about doing it in Flash. Thanks to David Lenaerts’ excellent Ripple class, it took me about 10 minutes to create the example below.
As you can see the performance is very nice. The code that I used to create this is below. Again, all of the cool stuff comes from David’s code.
1Lee
Lee
For being only two days in length, Google I/O certainly packed a punch this year. There were lots of announcements and Adobe was at the center of many of them. Through some creative badge sharing, I was lucky enough to attend this year. Here are the some of the things that were announced that are of interest to Flashers.
HTML 5 Extension for Dreamweaver CS5
If you cut through the FUD machine you know that Adobe supports HTML 5 and sees it as a vital piece of the web, alongside Flash. To that end, Adobe has released a free extension to Dreamweaver CS5 that has some great features if you are working with HTML 5 or mobile devices. At the most basic level, the extension provides the necessary code hinting and completion for HTML 5 and CSS 3. The nicest feature is the new Multiscreen Preview Panel. This allows you to see how your page will be rendered on a phone, a tablet, and the web at the same time. It also allows you to include CSS logic to change the layout based on the target device. Awesome stuff!
Google Open Sources VP8 and Adobe Adds Flash Player Support
One of the major arguments surrounding HTML 5 deals with choosing the best codec to support. Google announced that it would be open sourcing the VP8 video codec. At the same time we announced that we would support VP8 playback in Flash Player along with H.264 and VP6. For me the big takeaway from this is, Adobe has you covered no matter what format you choose. I’ll leave it to the browsers to battle on which one is best. We have no time frame for rolling VP8 support in Flash Player, but if you came by the Adobe sandbox you saw that we already have it working.
Adobe Releases Flash Player 10.1 for Android (kinda)
I only say kinda because you have to have Android 2.2 (Froyo) in order to run it. The trouble is that the vast majority of folks don’t have early access to Froyo. Once you have Froyo you will be able to download the beta 1 version of 10.1 through the Android marketplace. You can read the details here.
Adobe Announces AIR for Android Public Beta
Our private beta for AIR has been rocking and I’m excited that we are now entering the public beta phase. All you have to do is go on over to the Adobe Labs site and sign an NDA. After that you will automatically be added to the beta program. Unlike 10.1, AIR will run on Eclair and does not require Froyo. Have fun with it!
AIR for Android Flash CS5 Extension
The process of building AIR applications has been made very easy thanks to a new extension for Flash CS5. You get access to this at the same time you get the AIR runtime that I talked about in the last paragraph. This extension allows you to create a new project for Android and, if your device is connected, you can publish right to the device and even debug on the device. No command line needed at all!
Google TV with AIR and Flash
Another big announcement for Google was their new set-top box allowing you to do web stuff on your TV. It is actually much more involved than the way I’m describing it. It will also allow you to run Android apps (including AIR) on your TV. The browser includes Flash Player 10.1 so you can browse to all your favorite video sites on your TV. Get your head out of gutter, I don’t mean those kinds of sites. Here is a cool video showing off Google TV.
HTC Evo-4G For All
Google handed out the brand new HTC Evo-4G to every attendee and this phone is badass! It has the largest screen of any smartphone and is a real powerhouse. Below are some random shots I took from the HTC UI. Expect some examples of AIR running on this badboy. Did I mention it has HDMI out?
These are exciting times to be a Flash developer!
Lee
Several people have been making assertions that most Flash sites will not work properly on touch-based devices because these sites use rollovers or hovers for things like effects and navigation. Well I put together this little video together showing that Flash sites do indeed work the way you would expect since the Flash Player dispatches rollover events even on a touch screen.
This video is aimed at clearing up the misinformation surrounding Flash rollover events and touch devices. The assertion that most Flash sites need to be rewritten is absolutely false. But please grab a tablet and see for yourself. I tried every FWA Site of the Month and they all worked fine.
Lee
Advanced Text Layout With Flash CS5
I give an introduction to some of the new Text Layout features and functionality in Flash CS5.
Introduction to Multi-Touch in Flash Player 10.1
Flash Player 10.1 introduces a full, native multi-touch API that allows you to create some amazing applications. In this session I demonstrate how to build applications using native multi-touch feedback as well as how to use the built-in gesture support for things like scaling and rotating.
Lee
Update: my instructions for Mac got truncated but it is fixed now. Thanks to Kevin Suttle for pointing it out.
You may have read my earlier post about needing to not have too many files in your ActionScript source path in Flash CS5. After a certain number of files is reached, Flash will basically abort. This is to prevent Flash from indexing your entire hard drive if you happen to save your file in the top level of your disk (i.e c:\). Now the limit is actually 800 files by default, but as hardcore Flashers know, sometimes your global AS directory can be much larger. Well luckily there is a way to change this limit.
WARNING: do not change this if you are uncomfortable with editing your registry. Also do not change this and then complain that Flash is running slow when you save your FLA into your root directory of your hard drive.
Windows:
Mac:
What should you set it at? Well if you are good about saving your FLA files into their own folders, then it doesn’t really matter. I would try 5000 and see if that works. You can always change it back. Adobe is working on an official TechNote about this too.
Lee
One of the most underrated features of Flash CS5 is the new XFL file format. But there is some confusion out there about what it is and how to use it. This quick post will hopefully clear some of these things up.
The XFL format
The XFL file format is a way to represent a Flash Professional document as an XML-based, open folder of files. See the image below for an example of the XFL folder structure. You will notice that there is a file called DOMDocument.xml. This file is the heart of your project. Inside it you will see all of the information for your document including timelines, actions, motion paths, etc. You can edit this information and your changes will automatically take effect when you launch the file. One handy use for this is doing a search and replace across a large number of Flash documents to change strings or colors without having to go into each one and making the changes.
The new FLA format
As I mentioned before, you can still create an FLA file in Flash CS5 rather than the open XFL folder structure. But this new FLA is simply a zipped up version of that open folder structure. If you change the extension to .zip and then unzip it, you will find the same open structure. The new FLA is not an impenetrable binary black box like its predecessor. If you really want the old FLA, you need to save it as a Flash CS4 FLA.
Saving AS source files
One thing that has been tripping people up is where to put source files in relation to XFL folder structure. It might seem to make the most sense to put your external ActionScript files inside the project folder that is created. So let’s say that I create a new Flash document and save it to the desktop as foo.xfl. Flash will actually then create a folder called foo on the desktop. Inside of that folder is the XFL project file and the other folders that make up the project. But you CANNOT place ActionScript source files inside of this folder. You need to instead save them alongside the top-level folder of your project. So in this example I would save my ActionScript source files onto the desktop next to the foo folder.
Save and Compact?
You may notice that there is no longer an option to save and compact your FLA files. This is because the new FLA format is simply a zipped version of the open XFL structure so the binary compacting is no longer an option.
Update: we do plan on releasing the XML schema for the XFL format to allow others to create and edit the project format themselves. I will look into a time estimate for this.
Update 2: below is an example of how a frame script appears in the DomDocument.xml file.
1Update 3: below is an example of the TLF markup text from the DomDocument.xml file. You can use this as a template for creating dynamic TLF text.
1Lee