Here is

how to use this embed TxEff object within a blog/webpage in 5 easy steps:

1. Choose an effect from txeff.com (you can create your own effect with your own text and save it previously)

2. Get the embed code exactly like you do with youtube videos. (choose “customize” to change object size, background colors, autoplay and loop options)

3. Paste it within your posts and publish.

Since we just started this , we have a promotional offer: send us a link where you have posted an embed TxEff and we’ll send you a free TxEff with Reflection (a non-commercial limited edition upgraded version of the TxEff component).

Here is how the player looks like:

Innovating the Flash world again – TxEff

The name says it all. It’s a text effect component for Flash that will change the way you look at text. It’s specially designed for Flash users and designers that want a quick and easy way of animating a text without any coding. The free basic component contains 3 patterns. The number of patterns doesn’t limit you because in each pattern you can try numerous params. As you will find out for yourself this will just open your appetite for more ways of animating.

TxEff website – a new approach

You don’t have to explore every possible combination of params, we want to help you enrich your number of effects, all you have to do is access the TxEff website http://www.txeff.com/. This is not only a website it’s practically an effect DataBase, on which every time a TxEff user discovers a new effect, he can share it with the rest of the TxEff comunity.

If you go online and see something you like just copy the effect Id and paste it in your Component Inspector and you will have the desired effects without having to think of them yourself.

Enter our TxEff community and get all the benefits that come with it.The component itself is very user friendly. All you have to do is to write the text, access the TxEff component and tweak the params to get the desired effect, drag and drop the effect on text and you have a fully animated text.

TxEff is the result of months of development and the feedback we got from our clients. We spent time thinking what our clients would want and offer them that special something. Everyone on the team came up with innovating ideas on how a text effect component should look and act. The result is a very user friendly, time saving component that doesn’t require any coding.

TxEff’s special offer, ends on December 31 2007

Get the full licensed TxEff which contains a minimum of 50 patterns by March 2008. We’re continuously developing new and complex patterns to suit your artistic need and all this for only $99.97(promotional offer).

There’s more, if buy it in December you will get MCTE for free, or if you have already purchased it, you can get it’s value in discount coupons.

Last week we finally launched the ActionScript 3 versions of our V3 components. So now, when you buy aV3 component, you get the AS2 and AS3 versions (AT THE SAME PRICE 🙂 ). The differences between the two versions of the same component are not so great. They consist mostly in the way the events and event listeners are used (the AS3 versions use the new method with an event class for each component and constants declared for each event). You can find more details about the new way of handling events in the documentation corresponding to each component. However, a few of the components, will also have new properties and methods (this is the case for the AS3 version of the Loader Pro V3 component, which has a new feature: reflection).

For each component, the documentation lists properties and methods used by both the AS2 and AS3 versions and, separately, new properties, methods and events used only by the AS3 version. We’re also working on the AS3 version of our tutorials, so, soon enough, we’ll have them available on the site. Further more, each component has on its page (“How to use” section) issues from our Knowledge Base regarding that particular component. For now, only the AS2 issues are available, but as soon as we translate those issues to AS3, we’ll make them available, too.

Regarding the trial versions of our AS3 components, we will release them only when the encryption software used by us will be available for ActionScript 3. So, now, if you plan to try out our components, you only have AS2 trial versions available (which won’t work in an ActionScript 3 project).

We are really glad that you (our clients) like our components and we hope that the new AS3 versions won’t let you down.

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.

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