Flasher Archive
[Previous] [Next] - [Index] [Thread Index] - [Previous in Thread] [Next in Thread]
Subject: | Re: FLASH: best director book (is: D for F users) |
From: | John Dowdell |
Date: | Wed, 19 Jul 2000 21:48:43 +0100 |
At 2:17 AM 7/19/0, Dean Kerrigan wrote:
> Does anyone have a recommendation for the best Director book
> available for some one who already knows the basics and is
> competent with Flash actionscripting?
Actually, I haven't seen any book that has taken this approach... "Now that
you know how to work in Flash, how can you transfer those skills to
Director?"
This has been simmering on my back burner for a technote, but hasn't pushed
its way to the top of the stack yet... here are some roughcut notes:
-- Canvas: Both have a stage... you drag things out and arrange them, then
export. Flash's working area is resolution-independent, but Director's
working area uses a fixed pixel size.
-- Library: Flash has a symbol library. Director has a cast library. In
Flash an object on screen *may* be a symbol; in Director every sprite on
screen is *always* a castmember. (Rephrased, every single media element in
Director is in a library.)
-- Timeline: Flash uses nested timelines, and you navigate the object
hierarchy to have one object talk to another. Director uses a single
timeline (for the most part), and messages are broadcast along an explicit
event hierarchy.
-- Events and scoping: In Director, a mouse click on a sprite can be
handled by that sprite's behaviors. If the event is not handled, it can
then be captured and evaluted on any script for that castmember.
(Translation: if a symbol instance doesn't handle the event, then the
symbol master can handle it.) If the event is still not handled then it can
be captured and handled by a script for that frame, or a global-level movie
script. The basic hierarchy for handling events is
sprite->castmember->frame->movie.
Variables are usually local to a script. There are also global
variables, available from anywhere in the application. A script instance,
such as a drag'n'drop behavior or parent script, can have its own
persistent protected variables too.
There are lots of other differences in media and handling and strategy and
delivery and what-all, but the above are some of the biggest working
differences I see: the Stage is pretty much the same, Libraries are a
little different, the nested timelines of Flash aren't used but a broadcast
method is, and event flow and scope are a bit different.
I'd appreciate if other folks could refine the above, say what was
important to them when they expanded their skills from one to the other...
thanks!
jd
John Dowdell, Macromedia Tech Support, San Francisco CA US
Search technotes: http://www.macromedia.com/support/search/
Offlist email risks capture by the spam filters. I may not see your
email if it's not on the list. Private one-on-one email options are
available via Priority Access: http://www.macromedia.com/support/
flasher is generously supported by...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
flashforward2000 and the Flash(tm) Film Festival
July 24-26, 2000, NEW YORK CITY, Hammerstein Ballroom
www.flashforward2000.com
Produced by United Digital Artists and lynda.com
Sponsored by Macromedia, Adobe Systems, Fusion, Inc, AtomFilms,
shockwave.com and Electric Rain.
1.877.4.FLASH.4 or (1.805.640.6679 outside the US and Canada)
Register before June 30 and save $200!!-- www.flashforward2000.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To unsubscribe or change your list settings go to
http://www.chinwag.com/flasher or email helpchinwag [dot] com
[Previous] [Next] - [Index] [Thread Index] - [Next in Thread] [Previous in Thread]