Clark Karr wrote: > Rishi's comments are, in my opinion, correct. Assuming the typical XXE user > is intelligent but lacks expertise in technical details (or is uninterested > in learning these technical details), these error message(s) are cryptic, > contain too much information, and don't guide the user to a solution. > > My users run into this problem frequently.
Please note that this problem is specific to Windows and cannot happen on Linux and on the Mac. > I've had to include in the > training material a statement to the effect, "If XXE fails to generate pdf > after the first successful generation, close the file in pdf viewer." > Thank you for this feedback. > Anything that takes the user out of the primary job of writing should be > minimized. These 'context switches' are mentally disruptive and reduce > productivity. > > To that end, please consider: > 1. Have the pdf generation process check before generating the pdf and > tell the user "Cannot generate pdf until the pdf file is closed in pdf > viewer" or words to that effect. We currently don't know how to detect this case, but may be we'll find a way. > 2. Include a 'friendly' pdf viewer in XXE. That way, the user wouldn't > have to switch between applications and the pdf viewer pane/tab could use a > 'refresh/redraw' strategy (instead of locking the file) to 'play nicely' > with the editing panes/tabs. > This is a very high-end approach, may be even a bit overkill, but why not? Can you recommend a 100% Java PDF viewer component?
