|
If you were logged in you would be able to see more operations.
|
|
|
| Severity: |
Minor
|
| Fixed in Change#: |
4,602
|
| Runtime: |
N/A
|
| Fix in hand: |
False
|
|
Early in startup, before our debug console is available, we should use the firebug console when available. As a separate step, we can consider whether to integrate more generally with firebug; this bug is just for early-stage logging.
|
|
Description
|
Early in startup, before our debug console is available, we should use the firebug console when available. As a separate step, we can consider whether to integrate more generally with firebug; this bug is just for early-stage logging. |
Show » |
|
Improvement
Resolved
P2
Debug interface should use firebug console when available
Change 20070403-ptw-s by ptw@dueling-banjos.local on 2007-04-03 17:02:03 EDT
in /Users/ptw/OpenLaszlo/legals-1
for http://svn.openlaszlo.org/openlaszlo/branches/legals
Summary: Hook Debug.log to Firebug
Bugs Fixed:
LPP-2762'Debugger in DHTML no longer warns about undefined variable references'Technical Reviewer: max (verbal)
QA Reviewer: henry (verbal)
Doc Reviewer: jsundman (pending)
Documentation:
If you have Firebug installed in your browser, `_dbg_log_all__writes`
will default to `true` and all debugging output will be logged to the
Firebug console.
This can be useful for debugging errors in the debugger or errors that
occur early in the start-up of the LFC before the debugger output is
fully functional.
Details:
LzMessage: Fix constructor so that it does not store random
objects in the message slot (e.g., $reportSourceWarning passes the
error object as an initial value). This fixes
LPP-2762.To debug
LPP-2762:Add LzMessage.toArray and LzSourceMessage.toArray which convert
message objects into arrays of strings and objects for passing to
console log (so objects are inspectable).
kernel.js, LzRuntime: Implement Debug.log by hooking it to Firebug (if it exists).
Tests:
IWFM, Test case from bug passes