Differential D9102
UI - System Console Messages Authored by Harley Acheson (harley) on Oct 3 2020, 7:42 PM.
Details
Might seem a bit silly, but this is just an attempt to make the system console messages make a bit more sense. The patch changes the messages from what you see on the top of this capture, to what you see at the bottom:  The appearance of the system console can itself be a bit confusing to new users, but my hope is that by starting with "Starting Blender..." it is initially more obvious. And the formatting of the rest of the lines makes the startup process easier to follow.
Diff Detail
Event TimelineComment Actions On the face value this seems nice, but this information is really only for developers or technical users. Personally I don't especially like using too much vertical space in my console, especially for not-very-useful information that's repeated every time. The current messages could be improved (consistent capitalization, quoting ... etc). Further I'd leave them as is. There is another issue - do we want to move these to logging, so it's possible to configure them. Comment Actions Aesthetically, I prefer what you are proposing. You could also make use of indenting to better relate the paths to their heading. The issue Campbell and I saw is that this further increases scrollback with little valuable info. Like 99% of time I don't care about these prints, they are just kinda in the way. Now we put them even more in the way. Comment Actions I don't think we should print "remove prefs" and "found bundled python" by default. It may be useful in some cases, but it's just a small subset of potentially useful information for debugging issues. I'd rather see ways to more easily generate or access complete debug logs for users. Always printing when reading/writing scene .blend files does seems reasonable to me, but other than that I would only print errors. Comment Actions Abandoning for now. LazyDodo has demonstrated redirecting this stuff so we are hoping to get these into Info Editor. I was just waiting to see if we were going to first get changes to Info from Summer of Code. If that takes too long we could push ahead with that anyway. If that stalls, or we can only redirect after a certain point in startup, then we could always come back to this idea and pretty up what is shown. Comment Actions Good point re "found bundled python", I don't notice this since I'm mostly using dev builds where it doesn't print. I added this when first bundling Python and IIRC there were some issues not finding Python that needed investigation (also before we had logging options), moved to use logging so it's hidden by default. rBd49c71e96e55: Cleanup: use logging for "Found bundled Python" message As for reading preferences, IIRC it can be useful when figuring out which app-template is being used... although this should be moved to logging too.
+1 |