Library needs to support a logger system

[trepidity]

No description provided.

[Dynalon]

Agreed. As I am looking into PCL compatibility, I suggest we introduce a thin ILogger interface that has rudimentary logging function like .Debug(), .Notice(), .Warn() etc such that we can hook/register a logger depending on the plattform. For PCL, for example, there is not System.IO and hence no File.* and also no Console.WriteLine. A "ConsoleLogger" could then be added implementing that interface and registered from outside the PCL parts, and on Android we can use this aLogCat thingy that tomdroid uses.

[j-4]

love your thoughts!

[trepidity]

not complicated at all! LOL

[trepidity]

I can’t believe there isn’t something we cannot already use..It would seem that this would be something Xaramin should have developed already.

Maybe I’m too optimistic 

-- 
Jared

From: Timo Dörr [email protected]
Reply: tomboy-notes/tomboy-library [email protected]
Date: February 18, 2014 at 3:47:48 PM
To: tomboy-notes/tomboy-library [email protected]
Cc: Jared Jennings [email protected]
Subject:  Re: [tomboy-library] Library needs to support a logger system (#6)

Agreed. As I am looking into PCL compatibility, I suggest we introduce a thin ILogger interface that has rudimentary logging function like .Debug(), .Notice(), .Warn() etc such that we can hook/register a logger depending on the plattform. For PCL, for example, there is not System.IO and hence no File.* and also no Console.WriteLine. A "ConsoleLogger" could then be added implementing that interface and registered from outside the PCL parts, and on Android we can use this aLogCat thingy that tomdroid uses.

—
Reply to this email directly or view it on GitHub.

[Dynalon]

It not that complicated. I have come up with sth in db2b87d

The more tricky part is registering the logger implementation.