Status update
13
Sep4
Sep4
Eep, I forgot about this on Friday. Better late than never!
Plugin Update Awareness
Status
- Implemented in-page notification
- Implemented startup check and opening on webpage
- Wrote unit tests
- Submitted patch for review
Loose ends
- None
Next steps
- Fix stuff that comes out of review, if any
Target for next week
- Close project
Taskfox
Status
- Passed the reins to Labs for more Labsy iteration
Reflections
- Spaghetti tastes good, but spaghetti code doesn’t
Related posts:


10:40 AM on September 24th, 2009
(planet.mozilla.org had a link to http://pfs2.ozten.com/demo.html but I don’t know who wrote it. If it wasn’t you, can you forward this?)
For my 64-bit Firefox 3.7a1pre nightly on Kubuntu http://pfs2.ozten.com/demo.html says
“Outdated
Shockwave Flash 10.0 r32″
, but http://www.adobe.com/software/flash/about/ says “You have version 10,0,32,18 installed” and lists this as the latest version available for Linux.
BTW, that Adobe page (which you get to from “About Adobe Flash Player” in the player’s context menu and is one of the most popular pages on the web) should warn if you don’t have the latest version. It makes the user compare two numbers instead of doing it for them. Try giving your code to Adobe…
11:38 AM on September 24th, 2009
The database that is backing up that demo is all funny data.
We didn’t have real data yet, and for many plugins we still don’t. It was the first time we got the frontend and backend code talking to each other…
skierpage, thanks for trying it out and we have much better data (and a real stage env) so we should have something much more realistic by EOD tomorrow.
12:12 PM on September 24th, 2009
Thanks, Ozten.
1:16 PM on October 3rd, 2009
This page is in a testable state now
https://www-trunk.stage.mozilla.com/en-US/plugincheck/