Closed Bug 799153 Opened 13 years ago Closed 13 years ago

Add UI for toggling the debugger server in Firefox OS

Categories

(DevTools :: Debugger, defect, P3)

All
Gonk (Firefox OS)
defect

Tracking

(firefox18 fixed)

RESOLVED FIXED
Firefox 19
Tracking Status
firefox18 --- fixed

People

(Reporter: past, Assigned: past)

References

Details

(Whiteboard: [b2g])

Attachments

(1 file)

At JSConf we had discussed about having a UI toggle for enabling the debugger at some point. Looking at the current state of Firefox OS it may be appropriate to toggle the pref when flipping the Developer Mode setting.
This would be useful. Need someone from B2G product to figure out where this goes (settings? Developer submenu?) and someone in Gaia to implement it.
Flags: needinfo?
Priority: -- → P3
(In reply to Rob Campbell [:rc] (:robcee) from comment #1) > This would be useful. Need someone from B2G product to figure out where this > goes (settings? Developer submenu?) and someone in Gaia to implement it. Having this as a panel in settings would be awesome. I can mentor someone that want to do it (this is pretty simple). Basically Gaia does not have access to any firefox preferences but there is a dedicated mozSettings API that can be used. This API can then be mapped to real preferences: see http://mxr.mozilla.org/mozilla-central/source/b2g/chrome/content/settings.js#124 For the UI there is already a 'Developer' panel in Gaia and it would be great to add the necessary settings to configure the debugger server there. https://github.com/mozilla-b2g/gaia/blob/master/apps/settings/index.html#L1283
Flags: needinfo?
Attached patch Patch v1Splinter Review
Related pull request: https://github.com/mozilla-b2g/gaia/pull/6056 This patch fixes a typo and makes sure the modified pref is persisted, so that the bootstrap code in shell.js can see the changed value. A reboot (or b2g process restart) is necessary for the change to take effect.
Assignee: nobody → past
Status: NEW → ASSIGNED
Attachment #676132 - Flags: review?(21)
Comment on attachment 676132 [details] [diff] [review] Patch v1 Review of attachment 676132 [details] [diff] [review]: ----------------------------------------------------------------- Just curious why is the pref not persisted even if you don't call savePrefFile manually? Do you fear crashes?
Attachment #676132 - Flags: review?(21) → review+
(In reply to Vivien Nicolas (:vingtetun) from comment #4) > Just curious why is the pref not persisted even if you don't call > savePrefFile manually? Do you fear crashes? I'm not sure what you are asking exactly. If you mean why nsIPrefService.setFooPref doesn't automatically persist the pref, I think whoever implemented it didn't want to perform I/O without the caller's explicit request, for performance reasons. If you are asking why don't I reconfigure the debugger server on the fly, that's because that would require some additional refactoring in shell.js, like making startDebugger a member function (of shell?) so that I could add a stopDebugger sibling and call them from settings.js.
(In reply to Panos Astithas [:past] from comment #5) > (In reply to Vivien Nicolas (:vingtetun) from comment #4) > > Just curious why is the pref not persisted even if you don't call > > savePrefFile manually? Do you fear crashes? > > I'm not sure what you are asking exactly. If you mean why > nsIPrefService.setFooPref doesn't automatically persist the pref, I think > whoever implemented it didn't want to perform I/O without the caller's > explicit request, for performance reasons. That's the part I was asking :)
Whiteboard: [b2g] → [b2g][fixed-in-fx-team]
Backed out on suspicion of mochitest-1 and 3 permaorange: https://hg.mozilla.org/integration/fx-team/rev/7a86ea717506
Whiteboard: [b2g][fixed-in-fx-team] → [b2g]
Whiteboard: [b2g] → [b2g][fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [b2g][fixed-in-fx-team] → [b2g]
Target Milestone: --- → Firefox 19
Comment on attachment 676132 [details] [diff] [review] Patch v1 [Approval Request Comment] Bug caused by (feature/regressing bug #): the remote debugging UI toggle is a new feature User impact if declined: the UI toggle in gaia will not work Testing completed (on m-c, etc.): tested on m-c, desktop b2g and on my Nexus S Risk to taking this patch (and alternatives if risky): this patch doesn't affect other products at all String or UUID changes made by this patch: none
Attachment #676132 - Flags: approval-mozilla-aurora?
Attachment #676132 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: