Debug informations dialogs

[GoogleCodeExporter]

When a problem is detected by the application user can send a bug report to the 
dev team using the menu About/Debugging information.
Actually this action opens two dialogs: "explain your problem", "entre your 
email address" and send the report to the wiki, sending an email to one unique 
dev.
We should rewrite this part like this:
- action open a complete dialog with all needed user params "explain problem", 
"email", may be combo for the category of the bug...
- then when user click on send to dev team -> automatically create an issue on 
GoogleCode? OR send the bugreport link to the dev mailing list and create the 
wiki page.

Original issue reported on code.google.com by eric.mae...@gmail.com on 13 Nov 2012 at 7:12

[GoogleCodeExporter]

I just thought about the same thing, you were faster creating a wish for it.

problem is: automatically bug report creating in GCode needs login via a google 
account.
What could be done VERY easily, is:

About->"Report Error/Wish..." opens directly 
http://code.google.com/p/freemedforms/issues/entry
in the system browser (this is actually what QtCreator does as well.)
So the user can directly enter a bug report (just needs to have a google 
account) and we remove report/bug duplicating and mailing  and wiki etc., all 
in one place.

Would this be viable for you?
If we just create a dialog, we WILL get MUCH reports like "the patient view 
does not work." and with no more information. So the "little step" to log in 
will help us to get better quality bug reports, and the tool on google is 
already there - so let's use it and not write our own...?

Original comment by christian.a.reiter@gmail.com on 14 Nov 2012 at 2:40

[GoogleCodeExporter]

Hummm, we can
- add an entry in the About menu to open Google Issue (Report an issue on 
GoogleCode)
- keep and update the "debug required dialog" with the wiki

In this configuration, I really believe that most of our users are totally 
ignorant on how to feel an issue. So we have to "catch" the problems of the 
user with pertinent questions

Original comment by eric.mae...@gmail.com on 14 Nov 2012 at 3:33

[GoogleCodeExporter]

This issue was closed by revision 21c4a7191cb2.

Original comment by eric.mae...@gmail.com on 23 Dec 2012 at 1:01

• Changed state: Fixed

[GoogleCodeExporter]

Hm. the dialog is not really used at the moment - I don't know if it is what 
you want ATM.
I just connected the "Report error..." to the google code page.
But there is nothing added  as debug information, like the old dialog did - so 
THIS bug here is not really fixed.

Suggestion:
"report error" opens the dialog.
if the user enters a gmail address and is willing to do a proper bug report, 
direct him there and for get the dialog.
If not (another email,  doesn't want to), let him fill out the dialog, and send 
it to <anywhere???> WITH debug information. maybe the web site, maybe the 
mailing list.

It's impossible to add debug information to google issues WITHOUT having 
authenticated first.

What I would do: bug reports like "the feature XYZ doesn't work." are useless. 
If a user doesn't want to login to create a proper bug report, he probably 
won't take time to help us tracking down a bug. So for these users it's more 
convenient to just fire a mail to the mailing list, but let's not automatically 
spam our bug database with auto generated bug reports from users that don't 
really want to take some time helping.

So best IMHO is: directly link to the bug report page.
I kept the bug report dialog for later, maybe we find a better way to 
authenticate agains google and send the debug information as well. maybe as 
attachment.

So I would suggest setting this to wontfix or something like this...?

Original comment by christian.a.reiter@gmail.com on 27 Dec 2012 at 9:15

[GoogleCodeExporter]

Humm, did you check a recent compilation? I've coded this dialog.
It asks three/four useful questions for the debugging process, collects some 
info and prepare an email to the freemedforms-dev list. The user just need to 
send this mail.

Please check and tell me what you think of this.

Original comment by eric.mae...@gmail.com on 28 Dec 2012 at 7:45