Flasher Archive

[Previous] [Next] - [Index] [Thread Index] - [Previous in Thread] [Next in Thread]


Subject: Re: FLASH: processor occupancy tests?
From: Nigel Randsley-Pena
Date: Fri, 06 Nov 1998 00:31:06 +0000 (GMT)

David,

Starting from the end. flash processor usage is really quite normal.
Flash is vector based so all its elements, discounting foreign ones like
bitmap and sound of course, are described as vectors. This is a very
good way to describe obejcts in 2d space, in fact it's an excelent way
to describe objects in n-space, not only 2d. Transforming a vector
defined object is usually associated with a transform matrix that
multiplies the object, now this is where the downside of vector based
graphics show up. This process is cpu consuming as matrix multiplication
is not optimized in current normal cpu's. This is by the way why until
the advent of the pentium class cpu's vector based graphic solutions
where limited to the likes of Illustrator, Freehand, etc..
So what Flash represents is a very compact way to represent animations
allowing for use over the web but once it arrives at the client machine
it does need a good cpu.
As for the first question. the fact that you have lines or not doesn't
impact to much. As for the tweening. A scale tween is a simple matrix
transform while a shape tween can be much more complex. this does not
signify that one is always faster than the other as other factors have
to be taken in account. You're best bet is to build up your feeling for
it from working with the program and experimenting.

------------------------------------------------------------------------
To UNSUBSCRIBE send: unsubscribe flasher in the body of an
email to list-manageratshocker [dot] com. Problems to: owneratshocker [dot] com
N.B. Email address must be the same as the one you used to subscribe.
For info on digest mode send: info flasher to list-manageratshocker [dot] com



Replies
  FLASH: Site Critique, Todd Purgason
  FLASH: processor occupancy tests?, David Gary

[Previous] [Next] - [Index] [Thread Index] - [Next in Thread] [Previous in Thread]