[ALOY-37] ZipTi will need comprehensive logging
| GitHub Issue | n/a |
|---|
| Type | Story |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2012-07-19T11:52:01.000+0000 |
|---|
| Affected Version/s | 2012 Sprint 14 |
|---|
| Fix Version/s | 2012 Sprint 14 |
|---|
| Components | Runtime, Widgets, XML |
|---|
| Labels | n/a |
|---|
| Reporter | Tony Lukasavage |
|---|
| Assignee | Tony Lukasavage |
|---|
| Created | 2012-05-07T14:15:33.000+0000 |
|---|
| Updated | 2014-06-22T13:21:10.000+0000 |
|---|
Description
Description
ZipTi needs to have comprehensive logging. This includes logging during translation as well as runtime logging to account for the difficulty in debugging DOM generated code. We need to try to eliminate the inevitable developer pain points that come from an additional layer of abstraction.
Runtime
use Ti.API functions for logging to the console. We should probably have a way to control the verbosity of the output.
Translation
Use console.log() from node for output.
Comments
JSON Source
Closed because logging concerns have changed drastically since changing to XML/JSON. A new ticket will be created if necessary.