Back to the Future

One thing I would like to see some disucssion about is this idea of "event-driven" development vs "timeline-based" . I have talked to a lot of traditonal developers (VB, C++, and Delphi types) who just don't get timeline-bases dev and it was rumored Macromedia was going to try and solve this problem with the next version of the Flash IDE. I haven't seen much of the 2004 Professional so I really can't talk to it. Can anyone else? If Macromedia solves this problem I can finally see Flash RIA really going mainstream.

Here is an interesting article:
"Macromedia Plays Drag-and-Drop Game"
http://www.cbronline.com/latestnews/673d490507d3735b80256d8d0018b96e

Your second paragraph describes exactly how I feel right now. I'm excited about new things, but the pressure is on to learn them quickly. I always develop a personal project when a new version of a program comes out, just to learn.

I think that the real "pro" part of the professional version is it's ability to compile ActionScript 2.0. Unless I'm mistaken, the regular version won't be able to use it. Also from what I understand you won't be able to edit ActionScript 2.0 files using the actions panel, but only in external files. That's a little odd.

The best review I've read so far is at Flash Magazine

I share your feelings Todd. While it is always exciting to check the multiple improvements to the forthcoming version of Studio MX, I hate to realize that with it, usually comes another paradigm shift that will demand time - ever scarcer time- to adjust myself to. That's why I get a little weary of what I call the Macromedia merry-go-round sometimes.

And what is this "Actionscript 2.0" business anyway? Still, the make-or-break deal to me will be if we will finally have Flash (the app and the plugin) running decently in OS X.

It sucks the big one that you will have to shell out more for the Pro version in order to have video support. Perhaps a well-calculated move on MM's part.

I think the upgrades are coming too fast and older versions that folks are just getting used to are being shelved way before their time.

As for the public, maybe eventually people will get sick and tired of downloading new Flash Players every few weeks (it seems)...maybe when Macromedia sees that new Flash Player penetration is something like 25% after a year or two for some new future version, then they will hold their horses for a while. It gets a little frustrating even for a techie to stay on top of these things...after all, even us geeks have another life.

Yes, the upgrade cycle seems to be getting worse with very many programs. It's like they feel they need to do "something" just to keep the cash-flow coming in. What irks me most is when an applications upgrade features "bug fixes". It feels so good to pay for the version you already thought you bought before!

I do agree that it takes a lot of time to keep up, luckily Flash MX is my full-time job so I can do it. There are a HUGE number of benefits for app developers like me - better, less buggy components, data connectors, localization tools, and *Actionscript 2.0* - a new strongly typed language that will allow me to program in such a way as less bugs get in my published SWF. In addition - its backwards compatible meaning I can publish for Flash 6 player, and still have a nice coding environment.

For people with lite programming experience, there are some new media components that will really simplify creating media playback interfaces with stop-points, as well as a director-ish 'behavior' programming model that will allow a new, easier method for people to "wire" interfaces using small, reusable functions.

I am excited!

I have just taken a deeper look at Actionscript 2.0, and I joke with my peers that it looks like the bastard son of Java. The syntax, routines, methods... It can't get more Java-like than this. Lazy coders will probably balk at now being forced to declare variables' type and $'ing them all (a la PHP) but if that leads to a leaner, less buggier, and more versatile AS, I'm all for it.

I don't use Flash, but I did decide to finally buy Fireworks MX--yesterday (the day before the new versions were announced). I feel like the guy who went to the hardware store and bought 10 gallons of paint, only drive by the store the next day and see a sign that says "Huge Paint Sale Starting Today!"

The upgrade to Dreamweaver looks interesting to me, only because it looks like it finally supports CSS layouts in Design View. My site is laid out with CSS and looks ridiculous in Dreamweaver MX so I went back to hand-coding. But now...

The new flash looks hot, but I am hoping it wont be a dud root so to speak.

it might even convince me to go back to flash.

Well.. I guess I'm not the only one to feel ambvivalent about a new Flash version. Although new features gets you exited, my first feeling was that - "PHP has to wait a while."

jeez. glad i do not have to deal with this new beast. Working with online media feels like working at the post office– a never ending stream of other peoples garbage.
I LOVE PRINT.

That's funny. I left print because I thought online design would be more predictable. Can I go back?

But is the actual programme better? New technologies are all very well, but for many many people the current Flash tech does enough (especially those who don't believe Flash is the best way to create applications)... so therefore, have they put time into making the actual application easier to use, more productive, faster, etc? After all, I don't want new JPG technology from Photoshop 8, I want it to make it easier and quicker to make JPGs.

To the comment about upgrading the actual plugin - one of the new features of the Flash 7 player is that it self updates, without action from the user. How well this is implemented is yet to be seen - but I hope I won't be hearing things like "I went to your site and it said it was upgrading my computer, thanks!"

My only anxiety about the upcoming release is how quickly to implement some of these cool new features (CSS text box!) in any new client sites. Now we just need some of those animated e-cards to start distributing Flash 7 to the masses...

And as much as I'd like the actual Flash app in OSX to behave like Illustrator 8 (flat ended strokes anyone?), I'll settle for a more responsive GUI and better runtime performance for the Player on Mac.

Actioscript 2.0?, aww I miss my cryptic slash syntax...
setProperty (../../../holder/clip, visibility, 0)

Howdy, sorry I'm late to the discussion... quick notes:

-- Upgrade rate: It's been about 18 months, same as most other tools.

-- "timeline" vs VB: Yes, that's the intent, to provide multiple models of creation to SWF... 30-day trial should be available very soon, if you'd like to examine hands-on.

-- "ActionScript 2.0": LIke later versions of ECMAScript, which is more like Java, true... evolutionary change, not revolutionary.

-- Player penetration: Adoption rate has actually increased version-to-version... there were indeed multiple minor-version updaters in the last version, as more studied it for potential buffer-overrun exploits, so there were increasing security improvements over the last 18 months.

-- Recent purchases: If you bought within the past 30 days we'd also like to send you the new version free:
http://macromedia.com/support/service/ts/documents/current_offers.htm

Regards,
John Dowdell
Macromedia Support

John, thanks for replying here, especially for mentioning the free upgrade policy for people who recently purchased -- I would not have known about that otherwise. I'm going to take advantage of that for Fireworks, which means I can now afford to buy the upgrade to Dreamweaver (which I otherwise might have skipped). Thank you.