Use Ox.Log, not Ox.print #68

Closed
opened 2011-10-28 09:39:33 +00:00 by rlx · 0 comments
Owner

There's too much printing going on. To switch to Ox.Log, we have to determine how filtering messages works (regexp on json.stringify is a bad idea, numerical level as first argument may be better), and how logging can be configured in the GUI.

There's too much printing going on. To switch to Ox.Log, we have to determine how filtering messages works (regexp on json.stringify is a bad idea, numerical level as first argument may be better), and how logging can be configured in the GUI.
rlx added this to the 11.11 milestone 2011-10-28 09:39:33 +00:00
rlx added the
major
defect
labels 2011-10-28 09:39:33 +00:00
rlx added the
general
label 2011-10-29 17:57:39 +00:00
j was assigned by rlx 2011-10-29 17:57:39 +00:00
rlx self-assigned this 2011-10-29 17:57:39 +00:00
rlx self-assigned this 2011-10-29 17:57:39 +00:00
rlx added the
fixed
label 2011-11-04 16:41:40 +00:00
rlx closed this issue 2011-11-04 16:41:40 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: 0x2620/pandora#68
No description provided.