The current state of logging is a bit messy, to put it mildly. There is no single convention to how these messages are formatted (lowercase, uppercase, values in ' ' or not, etc.) and every part of the program has a different way of formatting them. The info log level is also not used how it should be, informing the user what the program does or has done. It shouldn't contain debug information. This is for the debug log level, which is currently spammed by the html parser, so we'll have to disable the log output of the parser. The debug log level should contain very detailed information about what the program is doing, like for example if a view is created, a log message should be printed with the message creating view {name}. When this view is added we should print another message, adding view {name} to {view}.
Note: This feature is being developed on a branch that emerges from the UI overhaul branch (#80). This means it is also merged into the UI overhaul branch and not the main branch
The current state of logging is a bit messy, to put it mildly. There is no single convention to how these messages are formatted (lowercase, uppercase, values in
' 'or not, etc.) and every part of the program has a different way of formatting them. The info log level is also not used how it should be, informing the user what the program does or has done. It shouldn't contain debug information. This is for the debug log level, which is currently spammed by the html parser, so we'll have to disable the log output of the parser. The debug log level should contain very detailed information about what the program is doing, like for example if a view is created, a log message should be printed with the messagecreating view {name}. When this view is added we should print another message,adding view {name} to {view}.Note: This feature is being developed on a branch that emerges from the UI overhaul branch (#80). This means it is also merged into the UI overhaul branch and not the main branch