2012-07-05, 19:42
Hello everyone,
I made this thread to help out people/developers who stare at the log file for several hours trying to know what did go wrong with their python script and/or XML windows, like me
I find that the xbmc.log file is a big chunk of unorganized block of text that was hard to search for what did go wrong in the application/add-on that is currently being tested specially when it needed to refresh constantly, so i wrote a little utility that sorts these information based on the severity levels from the wiki and make it somehow readable and make the development process less painful.
you can find it here: http://code.google.com/p/xbmc-monitor
I would like to hear your thoughts/opinions or if you have suggestions, However note this program was written solely to speed up my development process and is not by any-means commercial.
enjoy
I made this thread to help out people/developers who stare at the log file for several hours trying to know what did go wrong with their python script and/or XML windows, like me
I find that the xbmc.log file is a big chunk of unorganized block of text that was hard to search for what did go wrong in the application/add-on that is currently being tested specially when it needed to refresh constantly, so i wrote a little utility that sorts these information based on the severity levels from the wiki and make it somehow readable and make the development process less painful.
you can find it here: http://code.google.com/p/xbmc-monitor
I would like to hear your thoughts/opinions or if you have suggestions, However note this program was written solely to speed up my development process and is not by any-means commercial.
enjoy