And after a few weeks of careful planning and development, here they are: 6 new great patterns for our best seller MovieClipTransitionEffect component. Now, our customers have 25 patterns at disposal (9 embedded into the MCTE component and 16 external – you can see them here). And, even more: we’ve created a package that contains all the patterns, the MCTE component and the LoaderProV3 which you can buy for only $199 from here. For this small fee, now you can add stunning effects to your flash photo gallery, flash banner or flash presentation. Stay online, more to come…

I’ve been reading a lot of blogs and information about how the Flash Lite 3.0 will look like, when will be launched and what language base will be finally used. It is very important to know all these in order to create high quality flash lite components to be used along with high quality applications that would run on either Symbian, Linux, WindowsMobile or some stand alone OSes.

From our inside information, we believe that Flash Lite 3.0 will be a processor limited VM2 based, AS3.0 driven and will include those streaming capabilities that everyone claims for. Because there is an increasing number of devices (both mobile devices and less processing devices like digital interfaces for households), we started to think of cool animation lite components such as the award winning MCTE V3 flash component, and of course about some UI animated components.

Unlike Flash 8 and Flash CS3 Components, the basic Flash Lite 3.0 Components requirements are very important and those developing lite 3 components should be aware of these when designing and developing them.
Here are some good points in developing successful Flash Lite 3.0 Components:
1. Keep the processor safe, non-intensive use of the processor is required, for some devices, the same app/component should measure device capabilities and reduce the calculations till the processor and display device is safe.
2. Keep a small size(less than 200 kb per app) in order to have the app running on more devices.
3. Communication over the internet will be at some points restricted, keep in mind this aspect and design connection-loss error handled components, also monitor connection, pause and restart connection when possible without blocking the device.
4. The components will need to be especially crafted for touch screen devices, joystick and reduced-size keyboard interactivity. No mouse events will be triggered on most devices, onpress and onrelease events should be used to display of rollover and rollout effects, etc.

We hope that in less time after Adobe Flash Lite 3.0 official launch, we will also launch out V3 Lite components. Meanwhile we are getting close to the point of releasing the V3 AS3.0 Flash Components for Flash CS3.

With the advent of ActionScript 3.0 and Flash CS3, Adobe took out the possibility of direct access between AS2 and AS3 clips. The next option (besides communication through servers and web services) is local connection. Until now, if you’d create a clip in Flash MX2004 or Flash 8, using AS2, and inside that clip you would load another .swf file (that too created with AS2), both clips would be able to have access to each other’s objects and functions. This is not the case anymore with the new AS3 files. An AS3 clip will not be able to access any objects or functions defined in the AS2 file that it has loaded, and the loaded AS2 file will not be able to access objects and functions defined in its’ parent, the AS3 clip. The only way for the two movie clips to communicate is to use the LocalConnection class. For an unexperienced user this could be a little troublesome: loading the AS2 file, verifying that it’s been correctly loaded, creating LocalConnection objects in both files and trying to connect them in order to be able to execute functions defined inside those files and on the objects existing in those files.

For this reason we developed the ActionScriptBridge components (ASBTerminal for AS2 and ASBContainer for AS3), to ease the work needed to be done so the two AS2 and AS3 movie clips could communicate. The user has only to drag and drop an instance of the components in the AS2 and AS3 clips, define the functions he needs to call and use the run method of the components to call the defined functions.

Now this is still a beta version, but it’s working pretty well. The ASBContainer loads an external AS2 .swf file and the two clips attempt to communicate with each other using LocalConnection objects. The user has only to set the instance names for the two component instances and set the source file to the ASBContainer instance. All the rest is done by the two components: loading the AS2 file and initiating the communication. The connection name for each of the LocalConnection objects is set automatically by the ASBContainer instance. Each connection has a uniquely generated name, encrypted using MD5. Once the ASBContainer has established a communication channel with the ASBTerminal instance, it will not accept any other connection. Each ASBContainer instance should load its’ own AS2 file and there shouldn’t be two ASBContainer instances loading the same file.

Further development will depend on user feedback on this project, so any ideas or comments are welcome.

Interesting subject isn’t it? How can anyone track a product like a flash component that is not capable to connect to a server and to update information about it?

Flash components unlike other software applications and plug-ins are not track-able. Once a customer get access to a MXP flash component package file, he can virtually give it away to all it’s friends, and nobody will know. There are no unique serial numbers given along with the flash components, there are no key to unlock a free trial versions, there is no way you can secure a full featured flash component.

Some of our flash components may look like something that you think you can do in 2 days of work. However I must tell you that each V3 flash component was developed for more than one month and there are various people who work on every single one of them in order to get it done properly. Under these circumstances it is very important for to keep tracking the usage of every component and it is very important for us that our customers will respect the law of copy and distributing software, so they would respect the hard work that we’ve done for all these products.

During last year we’ve tried something new, because we wanted to know how our customers managed to use our flash components, and we couldn’t get them all to write feedback emails. So we’ve embed some text in some of our flash components in order to see their results on Google; after months and months of indexing they started to get back to us, and by simply googleing the text included inside the components we’ve been able to track back all of those flash files that were using those text linked flash components (of course only those that have been indexed).

By placing a simple search in Google, looking for filetype:swf jumpeye you can easy find hundreds of flash works that embed a late version of waves effect, the loader pro v1.2 and a version of square effect. Starting with V3 components we’ve embed abstract IDs for each components in order to get track of where and how are our components used, and in order not to harm any of our component users, so they don’t need to link to us from inside of their work. This way we have fair information on how our customers managed to use our products, and what side of every product they used most.

A few weeks ago, I started rewriting the V3 components from AS2 to AS3. Since I didn’t find any documentation from Adobe on how to create components for the new Flash CS3, I assumed it is done just like in the previous version of Flash. So I started working on AS3 version of LoaderProV3 component and managed to create a working version for AS3. I wrote a class and then, created the .swc file. So, I was happy that I managed to create my first Flash CS3 component, using AS3 coding. The loader does not have any assets so I didn’t bother with the fact that I could edit the assets for Adobe’s new Flash UI components simply by double clicking on the instance on stage.

The next component, how ever, required to do just that. It was a slider component with skinning possibilities, so the user should be able to edit the component’s assets on the stage. A created the component’s .swc file, but it didn’t work like the new Adobe components. After digging a bit through Adobe’s documentation I found out that Flash CS3 now supports .fla based components. Basically, you wouldn’t have .swc file, but a .fla file, containing all the component’s required classes and assets. Now, the big question: how on earth would you do that ? Adobe’s documentation doesn’t really say anything about component creation, only about how to skin the existing components.

I posted a question on one of Adobe’s forums, but it didn’t get answered. I don’t know, maybe I wasn’t clear enough or I just didn’t post it on the right forum. Anyway, I was able to find some valuable information on a few blogs. A step-by-step tutorial on how to build fla-based components for Flash CS3 can be found here (FlashBrighton) and here (you should read the comments too).

Currently, Flash CS3 supports two types of components: swc-based components and .fla based components. If your components don’t need any assets or skinning, probably the traditional .swc components will work just fine. These types of components are created exactly the same way as in Flash 8 or earlier. But if you create visual components, which are skinnable, you should probably choose the .fla based components, since the new way of editing assets is pretty convenient to everybody.

How to create a simple .fla component

In case of .fla based components for Flash CS3, there are a few more steps to follow:

1. First, create your component’s class and .fla files. The .fla file must contain whatever assets you need for the visual part of the component, a component shim, a component avatar and the movie clip corresponding to your component (with the correct linkage id and class associated).

2. In your .fla file create any artwork and skin clips you need for your component. Give them the linkage ids you need. Next, create an empty movie clip which will have the same name as your component. Don’t forget to give it a linkage id and associate your component’s class to it (Properties panel).

3. The component’s avatar is basically the bounding box. To create this avatar, you need to create an empty clip and draw a rectangle into it at the x=0 and y=0 coordinates. Then, drag the avatar clip from the Library into the first frame of the movie clip corresponding to your component. This avatar must be the only clip/shape on the first frame of your component’s clip.

4. The component shim is a compiled clip which has to have embedded into it all the classes your component needs. To create a component shim, you should open a new document and create as many empty clips in the Library as classes you need to embed (if you do not embed the classes into the component shim, you will have to give your component’s users the .fla file along with any .as file it uses). For each movie clip, you have to set in the Properties panel, the class to which it is associated (in case your component uses more than one class). Finally you’ll have to create one more clip and, in the Class edit box, of the Parameters panel, you should write a non-existing class name (you could use even “ComponentShim”, though, I belive it is better to use a different name for each component shim you create for your components). Convert the last clip into a compiled clip and copy it into your component’s .fla file. For any other details about the component shim, you should consult this article on www.flashbrighton.org.

5. Next, on the second frame your component’s clip, you need to place all the assets of the component: movie clips for the different states of the component, different artwork you need, a focus rectangle (if your component needs one) and the component shim.

6. Finally, right-click on the component’s clip and open the Component definition panel. Here, you need to set the main class of your component, check the Display in Components panel checkbox (otherwise it won’t appear in the Components panel) and set the Edit frame property to 2 (that way, when the user double clicks on your component, the contents of the second frame will be displayed – the component’s assets). In addition, you may set an icon for your component (click the button under the “Description” label and choose a predefined icon or your own custom one, or you can also use the [IconFile("iconName")] meta tag in your component’s class) and a live preview (if your component needs one).

7. To set up a live preview from an external .swf file, you need to create a new .fla document which has the fl.livepreview.LivePreviewParent class as document class and place your component on the stage (which has the same height as your component) at the (0, 0) coordinates; next, create the .swf file and, in the original .fla file of your component, give the new .swf file as your component’s live preview, in the Component Definition panel (I usually choose Live preview with .swf file embedded in .fla file).

8. After you have finished, you need to place the .fla file in the flash components folder

[Windows 2000/XP] Documents and Settings\userName\Local Settings\Application Data\Adobe\Flash CS3\language\Configuration\Components

or

Program Files\Adobe\Adobe Flash CS3\en\Configuration\Components\ – this path works too.

Fla based complex components that contain other components

In case you develop a component that makes use of other components embedded in it (the case of Adobe’s TextArea component which is composed of the TextArea component and the UIScrollBar component), one problem arises.

I’ll give you an example:

If you create a scroll bar component you need to put it into the flash components path to be able to access it from the Components panel. Next, you decide to create a TextArea component which uses the scroll bar component (it will be embedded into the TextArea .fla file). After you finish developing the component, you copy the .fla file to the flash components path. Next time you start Flash CS3, in the Components panel, you will see one TextArea component and two scroll bar components.

This happened to me while I was working on a similar component (it uses another component previously developed by me). I looked into the new Adobe UI components sources and it looks like all the UI components are placed into a single .fla file. Looks like this is the case if you develop visual components that contain other visual components and you want your users to be able to edit the assets by double clicking on the component. This will take them into the second frame of the component, where all the assets are, along with instances of the other components you need. Next, they are able to double click on those components too, to edit their assets. This would be the correct way to customize the component assets but it comes with the previously mentioned cost: you would have to deploy your component along with the other components it uses with a single .fla file. So, if someone would like one of your components used by that complex one that you’ve created, he/she would have to get the .fla file of your complex component, along with all the components it uses.

A work around this inconvenience would be to include the other components into the compiled clip of the component shim, so your component will still have access to those other components but your component’s users wouldn’t be able to directly edit the assets of the other components.

After the release of the V3 components for Flash MX 2004, Flash 8 and 9 with ActionScript 2.0, we started working on the components for Flash CS3 with ActionScript 3.0. So, after a month of Flash CS3 and AS3 here’s a personal overview of Adobe’s new product.

The new language features were a welcome addition and the rebuilt framework proved to be better than the previous Macromedia V2 architecture (at least, this is my opinion after a few days of work with AS3 and the new Adobe framework). In my personal opinion, AS 3 is a big leap forward, though it has its own problems (a few design faults- things I would have done a little different), but still, I’m already falling in love with AS3 (I started programming in C/C++ and Delphi, so I’m glad they decided to base the new language on the ECMAScript).

The “new” IDE looks better than the old one, but, I believe, it doesn’t perform as well. The transparency of the panels uses significant system resources and it’s not so easy to place them in the desired position, they have the tendency to attach them selves to other panels. The new ActionScript editor is better than the previous one and besides it, the new Flash CS3 has a few more interesting features (the possibility to import Photoshop files with their layers, advanced debugger or the new, easily skinnable, interface components). But, I’ve read other people’s opinions and I agree that for those who use Flash mainly to create animations and user interfaces, Flash 8 it’s more suitable. Those who need Flash with AS3… it’s clear… they need Flash CS3.

Finally, I give two thumbs up for ActionScript 3.0 and… let’s say… half a thumb up for the new IDE.

negush

We’ve just launched the MCTE V3 (MovieClip Transition Effect V3), the one and only flash transition manager, with lots of included patterns and customizable presets, the MCTE is maybe the most important flash component that ever launched.

We’re now working on various custom patterns to add value to the MCTE V3.
Visit the MCTE V3 page.

The story of the MCTE V3

We wanted to help flash users to make show/hide MovieClip animations without knowing to code, in a fast reliable way. After we released the Square Effects component we started to think about a component that will be used for all possible transitions between 2 different states of a MovieClip and we came up with the idea of THE MovieClip Transition Effect (MCTE).

With lots of patterns, having their own presets, with some customParams, a general Gain parameter, and with customizable tweening, MCTE V3 is simply the most easy to use, the most customizable transition effect ever.

We are currently developing other cool effects for the MCTE so all previous customers will not need to learn new component models after using MCTE. Once you understand how MCTE works, you can use it for all your animations, both frame animations, and dynamic animations, and change the patterns and presets at a blink of an eye.

The mass preorder rate that MCTE encountered convinced us to develop further patterns and packages (Both AS2.0 and AS3.0) and to improve the MCTE in order to fulfill your needs; this is why we want to assure you that working with the MCTE will be an easy job.