Ted Patrick - Demos & MAX @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
Improve Flash 10.1 and AIR 2.0
DIGG IT!
11
Comments
Published
Sunday, February 07, 2010
at
7:53 PM
.
Adobe engineering is headed into the final stretch of development of Flash Player 10.1 and AIR 2.0. We need community help to identify quality issues with your deployed and in-development content. While both Flash and AIR are tested extensively internally, every beta we receive valuable feedback from the Flash community and beyond.Here is how you can get involved:
Download and install Flash Player 10.1 Beta 2 and AIR 2.0 Beta 2
Test the new beta runtimes with your content and applications.
Log bugs at bugs.adobe.com. Engineering teams use your bug reports to reproduce errors and improve the runtime quality.
As far as beta timelines, beta 3 releases are a few weeks away and release candidates are expected within 60 days. Your involvement and assistance during this critical development window is really important and will only improve Flash Player and AIR quality.
Please also help spread the word about the beta process via Twitter:
Improve Flash 10.1 & AIR 2.0 via Beta 2 http://bit.ly/cty7Nm READ & RT #Flash #AIR #QUALITY
Special thanks
Ted :)
11 Responses to “Improve Flash 10.1 and AIR 2.0”
Post a CommentWhere to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- Simple Method Closure in AS3
- Making Su (sudoku)
- Sizing AIR NativeWindow to Stage
- CoolIris Express Launches - Put a 3D wall anywhere...
- Demos & MAX at Adobe - A new role
- Learning Fx4 from Scratch - Update 2
- Learning Fx4 from Scratch - Part 1 - Application
- SOURCE to 4 Flash iPhone Apps
- ADOBE MAX 2009: SESSIONS NOT TO MISS
- Learning Flex 4 ... from scratch!
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
- December 2009
- January 2010
- February 2010
- March 2010
I'd love to see Flash incorporate a crash reporter like Firefox or even like the old bug icon that Apple used on Safari when it was in beta.
Bugs.adobe.com is fine for developers, but I've always felt the average person will never know about this page or bother to jump through the hoops to sign up.
Something as simple as an option in the contextual menu like "Report a Bug" and it redirects the user to a simple web form on Adobe.com, capturing their system stats for them.
Maybe in the next beta.
As for myself, I'd kindly test, report and suggest features, but I've already done so and stumbled upon a show-stopper grade bug that isn't getting worthy attention from Adobe: [#FP-3186] Keystroke triggers double entry in input TextField. This, as you can tell, prevents me from running Flash Player 10.1 Beta 2 further.
I've also published similar concerns in Flash Platform is at a crossroads article.
I'd love to see a bug section @ bugs.adobe.com named "air" or "air2.0" ...
JohnQ, it not a good way to report bugs through crash reporter, it will end up having duplicate bugs report.
Anyway there are already enough testers worldwide, unlike Firefox has more complicated architecture as to Flash in term of size and features implementation.
Serge's post on quality improvements
Great call to action!
Blogged: "Help Improve Flash 10.1 and AIR 2.0*" http://bit.ly/9Va2R9
@yanil - it's better than nothing. There are enough users who face various bugs, crashes everyday. They are either unaware to file the issues in proper way (JIRA) or procrastinate doing it.
Having a feedback panel (that can be launched on demand without loosing the context) and bug-crash-reporter would be useful. However, there must be a way to turn off crash-reporter, if one wants to.
-abdul
Flash Player 10.1 still kills Captivate 4 for me during testing - test publish gives me an unusable file.
At least I can *run* Captivate 4 with the latest 10.1 beta. It used to refuse to launch, so some improvement :-)
Did they ever fix the security sand box issue w/ remote services?
Seams like no one is working on the old bugs.
My blog entry on fixing bugs before the next major Flash release:
http://matthewfabb.com/blog/2010/02/08/help-find-bugs-before-the-new-flash-player-is-released/
I also mention that it would be great to include a link to bug.adobe.com in the right-click content menu of Flash, to make more people aware of the open bug database outside of the Flash community.
I'd love to do more test, but this issue http://forums.adobe.com/thread/553774 keeps my application from even bootstrapping properly.