> I checked out writting flash code and, I am sure you have heard
> this, the naming convention is ridiculous. Stage? Actor? Wha?
> Most developers have spent quite a bit of time learing what
> object, methods and the like are all about - why come up with
> a totally unique language describing things that dont need it?
You're right, the authoring metaphor in the Macromedia Flash MX 2004
authoring tool is built around the mental model of someone who comes in
from visual design, rather than from abstract design.
The form-based development in the Pro version is a help (it's similar to
the mental model used in Visual Basic and similar tools), but it's not like
the text-based editing coming soon in Macromedia Flex.
Key concept: The development environment can be separate both from the file
format, and from the runtime environment. Flash technology has outgrown the
single integrated authoring tool... the SWF file format, and the Macromedia
Flash Player, offer things to people who prefer to develop in very
different ways. The file format and clientside runtime engine are no longer
linked to a single type of development environment.
(For David Becker's CNET article, there's existing discussion on blogs from
me, Mike Chambers, David Bisset, Jesse Ezell, others.)
jd
John Dowdell, Macromedia Developer Support, San Francisco
(Best to reply on-list, to avoid my mighty spam filters!)
Technotes: http://www.macromedia.com/support/search/
Column: http://www.macromedia.com/desdev/jd_forum/
Technical daily diary: http://www.macromedia.com/go/blog_jd
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
