Logging function and error dialogs missing

[GoogleCodeExporter]

Currently jME3 lacks logging functionality. This means that any error messages 
will be dumped nowhere, since by default Application.handleError() prints them 
to  (non-visible) console and kills the app.

jME3 needs the capability to enable logging and error dialogs.

Original issue reported on code.google.com by ShadowIs...@gmail.com on 6 Jul 2012 at 2:34

[GoogleCodeExporter]

I agree but I think this is flexible enough. If the default app 
templates/harnesses just have some way to display the error via a swing panel 
or android dialog. I think this is something that the user miht want to 
configure and handle himself like 3097 or whatsisname does (e.g. Auto-report 
functions, solution wizards etc.)

Original comment by normen667 on 6 Jul 2012 at 3:18

[GoogleCodeExporter]

User configuration should definitely be possible, yes. However in the common 
case where Application.handleError() is not overridden, the app simply goes to 
desktop if an error occurs, from user point of view this is unacceptable. At 
the very least there should be an indicator that a crash has occurred and what 
steps can the user take to resolve the issue. Furthermore, the lack of 
standardized file logging means that even if such error occurs, the developer 
won't be able to debug the issue on customer PC without updating the app to 
support logging. For the aforementioned reasons I am elevating the priority of 
this issue to high.

Original comment by ShadowIs...@gmail.com on 6 Jul 2012 at 3:46

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

... this would require os dependent features inside the engine, so something 
that can only be done in the system delegates. So its easy, if you really want 
this in the core engine and not in the application harnesses or templates then 
the default behavior of Application should be calling a new delegate method and 
implementing stubs for these.

Original comment by normen667 on 6 Jul 2012 at 3:49

[GoogleCodeExporter]

Currently working on adding a method to JmeSystem that will show an error 
dialog. On android there's already an exception display printed out on screen 
but there's no clear cut way of sending the log to the developer. By default an 
application exception in Android will allow the user to report it to the 
developer, jME3 should facilitate this use: 
http://lh4.ggpht.com/_rhCtHYLiamQ/TNMXXTX_33I/AAAAAAABf0U/P92tYhd0JTA/snap201011
04_162116.png

For Windows, jME3 should show a similar dialog but one that allows copy-pasting 
the error or emailing it to the developer.

Original comment by ShadowIs...@gmail.com on 9 Jul 2012 at 3:31

• Changed state: Started

[GoogleCodeExporter]

@Normen: Can we enable file-based logging by default in jME3? I believe this is 
a necessary evil. I understand we have had issues with jMP being slow while it 
was enabled, is there any way to avoid the slowdowns? 

Original comment by ShadowIs...@gmail.com on 4 Aug 2012 at 9:20

[GoogleCodeExporter]

I don't know what specifics of the logging made it slow but if theres a way to 
disable it then I guess we should be fine.. Maybe another SystemDelegate case?

Original comment by normen667 on 6 Aug 2012 at 11:10

[GoogleCodeExporter]

Original comment by ShadowIs...@gmail.com on 6 Sep 2012 at 6:11

• Added labels: Difficulty-Easy