Posts in Category "Flash CS3"

Flash and Snow Leopard

So, I take it by now most of you have already read John Nack’s post "Adobe Snow Leopard FAQ" as well as read the official Adobe FAQ. If not, you probably have been reading all kinds of tweets and blogs on the subject. So I won’t repeat what has already been posted. I did however want to update everyone on Flash’s status and maybe divert some flak that John has been receiving.

We have tested Flash CS4 on Snow Leopard and have currently found no issues. If this changes I will update this post.

As for Flash CS3, we did run a few tests. So, for now I can say that it installs, launches and runs fine with common steps i.e, draw rectangle, convert to movie clip, test movie, save and open file, etc. CS3 seems to run fine on Snow Leopard. This doesn’t guarantee that you won’t find any issues, there might be one; we have not run a full test pass on CS3. For the record, to do this, it would have taken our team a month at a minimum. As John mentions, we are not saying that CS3 won’t run on Snow Leopard, just that we are not planning to address any bugs that might be caused by the new OS.

I hope this helps.

About Flash Components

Many users have been asking about components. They want to know if we are releasing more components or where they can go to get more of them. Many members of our community have also been wondering what is our vision for components going forward. Apologies for not responding sooner.

The Flash Authoring team does not have plans to release any new components in the CS3 timeframe.   Of course, the Flex team will continue to develop and release new components; components are an integral part off their model and core to the success of the Flex product.

When the Flash Authoring team went out and met with users to research what we should be developing for CS3 and beyond, additional components didn’t make the cut. When we focus on the needs of the community, this is what we hear loud and clear: focus on expressiveness, focus on ground breaking design and focus on enabling the community to meet the needs of other users through extensibility. Demand for components has been very fragmented – some users want x, other users want y – and no matter how many components we have built we were still not fully satisfying all the needs of the community. And, frankly, we realize that in many cases Flex is a better alternative for some of the customers that ask for components to assist in RIA development.

So, for you component lovers, we’re doing two things – 1) continuing to invest in the extensibility of Flash Pro so that you can build and share the components you need and 2) investing in integration with Flex Builder to make it even easier to take advantage of what Flex has to offer.

So what does that mean to our users today? Well, it means that we are looking to third party vendors and our community to help fill that gap.

We have started to provide documentation on how to build and extend the new AS3 components. Jeff Kamerer wrote a comprehensive article on the matter and you can find it at http://www.adobe.com/devnet/flash/articles/creating_as3_components.html

Some community members and third party vendors have already created some great components, for example:

1. The Adobe Exchange for Flash has a large selection of third party components.

2. Grant Skinner has been developing components for some time now. In fact as many of you already know he worked with Metaliq to develop the AS3 components for Flash CS3. <URL?>

3. Yahoo has a great set of components at http://developer.yahoo.com/flash/astra-flash/

4. Digicrafts has some visually rich components at http://www.digicrafts.com.hk/components/

5. There is a nice selection of components at http://www.afcomponents.com/components/

** If your site is not listed, please send me a post and I will add it to the list.

Of course, everything I write today is affected by what our community has to say. When it’s all said and done you really are the ones that determine what we do. So with that in mind there are some other ideas/questions we have that I would like to throw out there and see what the feedback is.

1. What could we do to help promote and encourage the community to start creating new components for Flash Pro?

2. In the future, how would supporting the Flex components help solve the problem?

AIR update Beta 2 for Flash CS3

AIR update Beta 2 for Flash CS3 is now availble at Adobe Labs. The new update now includes support for AIR Beta 2. One of the new feautres of the update is  signing using digital certificates.In fact you must sign the AIR app in order to be able to publish it. Dont forget that.

Flash Team and Flash Forward

The Flash Product Managemnet team will be at Flash Forward in Boston. So if you are attending please stop by the booth and sey hello. Also, if you like, drop me a comment if you are going to be there, I will make a note to look out for you.

We are looking forward to talking with as many Flash users as possible. Also, make sure not to miss the Keynote. Kevin Lynch will be presenting and it’s going to be a vey good session.

See you there.

Using Copy Motion to ActionScript 3 with Flex

Previously I blogged about using the new Copy Motion to ActionScript 3 feature. Now I I would like to show you how to take that feature and extend it to Flex.

I have included my FFanimaotr flex project that has a working sample of this. You must have Flex and Flash CS3 installed for this to work since we need the Animator class that ships with Flash CS3. Just import the project to Flex and it should work.

Here is the Flex code:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" creationComplete="xmlService.send()" layout="absolute" height="492">

<mx:HTTPService url="{ combo.selectedItem + ‘.xml’ }" resultFormat="e4x" id="xmlService"/>

<mx:Script>

<![CDATA[
import fl.motion.Animator;


public var my_animator:Animator = null;

private function animate():void {


if (my_animator) my_animator.rewind();
my_animator = new Animator(XML(xmlService.lastResult),moveThis);
my_animator.play();


}

]]>
</mx:Script>

<mx:Button x="130" y="10" label="Animate" click="animate()" fillColors="[#810713, #810713]"/>
<mx:ComboBox x="10" y="10" id="combo" change="xmlService.send()">
<mx:dataProvider>
<mx:String>blurSwirl</mx:String>
<mx:String>bounce</mx:String>

</mx:dataProvider>
</mx:ComboBox>
<mx:DataGrid x="23" y="88" id="moveThis" width="368" height="238">
<mx:columns>
<mx:DataGridColumn headerText="Column 1" dataField="col1"/>
<mx:DataGridColumn headerText="Column 2" dataField="col2"/>
<mx:DataGridColumn headerText="Column 3" dataField="col3"/>
</mx:columns>
</mx:DataGrid>

</mx:Application>

I have enclosed two xml animation files called blurswirl.xml, which is the same example I used in my previous blog, and bounce.xml. You can use your own if you want, just add your animation file to the bin folder in the Flex project and change the name in the Flex code (in Green). Remember that you create animation xml files by selecting an animation on the timeline and then use the "Export Motion XML" command under the command menu.

Ok, so the part I need to point out is that if you want to create your own flex project then the trick is to add the Flash CS3 class path to your Flex project so that it knows where to go get the animator class. Normally the path (in Windows) is C:\Program Files\Adobe\Adobe Flash CS3\en\Configuration\ActionScript 3.0\Classes, but if you installed Flash CS3 in a different location you would need to adjust the path. On a Mac look for the same folder but starting from your application folder. You add this to your Flex project by going to the Project properties and adding the class path to the "Source Path" tab under "Flex Build Path".

Ok, so how does this work? simple, you just run the same AS3 code that I showed before (in Red). Except this time you tell it to animate a Flex component. In this case I am using the calendar component, but feel free to replace it with any component (SWFloader, VideoDisplay, etc) just make sure to give it an ID of "moveThis".

The only thing I am doing a bit different than what I did in my Flash CS3 example is calling Animator’s rewind function. as in:

if (my_animator) my_animator.rewind();

I am doing this so that when you select a different animation the component you are animating doesn’t continue from where it finished and fly off the page.

My example is actually more complicated than it needs to be. I am using a combo box with two animations you can select from. When one is selected it calls my animate function with in tern loads the XML file and then uses the Animator class to apply the animation to any component that has an ID of "moveThis".  The beauty is that its all at runtime.

Play around with it. See what you can do with it and if you think you have something cool please share.

Copy Motion to AS3 (ActionScript 3)

One of the new features we have in Flash CS3 is the ability to copy an animation on the timeline to AS3 (ActionScript 3). I am a big fan of this new feature let me show you why.

For example:

the animation that is illustrated above is a typical timeline animation. If you then right click on the timeline you would see the option to copy motion to AS3.

It then asks you to specify and instance name of the symbol to which you would like to apply this code too. Flash CS3 then places code into the clipboard. If you were to paste this code in the actionscript panel you would see:

import fl.motion.Animator;
var box_xml:XML =
<Motion duration="1" xmlns="fl.motion.*" xmlns:geom="flash.geom.*" xmlns:filters="flash.filters.*">
<source>
<Source frameRate="30" x="52" y="111.5" scaleX="1" scaleY="1" rotation="0" elementType="movie clip" symbolName="box">
<dimensions>
<geom:Rectangle left="0" top="0" width="92" height="77"/>
</dimensions>
<transformationPoint>
<geom:Point x="0.5" y="0.5"/>
</transformationPoint>
</Source>
</source>

<Keyframe index="0" tweenSnap="true" tweenSync="true">
<tweens>
<SimpleEase ease="0"/>
</tweens>
</Keyframe>
</Motion>;

var box_animator:Animator = new Animator(box_xml, box);
box_animator.play();

Notice that the code in red is the only part that truly is AS3. The blue part is XML describing the animation.

To get this to work, just create a new AS3 document and paste the code on frame 1 of the timeline and drop any symbol on stage and call it’s instance ‘box’. Run the movie and you will see the symbol move across the stage.

Ok,so what’s so cool about this? well, first. It allows me to re-use an animation as many times as I want. It also allows a normal designer/animator to work with a developer that prefers to see everything in code. However, one of best parts is that it allows me to store my animations as external XML files.

If instead of right-clicking on the timeline, I would have gone to the command menu and selected "Export Motion’. I would then be able to save just the XML description to an external file.

ok, so now what. Well, lets say I saved my animation as swirl.xml, if I change my AS3 code a little. Like so:

 

import fl.motion.Animator;

var green_can_xml:XML = new XML();
var green_can_animator:Animator;
var XML_URL:String = "swirl.xml";
var myXMLURL:URLRequest = new URLRequest(XML_URL);
var myLoader:URLLoader = new URLLoader(myXMLURL);
myLoader.addEventListener("complete", xmlLoaded);

function xmlLoaded(event:Event):void {
green_can_xml = XML(myLoader.data);
green_can_animator = new Animator(green_can_xml, green_can);
green_can_animator.play()
}

I can now have my flash movie load the animation at runtime and play it. This will allow me to change the behavior of the animation just by replacing an XML file. Cool huh? I’ll let you figure out all the uses fot it.

Oh, and in case you are wondering the same animation can then be applied to a component in Flex. I’ll show how to do that next post.

 

Flash Team at NAB

First, I want to apologize to those of you who wanted to leave comments to my previous posts but were not able too because commenting was not available. Normally I would blame the server or software for the glitch….but nope, it was all me.

Ok then, next topic. The Flash Team will be at NAB! Well, at least the Flash product management team will be there. In case you don’t know much about NAB, it is a wicked show. 100,000 of our best friends come together in Vegas to learn about electronic media. For those attending NAB please stop by and say hello; our booth number is SL3220. We will have a demo station for Flash CS3 Professional and be delivering several presentation in our theater that you might find interesting. I have listed a few of the Flash related topics below.

• Post Production Workflows with Adobe Production
Premium CS3
• What’s New in Adobe Premiere Pro CS3
• What’s New in Adobe After Effects CS3
• Adobe Flash CS3 for Video Professionals
• Audio for Video Professionals with Adobe Soundbooth CS3
• Video Streaming with Flash Media Server

Hope to see you there.

Welcome Flash CS3 Professional

Ok ladies and gentlemen, here it is at last! . It is a pleasure to officially introduce you to our latest release of Flash. FLASH CS3 Professional

 

This release has a lot of great new features and I will be covering all of them in some detail in this blog. But to start out I will point of 5 of the biggest.

  1. Photoshop and Illustrator import – you can now import all of your psd and ai files and not loose any fidelity while doing so.
  2. Support for ActionScript 3.0 – AS got faster, stronger, and better than ever.
  3. New UI - if you have a laptop this is a must have.
  4. Copy motion to AS3 – (one of my favs) this lets you take any animation that is on the timeline and convert it to ActionScript 3.0. You can then apply that animation to any symbol as pure code.
  5. New components - these are all new AS3 components that are much easier to skin. Just double click on the component and you have access to all the skin symbols.

So those are some of the major features, but we also added a few small tweaks and fixes to the tool. There is one in particular that I am really happy about, but instead of just telling you about it, lets see if any of you Flash gurus can figure this one out. We changed something in the documents property window (or something you can access from the documents property window)…can someone tell me what it is?

 

One last thing. Can someone shed some light into who is responsible for www.gettheglass.com  I love this site. Very nice work.