Have verbose (e.g. with full OpenGL raport) and non-verbose (mostly only with user's WritelnLog) log streams

[eugeneloza2factor]

This would significantly simplify debugging if something goes wrong, especially for new engine users who may not know yet how to add it manually.

[michaliskambi]

Making all examples set LogGLInformationVerbose:=true would a bit defeat the purpose of having LogGLInformationVerbose=false by default, and why we added LogGLInformationVerbose in the first place.

Some time ago we had only verbose log, and it was not configurable. And the verbose log was really too verbose, it was making people confused -- user's own WritelnLog / WritelnWarning messages could be easily missed, and it seemed like the "log" facility is mostly for internal engine reporting. But it's not, the purpose of CastleLog is to be useful for debugging your own applications with WritelnLog (quite like e.g. Unity's Debug.LogXxx). That's why I made CGE's internal log messages more of a summary (OpenGL(ES) version, modern or not etc.).

Maybe this deserves a different solution, having both "verbose" and "not verbose" log streams.

• Verbose log could go to file, and it could have lots of CGE-internal additional info full OpenGL raport,

• While non-verbose log could be displayed by default e.g. in CGE editor "Output" window, or in Delphi output window and such. Unless there's something alarming (a warning), this non-verbose log should be mostly influenced by user's WritelnLog calls and not be "spammed" by internal CGE messages.

For debugging new user's problem, they usually occur at the developer machine, and then our advise is: Use editor "Help -> System Information" menu item, button "Save To File".

I'm changing the title to reflect my view how to deal with this :)