On Sept. 15, 2009, Adobe Systems Incorporated (Nasdaq:ADBE) and Omniture, Inc. (Nasdaq:OMTR) announced the two companies have entered into a definitive agreement for Adobe to acquire Omniture in a transaction valued at approximately $1.8 billion on a fully diluted equity-value basis. Under the terms of the agreement, Adobe will commence a tender offer to acquire all of the outstanding common stock of Omniture for $21.50 per share in cash.

Adobe’s acquisition of Omniture furthers its mission to revolutionize the way the world engages with ideas and information. By combining Adobe’s content creation tools and ubiquitous clients with Omniture’s Web analytics, measurement and optimization technologies, Adobe will be well positioned to deliver solutions that can transform the future of engaging experiences and e-commerce across all digital content, platforms and devices.

Read Adobe Press Release here

*) Image belong to Adobe.com

Flash :

Google can now discover and index text content in SWF files of all kinds, including self-contained Flash websites and Flash gadgets such as buttons or menus. This includes all textual content visible to the user. Google supports common JavaScript techniques. In addition, we can now find and follow URLs embedded in Flash files.

Silverlight and other rich media formats:

Google can crawl and index the text content of Flash files, but we still have problems accessing the content of other rich media formats such as Silverlight. These rich media formats are inherently visual, which can cause some problems for Googlebot. Unlike some Internet spiders, Googlebot can read some rich media files and extract the text and links in them, but the structure and context are missing. Also, rich media designers often include content in the form of graphics, and because Google can’t detect words included in graphics, it can miss important keywords. In other words, even if we can crawl your content and it is in our index, it might be missing some text, content, or links.

read more detail here

Robert Penner has develop new approach for AS3 events, inspired by C# events and signals/slots in Qt. This project call Signals. This can be an alternative solutions to manage your Events.

Here are the Concept and Philosophy sections for a start:

The Concept

• A Signal is essentially a mini-dispatcher specific to one event, with its own array of listeners.
• A Signal gives an event a concrete membership in a class.
• Listeners subscribe to real objects, not to string-based channels.
• Event string constants are no longer needed.

Philosophy

• Composition and interfaces are favored over inheritance.
• Events in interfaces are a good thing.
• Event types are classes, not strings.
• Event classes should focus on the data they contain, not on who sends them.
• Event classes should not contain string constants that various other classes use.
• Test-Driven Development (TDD) is essential and fun.
• So far, not a single static keyword in the source.
• No singletons.

Further more details you can visit  at Google Code project: http://code.google.com/p/as3-signals/

Away3D Lite is not meant as a replacement for the standard Away3D libraries. Because of it’s use of the native 3D features in the Flash 10 Player, Away3D Lite is Flash 10 only, so the development of Away3D 2.5 & 3.5 will continue as usual. These engines are more of a workhorse for many different purposes and with many different features, while Away3D Lite offers the choice to be fast and small at the sacrifice of features. This is not to say that you can’t do anything with Away3D Lite! The list of main supported features in 1.0 includes:

• 3DS, MD2, Collada & Metasequoia loaders
• Bones animation
• Viewport clipping
• 3d mouse events
• All standard primitive types
• All standard camera types
• All standard material types
• Template classes for quick and easy setup

Plus, you will already know how to use Away3D Lite if you’ve used Away3D! Everything is where you’d expect, and there have only been very minor changes made to some property names, which in time will most likely percolate back through the various engines.

Check out more on the site here

*) image rights belong to away3d.com

New AdobeTV site http://tv.adobe.com Moved from full page Flex to HTML+OSMF Flash Video Players. Lighter & faster expierience. It also has a clear URL ex: http://tv.adobe.com/product/flex/, http://tv.adobe.com/channel/photography/, etc.  via @adobeted

It is important to make application as light as it can. First impression is always a great deal. People will leaving if the process take too long and not good for user experience.
The Flash Player cache is a new feature available in Flash Player 9 Update 3 (9,0,115,0). The cache allows files signed by Adobe to be cached by Flash Player. These files end in the file extension .swz.

The Flash Player cache differs from the browser cache in some useful ways. Because the cached SWZ files are signed by Adobe, they can be reused in more than one domain and are not limited to reuse within the domain in which they originated. For example, imagine that framework.swz is loaded from http://www.a.com and is placed in the cache of Flash Player. If the same framework.swz file needs to be downloaded from http://www.b.com, Flash Player looks in its cache to find a.com’s framework.swz file. When it finds a match, it uses the cached file rather than loading a new file from b.com.

The SWZ file persists in the cache even after the browser is closed. The file remains in the cache indefinitely, provided that the end user does not change settings in the Flash Player Settings Manager to reduce their caching ability. However, future SWZ files may eventually cause older, unused SWZ files to cycle out of the cache when the cache size limit is reached.

Fortunately, you need only one copy of a framework, since Flash Player uses a common cache for all browsers on a system. This means that if a user downloads a SWZ file using Microsoft Internet Explorer, that same SWZ file will also be available in Mozilla Firefox.

Read it more at http://www.adobe.com/devnet/flex/articles/flash_player_cache_print.html

If you a social addict, widget collector, developer, flickr user, etc, you should try this 100 tools / application built with Adobe AIR that can help you to maximizing your productivity.

Kuncinya adalah fps, nextPage() / prevPage(), & setInterval().
Karena idenya adalah mempercepat maka fps / frame per second / frame rate perlu didefinisikan paling awal. Untuk selanjutnya melakukan looping dengan menggunakan setInterval() sebagai pengganti play() yg menggunakan kecepatan normal (sesuai fps).
Terakhir adalah setting kecepatan. Untuk mempercepat diset interval looping n x fps. Misal utk percepatan 2x: 2 x fps. Sedangkan utk perlambatan fps / n.

Berikut adalah contoh penulisannya:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

// di timeline
var IntervalID:Number;
var FPS:Number = 31; // nilainya disesuaikan dengan framerate FLA
var speed:Number = 10;
 
function PlayForward () : Void
{
	nextFrame ();
}
 
// di button fast forward
on("release")
{
	clearInterval(IntervalID);
	IntervalID = setInterval(PlayForward, FPS * speed);
}
 
// di button slow forward
on("release")
{
	clearInterval(IntervalID);
	IntervalID = setInterval(PlayForward, FPS / speed);
}

After announced yesteday, about a few hour ago Google Chrome finally available for download.
This browser faster compare to IE7 or even to Firefox 3.0. Much lighter and really cool for the chrome feels. This is recommended browser and you should try it.

Check out Google Chrome related links bellow:

• The Technology Behind
• Video, The Story Behind Google Chrome
• Google Chrome for developer
• Google Chrome plugins related
• Community of Chrome Users

an Official FAQ about SWF and SEO from Adobe can be found here: SWF searchability FAQ