Now the question is will people be more at ease with a form in OO.o instead of their browser. I think for a large part of the target audience (that still uses computers as glorified typewriters) the answer is yes.
I think so. But heck, let's try it. Let's get someone to write an XForms OOo plugin for filing issues. Let's test it, show it to people, see what they think. It if looks good, then we add it to the next release and see how users respond.
Actually it's been mentioned, I think by at least a couple of users on other lists, that they thought the mechanism to report issues should be in OOo itself (of course they usually added other requirements such as OOo magically identifying the problem description, capturing the relevant steps that led to said problems and telepathically transmitting the information to the developer that wrote the lines that caused the issue).
Joking aside, I think making it easier to report issues is a good idea, with just the caveat that automating it from OOo might generate a lot of insufficient input (imprecision of the description, lack of reproducible steps, etc) that will end up directly in IZ, meaning in the lap of the QA people who will have to try and make sense of the report and request more details through IZ, which will drag the user right back into the (apparently) dreaded IZ world.
At least at the moment when a user wants to report a problem (without knowing about or wanting to go to IZ), the request usually ends up in the users@ lists, where more people than just the QA can ask for more details, confirm/infirm the problem, all this before an issue is submitted. Basically I fear for the load on the QA contributors if there's a direct route from OOo to IZ. But I may be wrong.
Cyrille
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
