Printable View
I have a meeting with Adobe later this week and I am to put to them the subjects you want to cover during their session at the conf. It has already been suggested that we do:
Deloyment
Patching
But is there anything else? They are to have a stand as well, so if you want to talk to them throughout the day about subjects not covered by their session you can.
Why do they feel a daily release cycle for updates is acceptable?
That's more of a question for the Q&A part of the talk I think. I need subject areas for them to cover.
Maybe a talk on Flash replacements as they have finsihed with flash now.
Security patch (non) release decisions. For example, delaying the Flash vuln fix for Adobe Reader X until June 2011 on the grounds that it would be "disruptive" and "Protected Mode mitigates the issue" while failing to acknowledge that Protected Mode often (still) needs to be disabled for certain applications that use / generate pdfs to function correctly.
More info about seemingly abandoned software. i.e Authorware - is it dead? If it is can they do the whole crossroads/stake/beheading/wild roses thing so people stop building apps using it?
Have they?Quote:
Originally Posted by FN-GM
From what i read on the internet the current release is the last.Quote:
Originally Posted by webman
FN-GM: I personally don't think that is the case. As recently as this month, Adobe wrote about the future of Flash on their blog: Adobe continues to advance Flash. (Adobe Flash Platform Blog)
Moral of the story dont believe everything you read on the net :DQuote:
Originally Posted by webman
Flash-the-player or Flash-the-content-authoring-package? It'd be something worth clarifying if you have a bunch of Adobe people handy: do Adobe plan to head Flash (the content authoring package) towards outputting HTML5 / Javascript / SVG material, or are they planning to stick with SWF output?Quote:
Originally Posted by FN-GM
Flash and accessibilityQuote:
Originally Posted by Dos_Box
Flash and (in)security
Flash and deploying updates in a sane way
Where Flash fits into a HTML5 ecosystem
Flash and free software (gnash springs to mind)
Again this is probably for the Q&A but I can't make it - can someone ask them about why their testing in enterprise environments is so poor (or "hit and miss" if you're feeling generous)?
Bugs like the DFS issue with Reader X and the problems with AppData redirection that affected several of their products (Reader, Acrobat, and Premiere Elements, just to name ones I saw first hand) are problems that simply should not have been in shipped products. They were evident the moment the program was run in an environment that uses these quite common features.
If they have made a choice not to do this testing themselves (which seems to be the case given the length of time this has been going on now), they either need to broaden their closed beta test base or even run public betas.
A clear explanation of their licensing?
Licensing - More flexible per-product site licensing. Why can't I buy a Photoshop site license if that's all I want?
Further to the above "why does the offline files/sync/dfs issues still exist 10 versions into Adobe Reader" - if they're ever likely to release a light PDF reader (along the lines of Foxit)