Closed
Bug 565413
Opened 16 years ago
Closed 15 years ago
updates to the rewrite of plain-text-console.js to add support for other logging mechanisms.
Categories
(Add-on SDK Graveyard :: General, enhancement, P3)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: openjaf, Unassigned)
Details
Attachments
(2 files)
|
984 bytes,
patch
|
Details | Diff | Splinter Review | |
|
4.11 KB,
text/javascript
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3pre) Gecko/20100510 Namoroka/3.6.5pre XPCOMViewer/0.9.2
Build Identifier: Modifications to plain-text-console.js
changed plain-text-console.js to console.js, must adjust accordingly in cuddlefish.js to require console.js instead of plain-text-console.js.
Reproducible: Always
| Reporter | ||
Comment 1•16 years ago
|
||
To change functionality to the new console.js file.
| Reporter | ||
Comment 2•16 years ago
|
||
Will replace plain-text-console.js
| Reporter | ||
Comment 3•16 years ago
|
||
At this point provides support for the standard terminal output and text output of the Mozilla console.
Comment 4•16 years ago
|
||
Thanks for the patch!
The notion of 'console' in this case is actually meant to refer to the kind of console that Firebug and WebKit's web inspector use, rather than anything mozilla-specific. I'd really like to keep it that way, and put anything relating to mozilla's console service in a separate file, such as 'console-service.js' (similar to 'observer-service', 'perferences-service', etc).
Also, the reason the file is called 'plain-text-console.js' is because it's just one, very pathetic and trivial, implementation of a console interface. Ideally we want to have a much richer implementation that provides the kinds of services Firebug/Web Inspector/etc has, which allow for object introspection and the like--probably via a hookup into the HeadsUpDisplay console that David Dahl is working on in bug 553146 and bug 534398.
| Reporter | ||
Comment 5•16 years ago
|
||
Was thinking of this as the aggregation point for all console messages that would then be distributed out to the different types of console's that may be in use. Right now it only utilizes the existing plain-text-console and an implementation of the Mozilla console utilizing text messages.
Would where the messages go (mozilla, firebug, command-line) be a selectable option?
I may not understand the underlying jetpack structure well enough at this point.
Comment 6•15 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.
To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Comment 7•15 years ago
|
||
James: It isn't clear what the status of this bug is; is this still an active issue that we should address?
Whiteboard: [triage:followup]
Updated•15 years ago
|
OS: Linux → All
Priority: -- → P3
Hardware: x86 → All
Whiteboard: [triage:followup]
Target Milestone: --- → Future
Please reopen if you think we should look at this again.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•