Added logging priorities and use SDLs logging facilities

By using SDL logging, we can rely on SDL to filter the log messages by
their priority before they get sent to our custom output function. For
example, we now no longer get entries for created and destroyed Window
instances by default, since these have only "debug" priority whereas the
default priority for the "app" category is "info".

We can also get log messages raised by SDL itself in our log now. Log
levels can be controlled per category through the "SDL_LOGGING"
environment variable.

Many existing log messages have been assigned a category based on their
existing prefix.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/gui/abilitieswindow.cpp b/src/gui/abilitieswindow.cpp
index 700fa7ff..d8122bf3 100644
--- a/src/gui/abilitieswindow.cpp
+++ b/src/gui/abilitieswindow.cpp
@@ -145,13 +145,13 @@ void AbilitiesWindow::draw(gcn::Graphics *graphics)
 void AbilitiesWindow::rebuild(const std::map<int, Ability> &abilityData)
 {
     delete_all(mEntries);
-    
+
     mEntries.clear();
     int vPos = 0; //vertical position of next placed element
 
     for (auto &[id, ability] : abilityData)
     {
-        logger->log("Updating ability GUI for %d", id);
+        Log::info("Updating ability GUI for %d", id);
 
         AbilityInfo *info = AbilityDB::get(id);
         if (info)
@@ -166,7 +166,7 @@ void AbilitiesWindow::rebuild(const std::map<int, Ability> &abilityData)
         }
         else
         {
-            logger->log("Warning: No info available of ability %d", id);
+            Log::warn("No info available of ability %d", id);
         }
     }
 }