We are attempting to take advantage of the performance improvements claimed for
the upgrade from Flash MX to MX 2004. We have been successful in generating our
app with "Flash Player 6" as the target, but when selecting 7 our app is
entirely broken.

With a little experimentation it appears that we have a number case
sensitivity problems. However, none are showing up as "compiler" issues, we
have to debug to find where the movieclip instances are not being referenced
properly.

So the questions are:
1. Are there any parser or lexer tools that will point out unknown variable
names?
2. Are there any tools that will flag unrecognized keywords?
3. Are there any tools that will aid in translating ActionsScript 1.0 to
ActionScript 2.0?

With over 150 *.as files in our app, we're not looking forward to a hand
re-write.

Any thoughts would be greatly appreciated.

-Eric

wow! that does sound difficult. are there any particular features of the v7
player that you are trying to take advantage of? if not, perhaps you can
continue to compile for v6 player. can't do this forever, but it does buy you
time.

Thanks for the input...

Yeah, the "feature" is the claimed "Boost runtime performance by 2-8x with the
enhanced compiler and the new Macromedia Flash Player 7"

We could always use better performance for the best "user experience". As we
have somewhere north of 36,000 lines of AS code, we'd rather not diddle with it
by hand.

Is there a performance advantage for AS 2.0 over 1.0?
Or, better yet, how much performance can be attributed to each step on the
"upgrade path"?
We have already seen a small boost in going from Flash MX to 2004, though
nowhere near 2 times. Where are the additional gains to be made in compiling to
player 7 and then again in translating to AS 2.0?

-Eric

ok...i'm no expert here, and one would think that macromedia would provide
migration help in some way...at the very least a list of syntax differences
between AS 1 and AS 2. That mx2004 doesn't just handle it is rather irritating
i would imagine (i still have flash MX).

so far, you've mentioned sensitivity as one possible difference...others could
be additional keywords or deprecated functions. the idea of writing some kind
of code parser to distinguish variables from keywords and automatically map
deprecated functions on to relevant one sounds rather daunting.

you might want to try googling or searching actionscript.org or perhaps
flaskit.com. if you can't find anything there, then you might be able to find
some kind of ASP or PHP project that understands flash format....then you could
extract all the actionscript from the image data and maybe put together some
kind of simple text search routine (like GREP thing or perhaps regular
expression search thing) that would find potential troublespots and report
them.

like i said, i'm no expert. there are people on this forum who would know
much better than me...