Jump to content

Recommended Posts

Posted

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.

Posted

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?

Posted
Maybe a talk on Flash replacements as they have finsihed with flash now.

 

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?

Posted

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.

 

Flash and accessibility

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)

Posted

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.

Posted
Licensing - More flexible per-product site licensing. Why can't I buy a Photoshop site license if that's all I want?
Posted
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)
Posted

It looks like they may be doing a live demonstration of their new Adobe issued flack jackets :)

 

Perhaps they could do a problem solving session with common faults and their recommended solutions although a 'pelt an Adobe developer with rotten tomatoes' session would probably be very popular :D

Posted
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 their phone lines are so hard to get through? :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...