@greg:
Thank you; most helpful. Unfortunately, not as soon as I'd hoped, but
at least I know. And I'll definitely add Emmy's blog to my reader.
@jd:
No, I'm not the decision maker. There are issues surrounding:
* Audio issues causing "Netscape" plugin to crash browser (resolved
in r28)
* Concern that AVM2 is not production ready (see #1). The same audio
stream does not crash AVM1 code.
* Concern over user experience of upgrading ("Netscape" restart) as
we look to mitigate #1
* There are no features in AVM2 API that we're using yet.
We actually had a very long meeting between CTO, PM and myself
laying out the pros and cons of developing for AVM2 or earlier.
I'd be happy to discuss offlist if you'd a peak inside.
My opinion is to develop for Flash Player 7 and Flash Player 9 (yuck,
forks), with attempts to migrate our user base as effortlessly as
possible. I pick FP7 because of mobile penetration and things like Wii,
while innovative code should be targeted at FP9. I pick FP9 because it
is being actively developed by Adobe and Apollo, etc. are coming down
the line.
Thanks,
-DT
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
