[ALOY-51] Add warning and error debugging to a $Ti.Logger object. The Logger itself should just queue messages and later an be queried for it's content, This way we can log in a platform independent way.
GitHub Issue | n/a |
---|---|
Type | Sub-task |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-07-19T11:52:06.000+0000 |
Affected Version/s | 2012 Sprint 14 |
Fix Version/s | 2012 Sprint 14 |
Components | XML |
Labels | n/a |
Reporter | Russell McMahon |
Assignee | Tony Lukasavage |
Created | 2012-05-07T21:55:34.000+0000 |
Updated | 2014-06-22T13:21:14.000+0000 |
Queueing messages is fine, but it won't help us in the most critical cases where an exception shut down a titanium application with no error output. We need the ability to dump the logging output in realtime with no queueing in order to be able to capture these very difficult to debug issues.
We should however abstract all logging to a logging class. This will allow us to use the same calls throughout our code, whether we are on node or Titanium, and the logging class can determine which logging calls are appropriate to use.
Initial logger class committed here: [https://github.com/appcelerator/ZipTi/commit/a2e8c0715eeb445cd02c81d60dae14455779118f](https://github.com/appcelerator/ZipTi/commit/a2e8c0715eeb445cd02c81d60dae14455779118f)